Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

[殷啟聰]

Control: tags -1 + fixed

I believe this bug has been fixed in
.

But I'm not the maintainer behind this package so I'll leave the rest
for its maintainers. I found this bug during a rebuild of all reverse
build dependencies of Gradle.

Processed: Re: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed
Bug #842721 [src:jayway-jsonpath] jayway-jsonpath: FTBFS (Could not resolve all 
dependencies)
Added tag(s) fixed.

-- 
842721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#828302: Request for sponsorship for fqterm 0.9.8.3.r4+git20161029-1

[Boyuan Yang]

Hi Aron,

I have prepared a new release (snapshot) of fqterm which contains the
fix for FTBFS with OpenSSL 1.1.0 from upstream git HEAD snapshot.
Looking forward to your review and sponsorship.

Changes since last upload:

 fqterm (0.9.8.3.r4+git20161029-1) unstable; urgency=medium

   * New upstream snapshot.
 - Various buildsystem cleanup.
 - Add new function: raw packet capture.
 - Fix FTBFS with OpenSSL 1.1.0. (Closes: #828302)
   * Bump debhelper compat to v10.
   * Fix Vcs-Git typo.
   * Switch buildsystem: cdbs -> debhelper v10.
   * Switch to build against Qt5.
   * Add new upstream docs.

   -- Boyuan Yang <073p...@gmail.com>  Sat, 29 Oct 2016 16:13:00 +0800

Several explanations:

* I chose to switch to Qt5 since Qt4 is suffering FTBFS with OpenSSL
1.1.0 and its support in stretch is unclear.


You may clone the Git repo and build the package using
git-buildpackage and pristine-tar:

  git clone https://alioth.debian.org/anonscm/git/chinese/fqterm.git

Alternatively, you may download the prebuilt deb package and dsc
package from deb-o-matic:

  dget -x -u 
http://debomatic-amd64.debian.net/debomatic/unstable/pool/fqterm_0.9.8.3.r4+git20161029-1/fqterm_0.9.8.3.r4+git20161029-1.dsc


Thanks!

--
杨博远 / Boyuan Yang <073p...@gmail.com>

Processed: Tag as forwarded

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 821481 https://jira.z-hub.io/projects/ZP/issues/ZP-804
Bug #821481 [d-push] d-push: PHP 7.0 Transition
Set Bug forwarded-to-address to 
'https://jira.z-hub.io/projects/ZP/issues/ZP-804'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 818280 is normal, tagging 818280

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 818280 normal
Bug #818280 [lvm2] upgrade-reports: System is unusable after "aptitute 
safe-upgrade"
Severity set to 'normal' from 'critical'
> tags 818280 + moreinfo
Bug #818280 [lvm2] upgrade-reports: System is unusable after "aptitute 
safe-upgrade"
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
818280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#839435: marked as done (nsscache must build-depend on tzdata)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2016 04:18:57 +
with message-id 
and subject line Bug#839435: fixed in nsscache 0.32-2
has caused the Debian Bug report #839435,
regarding nsscache must build-depend on tzdata
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
839435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nsscache
Version: 0.32-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> .F.
> ==
> FAIL: testGetSingleMapMetadataTimestampEpochFalse 
> (nss_cache.command_test.TestStatusCommand)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/mox.py", line 1870, in new_method
> func(self, *args, **kwargs)
>   File "/<>/nss_cache/command_test.py", line 817, in 
> testGetSingleMapMetadataTimestampEpochFalse
> values[1]['value'])
> AssertionError: 'Wed Dec 31 16:00:02 1969' != 'Thu Jan  1 00:00:02 1970'
> 
> --
> Ran 263 tests in 0.238s
> 
> FAILED (failures=1)
> debian/rules:11: recipe for target 'override_dh_auto_test' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/nsscache_0.32-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: nsscache
Source-Version: 0.32-2

We believe that the bug you reported is fixed in the latest version of
nsscache, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 839...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jamie Wilkinson  (supplier of updated nsscache package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2016 14:51:20 +1100
Source: nsscache
Binary: nsscache
Architecture: source all
Version: 0.32-2
Distribution: unstable
Urgency: medium
Maintainer: Jamie Wilkinson 
Changed-By: Jamie Wilkinson 
Description:
 nsscache   - asynchronously synchronise local NSS databases with remote direct
Closes: 839435
Changes:
 nsscache (0.32-2) unstable; urgency=medium
 .
   * Build-depend on tzdata.  Closes: #839435.
   * Bump standards version.
   * Update project homepage to GitHub.
Checksums-Sha1:
 ea7bdad365e54692c021ab96bd50a3480d33a1f2 1919 nsscache_0.32-2.dsc
 53e248a1f479b33808dc9ae66298febad459942c 9612 nsscache_0.32-2.debian.tar.xz
 85448cb847c2ab65e0bb48a99ad3678c1e8d24ad 85572 nsscache_0.32-2_all.deb
Checksums-Sha256:
 bcc3b2a93e28142235029efce9b0b8b5ef258931d81120b6221de42399786db7 1919 
nsscache_0.32-2.dsc
 72d6026dd6b75f3360eef57efd6b247ff3ba6b5c6aafc341c34b5ac8ed24adcd 9612 
nsscache_0.32-2.debian.tar.xz
 e29b6323ab2ebde76d9786c86fb304c24a2ae7001b1e1e0797476ac59160d03a 85572 
nsscache_0.32-2_all.deb
Fi

Processed: Re: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #841883 [src:linux] linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, 
stuck at loading initrd
Added tag(s) moreinfo.

-- 
841883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841883: linux-image-4.7.0-1-686: cannot boot with 4.7.8-1, stuck at loading initrd

[Ben Hutchings]

Control: tag -1 moreinfo

I think this may be the same as bug #841850 which is fixed in version
4.8.5-1.  Please let us know whether that works for you.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special
case.


signature.asc
Description: This is a digitally signed message part

Processed: Fix for the clipper FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #811763 [clipper] clipper: FTBFS with GCC 6: narrowing conversion
Added tag(s) patch.

-- 
811763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#811763: Fix for the clipper FTBFS

[Adrian Bunk]

Control: tags -1 patch

What broke the build is that gcc 6 changed the default C++ standard
from C++98 to C++14.

Not all valid C++98 code is also valid C++11 and C++14 code.

Note that this just changed the default, when told to process C++98 code 
gcc 6 does not differ in any significant way from gcc 5.

Making the code compatible with C++14 would be the best possible 
solution, but as a workaround it is possible to fix the build with
this change to tell gcc that this is C++98 code.


--- debian/rules.old2016-11-01 04:12:39.0 +
+++ debian/rules2016-11-01 04:13:10.0 +
@@ -1,6 +1,8 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
+export DEB_CXXFLAGS_MAINT_APPEND = -std=gnu++98
+
 # Uncomment this to turn on verbose mode.
 export DH_VERBOSE=1
 


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#842763: choreonoid FTBFS on armel and armhf: no matching function for call to 'QTransform::map(int, int, double*, double*)'

[Adrian Bunk]

Source: choreonoid
Version: 1.5.0+dfsg-0.1
Severity: serious

https://buildd.debian.org/status/package.php?p=choreonoid&suite=sid


/«BUILDDIR»/choreonoid-1.5.0+dfsg/src/Base/ImageWidget.cpp: In member function 
'void cnoid::ImageWidget::zoom(double)':
/«BUILDDIR»/choreonoid-1.5.0+dfsg/src/Base/ImageWidget.cpp:95:41: error: no 
matching function for call to 'QTransform::map(int, int, double*, double*)'
  invT.map(r.width()/2,r.height()/2,&x,&y);
 ^
In file included from /usr/include/qt4/QtGui/qbrush.h:51:0,
 from /usr/include/qt4/QtGui/qpalette.h:47,
 from /usr/include/qt4/QtGui/qwidget.h:50,
 from /usr/include/qt4/QtGui/QWidget:1,
 from 
/«BUILDDIR»/choreonoid-1.5.0+dfsg/src/Base/ImageWidget.h:8,
 from 
/«BUILDDIR»/choreonoid-1.5.0+dfsg/src/Base/ImageWidget.cpp:5:
/usr/include/qt4/QtGui/qtransform.h:141:18: note: candidate: QPoint 
QTransform::map(const QPoint&) const
 QPoint   map(const QPoint &p) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:141:18: note:   candidate expects 1 
argument, 4 provided
/usr/include/qt4/QtGui/qtransform.h:142:18: note: candidate: QPointF 
QTransform::map(const QPointF&) const
 QPointF  map(const QPointF &p) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:142:18: note:   candidate expects 1 
argument, 4 provided
/usr/include/qt4/QtGui/qtransform.h:143:18: note: candidate: QLine 
QTransform::map(const QLine&) const
 QLinemap(const QLine &l) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:143:18: note:   candidate expects 1 
argument, 4 provided
/usr/include/qt4/QtGui/qtransform.h:144:18: note: candidate: QLineF 
QTransform::map(const QLineF&) const
 QLineF   map(const QLineF &l) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:144:18: note:   candidate expects 1 
argument, 4 provided
/usr/include/qt4/QtGui/qtransform.h:145:18: note: candidate: QPolygonF 
QTransform::map(const QPolygonF&) const
 QPolygonFmap(const QPolygonF &a) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:145:18: note:   candidate expects 1 
argument, 4 provided
/usr/include/qt4/QtGui/qtransform.h:146:18: note: candidate: QPolygon 
QTransform::map(const QPolygon&) const
 QPolygon map(const QPolygon &a) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:146:18: note:   candidate expects 1 
argument, 4 provided
/usr/include/qt4/QtGui/qtransform.h:147:18: note: candidate: QRegion 
QTransform::map(const QRegion&) const
 QRegion  map(const QRegion &r) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:147:18: note:   candidate expects 1 
argument, 4 provided
/usr/include/qt4/QtGui/qtransform.h:148:18: note: candidate: QPainterPath 
QTransform::map(const QPainterPath&) const
 QPainterPath map(const QPainterPath &p) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:148:18: note:   candidate expects 1 
argument, 4 provided
/usr/include/qt4/QtGui/qtransform.h:152:10: note: candidate: void 
QTransform::map(int, int, int*, int*) const
 void map(int x, int y, int *tx, int *ty) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:152:10: note:   no known conversion for 
argument 3 from 'double*' to 'int*'
/usr/include/qt4/QtGui/qtransform.h:153:10: note: candidate: void 
QTransform::map(qreal, qreal, qreal*, qreal*) const
 void map(qreal x, qreal y, qreal *tx, qreal *ty) const;
  ^~~
/usr/include/qt4/QtGui/qtransform.h:153:10: note:   no known conversion for 
argument 3 from 'double*' to 'qreal* {aka float*}'

Bug#834718: choreonoid: maintainer address bounces

[Adrian Bunk]

On Thu, Aug 18, 2016 at 11:21:27AM +0200, Jakub Wilk wrote:
> Source: choreonoid
> Version: 1.5.0+dfsg-0.1
> Severity: serious
> Justification: Policy §3.3
> 
> I tried to report a bug against this package, and I got:
> 
> > Your mail to 'Ubuntu-devel-discuss' with the subject
> > 
> >Bug#834715: libcnoid-dev: arch-dependent file in "Multi-Arch: same"
> > package
> > 
> > Is being held until the list moderator can review it for approval.
> > 
> > The reason it is being held:
> > 
> >Post by non-member to a members-only list
> 
> As per Policy §3.3: “The email address given in the ‘Maintainer’ control
> field must accept mail from those role accounts in Debian used to send
> automated mails regarding the package. This includes non-spam mail from the
> bug-tracking system, […].”
> 
> NB, this is caught by Lintian:
> 
> E: choreonoid source: maintainer-address-causes-mail-loops-or-bounces Ubuntu 
> Developers 


Maintainer: Ubuntu Developers 
Original-Maintainer: Thomas Moulard 


Dimitri, did you accidentally include this maintainer change typical 
for Ubuntu in your NMU?


> Jakub Wilk

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: This one also looks pretty RC

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 760660 serious
Bug #760660 [bindgraph] bindgraph, don't startup.
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
760660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#837420: marked as done (dietlibc: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Tue, 01 Nov 2016 03:05:07 +
with message-id 
and subject line Bug#837420: fixed in dietlibc 0.34~cvs20160606-3
has caused the Debian Bug report #837420,
regarding dietlibc: FTBFS with bindnow and PIE enabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
837420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dietlibc
Version: 0.34~cvs20160606-2
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
gcc -D__dietlibc__ -isystem include -Os -fstrict-aliasing
-momit-leaf-frame-pointer -mfancy-math-387  -g -W -Wall -Wextra
-Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations
-Wno-switch -Wno-unused -Wredundant-decls -Wshadow
-fstack-protector-strong -nostdlib -o bin-x86_64/diet bin-x86_64/start.o
bin-x86_64/dyn_start.o diet.c bin-x86_64/dietlibc.a
bin-x86_64/dyn_stop.o -DDIETHOME=\"/<>\"
-DVERSION=\"0.34~cvs20160606-2\" -lgcc
/usr/bin/ld: bin-x86_64/dietlibc.a(stackgap.o): relocation R_X86_64_32
against `.rodata.str1.1' can not be used when making a shared object;
recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
Makefile:362: recipe for target 'bin-x86_64/diet' failed

...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/dietlibc_0.34~cvs20160606-2_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: dietlibc
Source-Version: 0.34~cvs20160606-3

We believe that the bug you reported is fixed in the latest version of
dietlibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Seiler  (supplier of updated dietlibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2016 02:32:22 +0100
Source: dietlibc
Binary: dietlibc-dev dietlibc-doc
Architecture: source
Version: 0.34~cvs20160606-3
Distribution: unstable
Urgency: medium
Maintainer: Hector Oron 
Changed-By: Christian Seiler 
Description:
 dietlibc-dev - diet libc - a libc optimized for small size
 dietlibc-doc - diet libc documentation - a libc optimized for small size
Closes: 837420
Changes:
 dietlibc (0.34~cvs20160606-3) unstable; urgency=medium
 .
   * Properly pass in CFLAGS from dpkg-buildflags.
 Rework Debian-specific patches to make sure we pass in dpkg-buildflags
 to dietlibc's build system. Also make sure that we pass -fno-pie and
 -no-pie to the build system so that the new default setting of gcc in
 Debian for PIE (enabled by default) is overridden, as static binaries
 don't support PIE. Drop the hardening patch that explicitly added
 stack protector support, as that is now passed in externally. This
 should also make the build reproducible again, as -fdebug-prefix-map
 is now passed to the compiler. (Closes: #837420)
   * Make dietlibc-doc a Multi-Arch: foreign package
Checksums-Sha1:
 2d1dc8841b724cf561086c17785956767334a0ff 2337 dietlibc_0.34~cvs20160606-3.dsc
 f313f4c340691085a026c5882e23738eb5b062e1 33600 
dietlibc_0.34~cvs20160606-3.debian.tar.xz
Checksums-Sha256:
 b62aa1630bf87c68035e83d7129373517941942c3a33d86728b1f8970b015110 2337 
dietlibc_0.34~cvs20160606-3.dsc
 acf8231eda09102e598d07be1475e3dfaa716b5b57a66923438b425ff7a86b68 33600 
dietlibc_0.34~cvs20160606-3.debian.tar.xz
Files:
 f59697dfcb3456fd02c93a34a75ebff6 2337 devel optional 
dietlibc_0.34~cvs20160606-3.dsc
 b51112c21f404d4a2a5cd9587e5209b4 33600 devel optional 
dietlibc_0.34~cvs20160606-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYF/K+AAoJEGMjNFnNz

Processed: Re: Bug#842586: git: FTBFS on mips64el (fatal: Out of memory, getdelim failed)

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 git/1:2.10.2-1
Bug #842586 [src:git] git: FTBFS on mips64el (fatal: Out of memory, getdelim 
failed)
No longer marked as found in versions git/1:2.10.2-1.
> close -1
Bug #842586 [src:git] git: FTBFS on mips64el (fatal: Out of memory, getdelim 
failed)
Marked Bug as done

-- 
842586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#842586: git: FTBFS on mips64el (fatal: Out of memory, getdelim failed)

[Anders Kaseorg]

Control: notfound -1 git/1:2.10.2-1
Control: close -1

On Mon, 31 Oct 2016, Sebastiaan Couwenberg wrote:
> I think we can close this issue as notfound in git/1:2.10.2-1, since the
> most reliable mips64el buildd was able to build it successfully.

Thanks, doing so.

Anders

Bug#842753: FTBFS: test failures

[gregor herrmann]

Package: libnet-sip-perl
Version: 0.690-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

0.690-1 fails to build all over the place with more or less failing
tests:

https://buildd.debian.org/status/fetch.php?pkg=libnet-sip-perl&arch=all&ver=0.690-1&stamp=1477852334

https://ci.debian.net/packages/libn/libnet-sip-perl/unstable/amd64/
(ok, doesn't look package specific)

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libnet-sip-perl_0.690-1.rbuild.log
https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/libnet-sip-perl_0.690-1.rbuild.log
https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/libnet-sip-perl_0.690-1.rbuild.log


Fascinating that it built for me yesterday …


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYF++FXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG5S8P/0yC0nHsTDRSYT4yY4Bd72k/
sGK3SROoWLZssxcQibtwAYiBCTkbDZ4mJwHMmTMOlLyu3jlUNect3cpctL1Cm1rS
jXDo+jPII2QoWd3QMu7no0fbjsUZdznxTxzsZvLOQKF2DsRqFx4vK8p5k5glzLn3
/nCCKdcxPhTVs7kzcA4v2AQvWp+VMDLQSB4LByDZmHMUhu5V80TLbAzNFUP2/o2a
d7XQncuj9E9LeMUoTinFqfEkG+ueoO70F7wYoOB3Hr54qOxUb+RYmbVK2a9jkeNH
vdcHCVIUig6lk9CH/fljCzv4VynzEilOtNlcQANlLORg6ACIpHfUksLCLJtys0xY
j4lrZ8ZWxpguKmdqcNLSeGcdWpAq9aDndMm01X1WC1TDOscUajg/lFA0PS3Ar+bz
gIf4edMgsdEWQlM/80WvtX3LM27tVvo8CPzERXR2VHidVMlDGG7YEBSB4peF18N9
IQHOccGFl7dj2fLoP5TQ3pdeGHYkNMm+3XByGPcSircezur5Qta/XI6+m8ZOZlkK
rdHMYGfGlqfApUCbOuv797G1yJirhoD6mRtf20WE29beB/wajYkGQTTtX9ZtEvhJ
c0oKbRJvHmadrRE55CHhGrLiQmMebL7sRkk4kkoUzYgzsMlUsn7ngfOmcn9gT5wc
SFY4lCtnMYnVQaGX0GaC
=nZRb
-END PGP SIGNATURE-

Bug#841511: python-bitbucket-api, python-bitbucket: error when trying to install together

[陳昌倬]

On Mon, Oct 24, 2016 at 12:56:08PM +, David Villa wrote:
> I think python-bitbucket can be removed. Its functionality is quite limited.

Hi David,

In that case, could you help to send a removal request?


-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#836885: [Pkg-openldap-devel] Bug#836885: please stop building against Heimdal

[Ryan Tandy]

On Tue, Nov 01, 2016 at 01:12:08AM +0100, Emilio Pozuelo Monfort wrote:

This is blocking the removal of heimdal, thus bumping to serious.


Yes, sorry about that. I am actively working on this, but it's not quite 
ready to upload yet.

Bug#837485: [pkg-golang-devel] Bug#837485: Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

[Tianon Gravi]

On 31 October 2016 at 17:12, Michael Hudson-Doyle
 wrote:
> The question is, do we backport the fixes for golang-1.6, or just remove it
> from the archive?

Looks like removal would be fairly straightforward; the only package
currently affected is "golang-github-docker-go", which could just as
well stop using patching and just use the pre-patched copy of
encoding/json embedded in upstream's source (since refreshing
_upstream's_ patches for Go 1.7 likely isn't worth the effort for such
a minor package IMO).

For reference:

$ ssh mirror.ftp-master.debian.org dak rm -Rn golang-1.6
Will remove the following packages from unstable:

golang-1.6 |1.6.3-2 | source, all
golang-1.6-doc |1.6.3-2 | all
golang-1.6-go |1.6.3-2 | amd64, arm64, armel, armhf, i386, ppc64el
golang-1.6-src |1.6.3-2 | amd64, arm64, armel, armhf, i386, ppc64el

Maintainer: Go Compiler Team 

--- Reason ---

--

Checking reverse dependencies...
# Broken Build-Depends:
golang-github-docker-go: golang-1.6-go
 golang-1.6-src

Dependency problem found.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#773205: libatomic-ops-dev: FTBFS on mips64el

[Ian Wienand]

I'm sorry about this. I must have misread the history of that branch

My preference is to be in sync with upstream, so I have asked if we
can get this in a 7.4.5 release [1]

If no response, or not possible, I'll add these back in

Thanks,

-i

[1] https://github.com/ivmai/libatomic_ops/issues/20

On Fri, Oct 28, 2016 at 8:31 PM, James Cowgill  wrote:
> Control: found -1 7.4.4-1
> Control: severity -1 serious
>
> Hi,
>
> In 7.4.4-1 the patches adding mips64el support were removed from the
> package. While they've applied upstream in the 'master' branch not all
> of them were applied to the 'release-7_4' branch and libatomic-ops FTBFS
> on mips64el again.
>
> These have been applied to 7.4.4-1 (which is good):
>  0002-Remove-inclusion-of-acquire_release_volatile.h-on-mi.patch
>  0003-Minor-fix-of-code-alignment-in-mips-AO_compare_and_s.patch
>
> Please reapply these patches from 7.4.2-3:
>  0001-Use-LLD-and-SCD-instructions-on-mips64.patch
>  0004-Support-n32-ABI-for-mips64.patch
>
> Thanks,
> James
>

Bug#837485: [pkg-golang-devel] Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

[Michael Hudson-Doyle]

I fixed this problem a while ago upstream for Go 1.7 (
https://github.com/golang/go/issues/15443,
https://github.com/golang/go/issues/15887). The question is, do we backport
the fixes for golang-1.6, or just remove it from the archive? I'd lean
towards the latter.

On 1 November 2016 at 08:18, Niels Thykier  wrote:

> On Mon, 12 Sep 2016 00:55:37 +0200 Balint Reczey
>  wrote:
> > Source: golang-1.6
> > Version: 1.6.3-1
> > Severity: important
> > User: bal...@balintreczey.hu
> > Usertags: pie-bindnow-20160906
> > Justification: FTBFS on amd64 with extra hardening
> > Tags: patch
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64 with patched GCC and dpkg.
> >
> > The rebuild tested if packages are ready for a transition
> > enabling PIE and bindnow for amd64.
> >
> > For more information about the changes to sid's dpkg and GCC please
> > visit:
> >  https://wiki.debian.org/Hardening/PIEByDefaultTransition
> >
> > Relevant part (hopefully):
> > ...
> > [...]
>
> Dear maintainers,
>
> The thread-sanitizer (used by golang) is not compatible with PIE[1].
>
>  * Please disable either PIE or the thread-sanitizer.
>  * From a quick look, it appears that the thread-sanitizer is done by
>upstream.
>  * On that basis, I think we should prefer that over PIE in the given
>case (for consistency with upstream).
>
>
> Thanks,
> ~Niels
>
> [1] https://wiki.ubuntu.com/SecurityTeam/PIE
>
> ___
> pkg-golang-devel mailing list
> pkg-golang-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-golang-devel
>

Processed: Re: please stop building against Heimdal

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #836885 [src:openldap] please stop building against Heimdal
Severity set to 'serious' from 'important'

-- 
836885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Removal of Heimdal from testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #837628 [libheimdal-kadm5-perl] Removal of Heimdal from testing
Severity set to 'serious' from 'normal'

-- 
837628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#818561: Useless in Debian

[David Prévot]

Hi Axel, haskell-hoogle maintainers,

Le 31/10/2016 à 13:25, Axel Beckert a écrit :
> David Prévot wrote:
>> Package: libjs-chosen
>> Version: 0.9.11-2
>> Severity: serious
>> Tags: sid stretch
>>
>> [ Filled as an RC-bug by the maintainer to see the package auto-removed
>>   from testing. ]
>>
>> I packaged libjs-chosen as used by owncloud, but owncloud is going away,
>> see #816376. There is a priori little point to ship libjs-chosen in the
>> next Debian stable release.

> JFTR: The recent hoogle update pulled this in. So it seems no more
> useless but now even has reverse dependencies again. :-)

Thank you Axel for the heads up. I guess someone (maybe from the
hoogle team) will want to take over the maintenance. Feel free to remove
me from Uploaders when you do.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#842752: postgresql-9.6: FTBFS: test failures on i386/armel/armhf

[Emilio Pozuelo Monfort]

Source: postgresql-9.6
Version: 9.6.1-1
Severity: serious

Your package failed to build on i386, armel and armhf with test errors.

See the logs at https://buildd.debian.org/status/package.php?p=postgresql-9.6

Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#842751: fim: FTBFS on several architectures

[Emilio Pozuelo Monfort]

Package: fim
Version: 0.5~rc2-2
Severity: serious

Your package still fails to build on several architectures. See the logs at
https://buildd.debian.org/status/package.php?p=fim

Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#830423: marked as done (connect-proxy: FTBFS: dpkg-buildpackage: error: dpkg-genchanges gave error exit status 25)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 23:48:40 +
with message-id 
and subject line Bug#830423: fixed in connect-proxy 1.105-1
has caused the Debian Bug report #830423,
regarding connect-proxy: FTBFS: dpkg-buildpackage: error: dpkg-genchanges gave 
error exit status 25
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
830423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: connect-proxy
Version: 1.101-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> mkdir -p /«PKGBUILDDIR»/debian/connect-proxy/usr/bin/
> install connect-proxy /«PKGBUILDDIR»/debian/connect-proxy/usr/bin/
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> dh_testdir
> dh_testroot
> dh_installchangelogs 
> dh_installdocs
> dh_installman
> dh_link
> dh_strip
> dh_compress
> dh_fixperms
> dh_installdeb
> dh_shlibdeps
> dh_gencontrol
> dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
> not NFS-safe
> dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
> not NFS-safe
> dh_md5sums
> dh_builddeb
> dpkg-deb: building package 'connect-proxy-dbgsym' in 
> '../connect-proxy-dbgsym_1.101-1_amd64.deb'.
> dpkg-deb: building package 'connect-proxy' in 
> '../connect-proxy_1.101-1_amd64.deb'.
>  dpkg-genchanges -sa >../connect-proxy_1.101-1_amd64.changes
> dpkg-genchanges: warning: debian/changelog(l17): invalid abbreviated 
> month name 'Sept'
> LINE:  -- Philippe Coval   Wed, 20 Sept 2007 23:59:42 +0200
> dpkg-genchanges: warning: debian/changelog(l17): cannot parse 
> non-comformant date '20 Sept 2007 23:59:42 +0200'
> LINE:  -- Philippe Coval   Wed, 20 Sept 2007 23:59:42 +0200
> Can't call method "epoch" on an undefined value at 
> /usr/share/perl5/Dpkg/Changelog.pm line 498.
> dpkg-buildpackage: error: dpkg-genchanges gave error exit status 25
> 
> Build finished at 20160706-2140

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/connect-proxy_1.101-1_unstable_reb.normal.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: connect-proxy
Source-Version: 1.105-1

We believe that the bug you reported is fixed in the latest version of
connect-proxy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 830...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Bayle  (supplier of updated connect-proxy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 31 Oct 2016 21:03:15 +0100
Source: connect-proxy
Binary: connect-proxy
Architecture: source amd64
Version: 1.105-1
Distribution: unstable
Urgency: medium
Maintainer: Philippe Coval 
Changed-By: Christian Bayle 
Description:
 connect-proxy - Establish TCP connection using SOCKS4/5 or HTTP tunnel
Closes: 689051 830423
Changes:
 connect-proxy (1.105-1) unstable; urgency=medium
 .
   * New upstream release (rebuilt tarball)
   * Removed quilt, created a Makefile, switched to dh7
   * Fix non-comformant date in debian/changelog (Closes: #830423)
   * Removed patch (Closes: #689051)
Checksums-Sha1:
 cd91c29e318868a65eb9c67649a8263765e17723 1791 connect-proxy_1.105-1.dsc
 44bd57b22d45c8e57c35cc2e7ec68b9a18150ab0 24809 connect-proxy_1.105.orig.tar.gz
 10125a922614151aafb3e777e9f0440606683b7c 5048 
connect-proxy_1.105-1.debian.tar.xz
 dde39f67469b5f2514d9d2de0a570b196124dffe 4104 
connect-proxy-dbgsym_1.105-1_amd64.deb
 743babc24e6d73423808633889a7f91154fc49a5 1883

Bug#841597: blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Kouhei Maeda]

Thanks your report.
But in my environment that I made with pbuilder and cowbuilder, the
problem does not reappear.
Please tell me your environmental how to make because I want to test
it in the same environment.

Best regards,
--
Kouhei Maeda 
 KeyID 4096R/7E37CE41


2016-10-21 22:38 GMT+09:00 Lucas Nussbaum :
> Source: blockdiag
> Version: 1.5.3+dfsg-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161021 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
>> ---[ stderr ] ---
>> WARNING: unknown image type: http://localhost:8000/circle.svg
>> WARNING: unknown image type: http://localhost:8000/circle.eps
>>
>>
>> - >> end captured stdout << --
>>
>> Ran 710 tests in 2.530s
>>
>> FAILED (SKIP=351, failures=1)
>> E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
>> /<>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 
>> -m nose
>> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
>> exit code 13
>> debian/rules:13: recipe for target 'build' failed
>> make: *** [build] Error 25
>> dpkg-buildpackage: error: debian/rules build gave error exit status 2
>> E: Build killed with signal TERM after 150 minutes of inactivity
>
> If the failure looks somehow time/timezone related:
> Note that this rebuild was performed without the 'tzdata' package
> installed in the chroot. tzdata used be (transitively) part of
> build-essential, but it no longer is. If this package requires it to
> build, it should be added to build-depends. For the release team's
> opinion on this, see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185
>
> If the failure looks LSB-related:
> similarly to tzdata, lsb-base is not installed in the build chroot.
>
> The full build log is available from:
>http://aws-logs.debian.net/2016/10/21/blockdiag_1.5.3+dfsg-1_unstable.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.

Bug#818561: Useless in Debian

[Axel Beckert]

Hi,

David Prévot wrote:
> Package: libjs-chosen
> Version: 0.9.11-2
> Severity: serious
> Tags: sid stretch
> 
> [ Filled as an RC-bug by the maintainer to see the package auto-removed
>   from testing. ]
> 
> I packaged libjs-chosen as used by owncloud, but owncloud is going away,
> see #816376. There is a priori little point to ship libjs-chosen in the
> next Debian stable release.
> 
> I intend to follow up with an RM request in a few months if nobody
> objects (but feel free to beat me to it).

JFTR: The recent hoogle update pulled this in. So it seems no more
useless but now even has reverse dependencies again. :-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#829477: marked as done (courier-mta: fails to install: Invalid command 'gendh')

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 23:19:05 +
with message-id 
and subject line Bug#829477: fixed in courier 0.76.3-1
has caused the Debian Bug report #829477,
regarding courier-mta: fails to install: Invalid command 'gendh'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
829477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-mta
Version: 0.76.1-3+exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package courier-mta.
  (Reading database ... 
(Reading database ... 10293 files and directories currently installed.)
  Preparing to unpack .../courier-mta_0.76.1-3+exp1_amd64.deb ...
  Adding 'diversion of /usr/bin/addcr to /usr/bin/addcr.ucspi-tcp by 
courier-mta'
  Adding 'diversion of /usr/share/man/man1/addcr.1.gz to 
/usr/share/man/man1/addcr.ucspi-tcp.1.gz by courier-mta'
  Unpacking courier-mta (0.76.1-3+exp1) ...
  Setting up courier-mta (0.76.1-3+exp1) ...
  update-alternatives: using /usr/bin/lockmail.courier to provide 
/usr/bin/lockmail (lockmail) in auto mode
  update-alternatives: using /usr/bin/preline.courier to provide 
/usr/bin/preline (preline) in auto mode
  /run/courier/esmtpd.pid.lock: No such file or directory
  Generating a 4096 bit RSA private key
  ..++
  
.++
  writing new private key to '/etc/courier/esmtpd.pem'
  -
  Invalid command 'gendh'; type "help" for a list.
  dpkg: error processing package courier-mta (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   courier-mta


cheers,

Andreas


courier-mta_0.76.1-3+exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 0.76.3-1

We believe that the bug you reported is fixed in the latest version of
courier, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 829...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated courier package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2016 11:53:03 +0100
Source: courier
Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail 
courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap 
courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl
Architecture: source
Version: 0.76.3-1
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Ondřej Surý 
Description:
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax<->mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-imap-ssl - Courier mail server - IMAP over SSL [transitional]
 courier-ldap - Courier mail server - LDAP support
 courier-maildrop - Courier mail server - mail delivery agent [transitional 
package]
 courier-mlm - Courier mail server - mailing list manager
 courier-mta - Courier mail server - ESMTP daemon
 courier-mta-ssl - Courier mail server - ESMTP over SSL
 courier-pcp - Courier mail server - PCP server
 courier-pop - Courier mail server - POP3 server
 courier-pop-ssl - Courier mail server - POP3 over SSL [transitional]
 courier-ssl - Courier mail server - SSL/TLS Support [transitional]
 courier-webadmin - Courier mail server - web-based administration frontend
 sqwebmail  - Courier mail server - webmail server
Closes: 828272 829477
Changes:
 courier (0.76.3-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.76.3
+ OpenSSL 1.1.0 support (Closes: #828272)
   * Rebase patches on top o

Bug#828272: marked as done (courier: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 23:19:05 +
with message-id 
and subject line Bug#828272: fixed in courier 0.76.3-1
has caused the Debian Bug report #828272,
regarding courier: FTBFS with openssl 1.1.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
828272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: courier
Version: 0.76.1-3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/courier_0.76.1-3_amd64-20160529-1412

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 0.76.3-1

We believe that the bug you reported is fixed in the latest version of
courier, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 828...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated courier package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Oct 2016 11:53:03 +0100
Source: courier
Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail 
courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap 
courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl
Architecture: source
Version: 0.76.3-1
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Ondřej Surý 
Description:
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax<->mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-imap-ssl - Courier mail server - IMAP over SSL [transitional]
 courier-ldap - Courier mail server - LDAP support
 courier-maildrop - Courier mail server - mail delivery agent [transitional 
package]
 courier-mlm - Courier mail server - mailing list manager
 courier-mta - Courier mail server - ESMTP daemon
 courier-mta-ssl - Courier mail server - ESMTP over SSL
 courier-pcp - Courier mail server - PCP server
 courier-pop - Courier mail server - POP3 server
 courier-pop-ssl - Courier mail server - POP3 over SSL [transitional]
 courier-ssl - Courier mail server - SSL/TLS Support [transitional]
 courier-webadmin - Courier mail server - web-based administration frontend
 sqwebmail  - Courier mail server - webmail server
Closes: 828272 829477
Changes:
 courier (0.76.3-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.76.3
+ OpenSSL 1.1.0 support (Closes: #828272)
   * Rebase patches on top of 0.76.3 release
   * Use default-libmysqlclient-dev as a first choice dependency
   * Use openssl dhparam instead of openssl gendh for OpenSSL 1.1.x
 compatibility (Closes: #829477)
Checksums-Sha1:
 88cb02da0dd2bcfe4dae727de119a5683dea6ede 3217 courier_0.76.3-1.dsc
 0aec8634a6e37c0342e4b88f78210e6287819413 7239375 courier_0.76.3.orig.tar.bz2
 6efea58853f66a089e34b7dc502efd3285816ff6 94396 courier_0.76.3-1.debian.tar.xz
Checksums-Sha256:
 923365e754bfbde8af4efe0dbd120af1e28f0a44656a6240f41ce1083465361e 3217 
courier_0.76.3-1.dsc
 ac98301c346e00730e7e40a662c64099dae5cdb5f99b7ac8a104883d2d2dcca6 7239375 
courier_0.76.3.orig.tar.bz2
 939d80386028e341af9dcf8ac742325043daf000181ffdf08460a5a370f7d0ad 94396 
courier_0.76.3-1.debian.tar.xz
Files:
 f23f1030e3cfd91d21b8457df049436c 3217 mail optional courier_0.76.3-1.dsc
 caac8e3aff3a1edbc8c0aef0a2b08ea1 7239375 mail optional 
courier_0.76.3.orig.tar.bz2
 a00088ca43f7ae8d8125330b4ce3d282 94396 mail optional 

Bug#818280: upgrade-reports: System is unusable after "aptitute safe-upgrade" [SOLVED]

[Michael Biebl]

Control: reassign -1 lvm2

On Wed, 16 Mar 2016 17:51:32 +0100 Gilles Sadowski
 wrote:
> Hi.
> 
> It turned out that the problem was related to LVM partitions not being
> "available" while "systemd" was trying to run "fsck" on them.
> 
> In maintenance mode, I just ran
> 
>  # vgchange -a y theVolumeGroupName
> 
> and they were automatically detected, and mounted.
> Then the boot sequence could proceed normally.
> 
> Why couldn't "systemd" figure out the problem?

Problem seems to happen under "sysinit" as well.

> Upon rebooting, I chose the option "sysinit" (rather than the default grub 
> entry).
> This led to a flood of "Failed" during the boot sequence, seemingly caused by 
> a read-only root filesystem.


So might be a LVM problem. Unfortunately the bug report is very light of
details. Might be just a misconfigured system


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#818280: upgrade-reports: System is unusable after "aptitute safe-upgrade" [SOLVED]

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 lvm2
Bug #818280 [systemd] upgrade-reports: System is unusable after "aptitute 
safe-upgrade"
Bug reassigned from package 'systemd' to 'lvm2'.
Ignoring request to alter found versions of bug #818280 to the same values 
previously set
Ignoring request to alter fixed versions of bug #818280 to the same values 
previously set

-- 
818280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#828579: trousers: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #828579 [src:trousers] trousers: FTBFS with openssl 1.1.0
Added tag(s) patch.

-- 
828579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#828579: trousers: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 patch

On 2016-06-26 12:24:29 [+0200], Kurt Roeckx wrote:
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/trousers_0.3.13-4_amd64-20160529-1546

The fedora bugzilla has a patch
https://bugzilla.redhat.com/show_bug.cgi?id=1388518

> Kurt

Sebastian

Bug#829477: courier-mta: fails to install: Invalid command 'gendh'

[Ondřej Surý]

Yes, I already had a fix in repo (use dhparam -2 instead) and I have just 
uploaded that.


Ondřej


On 31 October 2016 11:24:13 PM Andreas Beckmann  wrote:


On 2016-10-31 16:32, Stefan Hornburg (Racke) wrote:

On 07/03/2016 07:07 PM, Andreas Beckmann wrote:

Package: courier-mta
Version: 0.76.1-3+exp1



I believe this line in the script /usr/lib/courier/mkesmtpdcert
causes the error:

/usr/bin/openssl gendh -rand "$PEMFILE".rand 512 >>"$PEMFILE" || cleanup

Why openssl doesn't know about it on piuparts eludes me.


that is probably openssl 1.1 from experimental being used in that test


Andreas

Processed: Re: pkcs11-helper: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/OpenSC/pkcs11-helper/pull/7
Bug #828506 [src:pkcs11-helper] pkcs11-helper: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://github.com/OpenSC/pkcs11-helper/pull/7'.
> tags -1 patch
Bug #828506 [src:pkcs11-helper] pkcs11-helper: FTBFS with openssl 1.1.0
Added tag(s) patch.

-- 
828506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#828506: pkcs11-helper: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: forwarded -1 https://github.com/OpenSC/pkcs11-helper/pull/7
control: tags -1 patch

On 2016-06-26 12:23:44 [+0200], Kurt Roeckx wrote:
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/pkcs11-helper_1.11-5_amd64-20160529-1509

There is an pull request from fedora. The fedora bug ist at
https://bugzilla.redhat.com/show_bug.cgi?id=1388463

> Kurt

Sebastian

Bug#828259: cargo: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-06-26 12:21:14 [+0200], Kurt Roeckx wrote:
> Source: cargo
> Version: 0.9.0-1
> Severity: important
> Control: block 827061 by -1
> 
> Hi,
> 
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/cargo_0.9.0-1_amd64-20160529-1410

There is fedora bug [0] and they point to upstream towards rust-openssl [1]
which should be fixed first.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1383778
[1] https://github.com/sfackler/rust-openssl/issues/452

> 
> If you have problems making things work, feel free to contact us.
> 
> 
> Kurt

Sebastian

Bug#841420: Breaks Nvidia driver install from .run

[Berillions]

I can confirm that the new version of GCC breaks the module's compilation
when i try to install the Nvidia driver for my graphic card from the .run
file.

The only solution that i found was to launch "export CC=/usr/bin/gcc-5"
before to launch the driver's installation

Cheers,
Maxime

Bug#842748: incremental: FTBFS (failing tests)

[Santiago Vila]

Package: src:incremental
Version: 16.10.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/incremental
copying src/incremental/update.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/incremental
copying src/incremental/_version.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/incremental
copying src/incremental/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/incremental
creating /<>/.pybuild/pythonX.Y_2.7/build/incremental/tests
copying src/incremental/tests/test_version.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/incremental/tests
copying src/incremental/tests/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/incremental/tests
copying src/incremental/tests/test_update.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/incremental/tests
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/incremental
copying src/incremental/update.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/incremental
copying src/incremental/_version.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/incremental
copying src/incremental/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/incremental
creating /<>/.pybuild/pythonX.Y_3.5/build/incremental/tests
copying src/incremental/tests/test_version.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/incremental/tests
copying src/incremental/tests/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/incremental/tests
copying src/incremental/tests/test_update.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/incremental/tests
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m unittest discover -v 
test_detectUnknownVersion (incremental.tests.test_version.FormatDiscoveryTests)
test_detectUnknownVersion ... ok
test_detectVersion10 (incremental.tests.test_version.FormatDiscoveryTests)
test_detectVersion10 ... ok
test_detectVersion4 (incremental.tests.test_version.FormatDiscoveryTests)
test_detectVersion4 ... ok
test_detectVersion8 (incremental.tests.test_version.FormatDiscoveryTests)
test_detectVersion8 ... ok
test_detectVersion9 (incremental.tests.test_version.FormatDiscoveryTests)
test_detectVersion9 ... ok
test_getVersionStringWithRevision 
(incremental.tests.test_version.FormatDiscoveryTests)
test_getVersionStringWithRevision ... ok
test_unparseableEntries (incremental.tests.test_version.FormatDiscoveryTests)
test_unparseableEntries ... ok
runTest (twisted.trial._asynctest.TestCase)
runTest ... ok
testShort (incremental.tests.test_version.VersionsTests)
testShort ... ok
test_NEXTMustBeAlone (incremental.tests.test_version.VersionsTests)
test_NEXTMustBeAlone ... ok
test_base (incremental.tests.test_version.VersionsTests)
test_base ... ok
test_baseWithDev (incremental.tests.test_version.VersionsTests)
test_baseWithDev ... ok
test_baseWithDevAndRC (incremental.tests.test_version.VersionsTests)
test_baseWithDevAndRC ... ok
test_baseWithNEXT (incremental.tests.test_version.VersionsTests)
test_baseWithNEXT ... ok
test_baseWithPrerelease (incremental.tests.test_version.VersionsTests)
test_baseWithPrerelease ... ok
test_baseWithReleaseCandidate (incremental.tests.test_version.VersionsTests)
test_baseWithReleaseCandidate ... ok
test_comparingDev (incremental.tests.test_version.VersionsTests)
test_comparingDev ... ok
test_comparingDevAndRC (incremental.tests.test_version.VersionsTests)
test_comparingDevAndRC ... ok
test_comparingDevAndRCDifferent (incremental.tests.test_version.VersionsTests)
test_comparingDevAndRCDifferent ... ok
test_comparingDevReleasesWithReleases 
(incremental.tests.test_version.VersionsTests)
test_comparingDevReleasesWithReleases ... ok
test_comparingNEXTReleases (incremental.tests.test_version.VersionsTests)
test_comparingNEXTReleases ... ok
test_comparingNEXTReleasesEqual (incremental.tests.test_version.VersionsTests)
test_comparingNEXTReleasesEqual ... ok
test_comparingPrereleasesWithReleases 
(incremental.tests.test_version.VersionsTests)
test_comparingPrereleasesWithReleases ... ok
test_comparingReleaseCandidates (incremental.tests.test_version.VersionsTests)
test_comparingReleaseCandidates ... ok
test_comparingReleaseCandidatesWithReleases 
(incremental.tests.test_version.VersionsTests)
test_comparingReleaseCandidatesWithReleases ... ok
test_devWithReleaseCandidate (inc

Bug#829477: courier-mta: fails to install: Invalid command 'gendh'

[Andreas Beckmann]

On 2016-10-31 16:32, Stefan Hornburg (Racke) wrote:
> On 07/03/2016 07:07 PM, Andreas Beckmann wrote:
>> Package: courier-mta
>> Version: 0.76.1-3+exp1

> I believe this line in the script /usr/lib/courier/mkesmtpdcert
> causes the error:
> 
>   /usr/bin/openssl gendh -rand "$PEMFILE".rand 512 >>"$PEMFILE" || cleanup
> 
> Why openssl doesn't know about it on piuparts eludes me.

that is probably openssl 1.1 from experimental being used in that test


Andreas

Processed: Move to systemd

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 818280 systemd
Bug #818280 [upgrade-reports] upgrade-reports: System is unusable after 
"aptitute safe-upgrade"
Bug reassigned from package 'upgrade-reports' to 'systemd'.
Ignoring request to alter found versions of bug #818280 to the same values 
previously set
Ignoring request to alter fixed versions of bug #818280 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
818280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Kernel issue?

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 842458 src:linux
Bug #842458 [upgrade-reports] upgrade-reports: After dist-upgrade from jessie 
to testing, kernel doesn't load, not a single message on screen
Bug reassigned from package 'upgrade-reports' to 'src:linux'.
Ignoring request to alter found versions of bug #842458 to the same values 
previously set
Ignoring request to alter fixed versions of bug #842458 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: libghc-lambdabot-haskell-plugins-dev: inane memory usage during profiling build

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://ghc.haskell.org/trac/ghc/ticket/12790
Bug #842740 [libghc-lambdabot-haskell-plugins-dev] 
libghc-lambdabot-haskell-plugins-dev: inane memory usage during profiling build
Set Bug forwarded-to-address to 'https://ghc.haskell.org/trac/ghc/ticket/12790'.

-- 
842740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#842740: libghc-lambdabot-haskell-plugins-dev: inane memory usage during profiling build

[Clint Adams]

Package: libghc-lambdabot-haskell-plugins-dev
Version: 5.1-2
Severity: serious
Control: forwarded -1 https://ghc.haskell.org/trac/ghc/ticket/12790

Number of terms skyrockets during Simplify, probable GHC bug.

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Jose R R]

On Mon, Oct 31, 2016 at 12:31 AM, Konstantin Demin  wrote:
> I have tested several scenarios and "KCPPFLAGS=-fno-PIE" does that
> trick much better :-)
>
> --
> SY,
> Konstantin Demin
uname -a
Linux cohuatlicue 4.7.10.tezcatlipoca #1 SMP PREEMPT Mon Oct 31
09:47:07 PDT 2016 x86_64 GNU/Linux

i.e., Aufs4/Reiser4 kernel re-built with your suggestion, as:

time KCPPFLAGS="-fno-PIE" fakeroot make-kpkg
--append-to-version=.tezcatlipoca --stem gcc6-aufs4+reiser4m -j8
--initrd kernel_image kernel_headers

Thanks again, Konstantin.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#842710: [gcc-6] Fails to compile OpenWrt/LEDE prereq-build

[Adrian Bunk]

Control: reassign -1 release.debian.org
Control: severity -1 normal
Control: retitle -1 nmu: zlib_1:1.2.8.dfsg-2
Control: affects -1 src:zlib

On Mon, Oct 31, 2016 at 03:27:11PM +0100, Charlemagne Lasse wrote:
> Package: gcc-6
> Version: 6.2.0-10
> Severity: serious
> X-Debbugs-CC: lede-...@lists.infradead.org
> 
> There is a regression after gcc-6 6.2.0-6. I get following output when
> trying to compile LEDE/OpenWrt "Please install a static zlib"
>...
> with gcc-6 6.2.0-10 fails:
> 
> $ echo 'int main(int argc, char **argv) { gzdopen(0, "rb"); return 0;
> }' | gcc -include zlib.h -x c -o a.out - -Wl,-Bstatic -lz
> -Wl,-Bdynamic
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libz.a(gzlib.o):
> relocation R_X86_64_32S against `.rodata' can not be used when making
> a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status
> $ echo $?
> 1

Thanks for your bug report.

The problem here is that gcc now defaults to PIE, which is not 
compatible with static libraries compiled without PIE. (The error 
message is misleading, PIE is sufficient and PIC is not required.)

The (few) static libraries that are used for building other packages
in unstable have already been recompiled.

A rebuild of all packages containing static libraries at once is not 
planned, but it will be ensured that all such packages will be rebuilt 
before the release of stretch.

I am reassigning this bug to the release team to schedule a binNMU
of zlib:
nmu zlib_1:1.2.8.dfsg-2 . ANY . unstable . -m "Recompile static libraries with 
PIE"

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Re: [gcc-6] Fails to compile OpenWrt/LEDE prereq-build

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 release.debian.org
Bug #842710 [gcc-6] [gcc-6] Fails to compile OpenWrt/LEDE prereq-build
Bug reassigned from package 'gcc-6' to 'release.debian.org'.
No longer marked as found in versions gcc-6/6.2.0-10.
Ignoring request to alter fixed versions of bug #842710 to the same values 
previously set
> severity -1 normal
Bug #842710 [release.debian.org] [gcc-6] Fails to compile OpenWrt/LEDE 
prereq-build
Severity set to 'normal' from 'serious'
> retitle -1 nmu: zlib_1:1.2.8.dfsg-2
Bug #842710 [release.debian.org] [gcc-6] Fails to compile OpenWrt/LEDE 
prereq-build
Changed Bug title to 'nmu: zlib_1:1.2.8.dfsg-2' from '[gcc-6] Fails to compile 
OpenWrt/LEDE prereq-build'.
> affects -1 src:zlib
Bug #842710 [release.debian.org] nmu: zlib_1:1.2.8.dfsg-2
Added indication that 842710 affects src:zlib

-- 
842710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 828469 fixed-upstream
Bug #828469 [src:openipmi] openipmi: FTBFS with openssl 1.1.0
Added tag(s) fixed-upstream.
> forwarded 828469 
> https://sourceforge.net/p/openipmi/code/ci/eeacbf0c675b61881fc00539cb365de084950ceb/
Bug #828469 [src:openipmi] openipmi: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://sourceforge.net/p/openipmi/code/ci/eeacbf0c675b61881fc00539cb365de084950ceb/'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
828469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tag security

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 842702 security
Bug #842702 [zabbix-frontend-php] Remote Code Execution on Zabbix 2.2 < 3.0.3
Added tag(s) security.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#842737: ohai: FTBFS: Could not find 'addressable' (>= 0) among 31 total gem(s) (Gem::LoadError)

[Chris Lamb]

Source: ohai
Version: 8.21.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ohai fails to build from source in unstable/amd64:

  […]

  
┌──┐
  │ Checking Rubygems dependency resolution on ruby2.3  
 │
  
└──┘
  
  
GEM_PATH=debian/ohai/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -e gem\ \"ohai\"
  /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'addressable' (>= 0) among 31 total gem(s) (Gem::LoadError)
  Checked in 
'GEM_PATH=debian/ohai/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1438:in `block in 
activate_dependencies'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `each'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in 
`activate_dependencies'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1409:in `activate'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1441:in `block in 
activate_dependencies'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `each'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in 
`activate_dependencies'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1409:in `activate'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
`synchronize'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
from -e:1:in `'
  bigdecimal (1.2.8)
  chef-config (12.14.60)
  did_you_mean (1.0.0)
  diff-lcs (1.2.5)
  ffi (1.9.10)
  ffi-yajl (2.2.3)
  fuzzyurl (0.8.0)
  io-console (0.4.5)
  ipaddress (0.8.3)
  json (1.8.3)
  minitest (5.9.0)
  mixlib-cli (1.7.0)
  mixlib-config (2.2.1)
  mixlib-log (1.7.1)
  mixlib-shellout (2.2.6)
  net-telnet (0.1.1)
  plist (3.2.0)
  power_assert (0.2.7)
  psych (2.0.17)
  rake (10.5.0)
  rdoc (4.2.1)
  rspec (3.5.0)
  rspec-collection_matchers (1.1.2)
  rspec-core (3.5.3)
  rspec-expectations (3.5.0)
  rspec-mocks (3.5.0)
  rspec-support (3.5.0)
  systemu (2.6.5)
  test-unit (3.1.7)
  thread_order (1.1.0)
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20161031194437.QRAyVGVM5A.db.ohai/ohai-8.21.0/debian/ohai 
returned exit code 1
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 1

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ohai.8.21.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#837359: ocaml: FTBFS on -fPIE binNMU on armhf - test failure

[Adrian Bunk]

On Mon, Oct 31, 2016 at 06:46:00PM +, Niels Thykier wrote:
> Control: retitle -1 ocaml: FTBFS on -fPIE binNMU on armhf - test failure
> 
> Dear maintainer,
> 
> We have tried to binNMU ocaml in unstable now that PIE is on by default.
>  This worked fine on all release architectures except armhf, where 4
> tests failed:
> 
> """
> Summary:
>   468 test(s) passed
> 4 test(s) failed
> 0 unexpected error(s)
> 
> List of failed tests:
> tests/asmcomp/quicksort2
> tests/asmcomp/soli
> tests/asmcomp/arith
> tests/asmcomp/tagged-integr
> """
> 
> Source:
> https://buildd.debian.org/status/fetch.php?pkg=ocaml&arch=armhf&ver=4.02.3-7%2Bb1&stamp=1477553350


 ... testing 'quicksort2':/usr/bin/ld: quicksort2.o: relocation 
R_ARM_THM_MOVW_ABS_NC against `cmp' can not be used when making a shared 
object; recompile with -fPIC
quicksort2.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
 => failed
 ... testing 'soli':/usr/bin/ld: soli.o: relocation R_ARM_THM_MOVW_ABS_NC 
against `a local symbol' can not be used when making a shared object; recompile 
with -fPIC
soli.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
 => failed
 ... testing 'arith':/usr/bin/ld: arith.o: relocation R_ARM_THM_MOVW_ABS_NC 
against `D' can not be used when making a shared object; recompile with -fPIC
arith.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
 => failed
 ... testing 'tagged-integr':/usr/bin/ld: tagged-integr.o: relocation 
R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when making a 
shared object; recompile with -fPIC
tagged-integr.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
 => failed

Several other testcases are building fine.

The odd thing is that these worked on armel and arm64 but failed on armhf.

Note that the "recompile with -fPIC" error message can be misleading.
It is also given when building binaries where only PIE is required
(which is the default in the gcc used).


> If you believe this is a transient failure, please let me know and I
> will schedule a retry (give-back).
> 
> Thanks,
> ~Niels

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#838812: pg_upgradecluster skips databases owned by a role who is not a user

[Tilman Koschnick]

Package: postgresql-common
Version: 177.pgdg80+1
Followup-For: Bug #838812

Dear Maintainer,

I can confirm the problem; the attached patch fixes it.

A brief explanation: In the query to select databases which need upgrading, 
pg_database is joined onto pg_user, which is a view of pg_shadow, which in turn 
is a view of pg_authid, containing only roles with login privileges. Thus any 
databases owned by roles without login privileges are not included in the list. 
The fix is to join on pg_authid instead.

See https://www.postgresql.org/docs/9.6/static/view-pg-user.html and 
https://www.postgresql.org/docs/9.6/static/view-pg-shadow.html .

Regards, Til

PS #614374 is a duplicate of this bug.

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postgresql-common depends on:
ii  adduser   3.113+nmu3
ii  debconf [debconf-2.0] 1.5.56
ii  init-system-helpers   1.22
ii  lsb-base  4.1+Debian13+nmu1
ii  postgresql-client-common  177.pgdg80+1
ii  procps2:3.3.9-9
ii  ssl-cert  1.0.35
ii  ucf   3.0030

Versions of packages postgresql-common recommends:
ii  logrotate  3.8.7-1+b1

postgresql-common suggests no packages.
--- /usr/bin/pg_upgradecluster.orig	2016-10-31 13:38:45.942422918 +0100
+++ /usr/bin/pg_upgradecluster	2016-10-31 13:40:34.561540476 +0100
@@ -439,7 +439,7 @@
 	my %databases;
 	open F, '-|', $oldpsql, '-h', $oldsocket, '-p', $info{'port'}, 
 	'-F|', '-d', 'template1', '-Atc', 
-	'SELECT datname, datallowconn, pg_catalog.pg_encoding_to_char(encoding), usename FROM pg_database, pg_user WHERE datdba = usesysid' or 
+	'SELECT datname, datallowconn, pg_catalog.pg_encoding_to_char(encoding), rolname FROM pg_database, pg_roles WHERE datdba = pg_roles.oid' or
 	error 'Could not get pg_database list';
 	while () {
 	chomp;

Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

[Niels Thykier]

On Mon, 12 Sep 2016 00:55:37 +0200 Balint Reczey
 wrote:
> Source: golang-1.6
> Version: 1.6.3-1
> Severity: important
> User: bal...@balintreczey.hu
> Usertags: pie-bindnow-20160906
> Justification: FTBFS on amd64 with extra hardening
> Tags: patch
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64 with patched GCC and dpkg.
> 
> The rebuild tested if packages are ready for a transition
> enabling PIE and bindnow for amd64.
> 
> For more information about the changes to sid's dpkg and GCC please
> visit:
>  https://wiki.debian.org/Hardening/PIEByDefaultTransition
> 
> Relevant part (hopefully):
> ...
> [...]

Dear maintainers,

The thread-sanitizer (used by golang) is not compatible with PIE[1].

 * Please disable either PIE or the thread-sanitizer.
 * From a quick look, it appears that the thread-sanitizer is done by
   upstream.
 * On that basis, I think we should prefer that over PIE in the given
   case (for consistency with upstream).


Thanks,
~Niels

[1] https://wiki.ubuntu.com/SecurityTeam/PIE

Bug#774082: What is the solution/workaround ?

[Vincent Danjean]

Le 31/10/2016 à 18:22, Benoit Plessis a écrit :
> 
> Hi,
> 
> I am also affected by this issue, where the initramfs only activate the
> root/usr lv's
> 
> what is the recommended jessie workaround, disabling lvmetad ?

The workaround I gave in my comment #74 [1] allows me to use
lvmetad on all my jessie machines. You can try it.

  Regards,
Vincent


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774082#74

-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main

Bug#842586: git: FTBFS on mips64el (fatal: Out of memory, getdelim failed)

[Sebastiaan Couwenberg]

On Mon, 31 Oct 2016 15:30:52 + James Cowgill wrote:
> I've had a bit of a look at this bug. I've now tried to build git on two
> different machines running different hardware (octeon and loongson) and
> it built fine both times so I'm not too sure what's going on here.
> 
> All 3 builds which failed were Loongson machines running 3.16 kernels.
> While I know they have FPU problems, I wouldn't have thought that would
> give an out of memory error.
> 
> It would be good to get the package rebuilt on an Octeon to see if it is
> a hardware problem.

I'm not sure if mipsel-sil-01 is an Octeon system, but it just
successfully built git (1:2.10.2-1).

I have noticed that mipsel-sil-01 is not as prone to fail builds as
mipsel-manda-0{1,2} are, if there is some way to prefer that buildd that
would be awesome.

I think we can close this issue as notfound in git/1:2.10.2-1, since the
most reliable mips64el buildd was able to build it successfully.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#837569: marked as done (psicode needs PIE binNMU)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 18:53:00 +
with message-id 
and subject line Re: mpqc3: FTBFS with bindnow and PIE enabled
has caused the Debian Bug report #837569,
regarding psicode needs PIE binNMU
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
837569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpqc3
Version: 0.0~git20160216-3
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
-- Found OpenBabel2:
--  OPENBABEL2_LIBRARIES: /usr/lib/libopenbabel.so
--  OPENBABEL2_INCLUDE_DIR: /usr/include/openbabel-2.0
-- Performing Test PSI3_COMPILES
-- Performing Test PSI3_COMPILES - Failed
CMake Error at external/Psi3:56 (message):
  Could not compile Psi3 test program
Call Stack (most recent call first):
  external/External:16 (include)
  CMakeLists.txt:301 (include)
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/mpqc3_0.0~git20160216-3_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
On Mon, 12 Sep 2016 16:31:44 +0200 Balint Reczey
 wrote:
> Source: mpqc3
> Version: 0.0~git20160216-3
> Severity: important
> User: bal...@balintreczey.hu
> Usertags: pie-bindnow-20160906
> Justification: FTBFS on amd64 with extra hardening
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64 with patched GCC and dpkg.
> 
> The rebuild tested if packages are ready for a transition
> enabling PIE and bindnow for amd64.
> 
> For more information about the changes to sid's dpkg and GCC please
> visit:
>  https://wiki.debian.org/Hardening/PIEByDefaultTransition
> 
> Relevant part (hopefully):
> ...
> -- Found OpenBabel2:
> --  OPENBABEL2_LIBRARIES: /usr/lib/libopenbabel.so
> --  OPENBABEL2_INCLUDE_DIR: /usr/include/openbabel-2.0
> -- Performing Test PSI3_COMPILES
> -- Performing Test PSI3_COMPILES - Failed
> CMake Error at external/Psi3:56 (message):
>   Could not compile Psi3 test program
> Call Stack (most recent call first):
>   external/External:16 (include)
>   CMakeLists.txt:301 (include)
> ...
> 
> The full build log is available from:
>  
> https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/mpqc3_0.0~git20160216-3_amd64.build.gz
> 
> Thanks,
> Balint
> 
> 
> 

This was solved by a binNMU.

Thanks,
~Niels--- End Message ---

Bug#837359: ocaml: FTBFS on -fPIE binNMU on armhf - test failure

[Niels Thykier]

Control: retitle -1 ocaml: FTBFS on -fPIE binNMU on armhf - test failure

Dear maintainer,

We have tried to binNMU ocaml in unstable now that PIE is on by default.
 This worked fine on all release architectures except armhf, where 4
tests failed:

"""
Summary:
  468 test(s) passed
4 test(s) failed
0 unexpected error(s)

List of failed tests:
tests/asmcomp/quicksort2
tests/asmcomp/soli
tests/asmcomp/arith
tests/asmcomp/tagged-integr
"""

Source:
https://buildd.debian.org/status/fetch.php?pkg=ocaml&arch=armhf&ver=4.02.3-7%2Bb1&stamp=1477553350

If you believe this is a transient failure, please let me know and I
will schedule a retry (give-back).

Thanks,
~Niels

Processed: Re: Bug#837359: ocaml: FTBFS on -fPIE binNMU on armhf - test failure

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 ocaml: FTBFS on -fPIE binNMU on armhf - test failure
Bug #837359 [src:ocaml] ocaml needs PIE binNMU
Changed Bug title to 'ocaml: FTBFS on -fPIE binNMU on armhf - test failure' 
from 'ocaml needs PIE binNMU'.

-- 
837359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841683: marked as done (lp-solve needs PIE binNMU)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 18:49:00 +
with message-id 
and subject line Re: liblpsolve55-dev: Please build liblpsolve55.a with -fPIC
has caused the Debian Bug report #841683,
regarding lp-solve needs PIE binNMU
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblpsolve55-dev
Version: 5.5.0.15-4
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: makes mccs FTBFS with extra hardening
Affects: mccs libreoffice

Dear Maintainers,

During a rebuild of all packages in sid, mccs
failed to build on amd64 with patched GCC and dpkg. The root
cause seems to be that liblpsolve55.a is shipped as a non-PIC library.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64 (and selected architectures).

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part of mccs's build log:
...
g++ -Wall -O6 -Wl,-z,relro -Wl,-z,now  -DUSELPSOLVE -o mccs objs/cudf.o
objs/constraint_generation.o objs/lp_solver.o objs/pblib_solver.o
objs/removed_criteria.o objs/changed_criteria.o objs/new_criteria.o
objs/notuptodate_criteria.o objs/nunsat_criteria.o objs/count_criteria.o
objs/unaligned_criteria.o objs/lexicographic_combiner.o
objs/lexagregate_combiner.o objs/agregate_combiner.o
objs/lexsemiagregate_combiner.o objs/leximin_combiner.o
objs/leximax_combiner.o objs/lexleximin_combiner.o
objs/lexleximax_combiner.o objs/cudf_reductions.o objs/lpsolve_solver.o
-lfl -L. -lccudf \
 \
 \
-L/usr/lib -llpsolve55 -ldl -lcolamd \
/usr/bin/ld: /usr/lib/liblpsolve55.a(lp_lib.o): relocation
R_X86_64_32 against `.rodata.str1.1' can not be used when making a
shared object; recompile with -fPIC
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/mccs_1.1-3_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
On Mon, 12 Sep 2016 16:29:06 +0200 Balint Reczey
 wrote:
> Source: liblpsolve55-dev
> Version: 5.5.0.15-4
> Severity: important
> User: bal...@balintreczey.hu
> Usertags: pie-bindnow-20160906
> Justification: makes mccs FTBFS with extra hardening
> Affects: mccs libreoffice
> 
> Dear Maintainers,
> 
> During a rebuild of all packages in sid, mccs
> failed to build on amd64 with patched GCC and dpkg. The root
> cause seems to be that liblpsolve55.a is shipped as a non-PIC library.
> 
> The rebuild tested if packages are ready for a transition
> enabling PIE and bindnow for amd64 (and selected architectures).
> 
> For more information about the changes to sid's dpkg and GCC please
> visit:
>  https://wiki.debian.org/Hardening/PIEByDefaultTransition
> 
> Relevant part of mccs's build log:
> ...
> g++ -Wall -O6 -Wl,-z,relro -Wl,-z,now  -DUSELPSOLVE -o mccs objs/cudf.o
> objs/constraint_generation.o objs/lp_solver.o objs/pblib_solver.o
> objs/removed_criteria.o objs/changed_criteria.o objs/new_criteria.o
> objs/notuptodate_criteria.o objs/nunsat_criteria.o objs/count_criteria.o
> objs/unaligned_criteria.o objs/lexicographic_combiner.o
> objs/lexagregate_combiner.o objs/agregate_combiner.o
> objs/lexsemiagregate_combiner.o objs/leximin_combiner.o
> objs/leximax_combiner.o objs/lexleximin_combiner.o
> objs/lexleximax_combiner.o objs/cudf_reductions.o objs/lpsolve_solver.o
> -lfl -L. -lccudf \
>  \
>  \
> -L/usr/lib -llpsolve55 -ldl -lcolamd \
> /usr/bin/ld: /usr/lib/liblpsolve55.a(lp_lib.o): relocation
> R_X86_64_32 against `.rodata.str1.1' can not be used when making a
> shared object; recompile with -fPIC
> ...
> 
> The full build log is available from:
>  
> https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/mccs_1.1-3_amd64.build.gz
> 
> Thanks,
> Balint
> 
> 
> 

Solved by a binNMU.

Thanks,
~Niels--- End Message ---

Bug#806118: marked as done (tiff: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 18:37:29 +
with message-id 
and subject line Bug#806118: fixed in tiff 4.0.6-3
has caused the Debian Bug report #806118,
regarding tiff: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
806118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tiff
Version: 4.0.5-1
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep --with autoreconf --with autotools-dev
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
make -j1 install DESTDIR=/<>/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[1]: Entering directory '/<>'
Making install in port
make[2]: Entering directory '/<>/port'
make[3]: Entering directory '/<>/port'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>/port'
make[2]: Leaving directory '/<>/port'
Making install in libtiff
make[2]: Entering directory '/<>/libtiff'
make[3]: Entering directory '/<>/libtiff'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu'
 /bin/bash ../libtool   --mode=install /usr/bin/install -c   libtiff.la 
libtiffxx.la '/<>/debian/tmp/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/libtiff.so.5.2.3 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libtiff.so.5.2.3
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libtiff.so.5.2.3 libtiff.so.5 || { rm -f libtiff.so.5 && ln -s 
libtiff.so.5.2.3 libtiff.so.5; }; })
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libtiff.so.5.2.3 libtiff.so || { rm -f libtiff.so && ln -s 
libtiff.so.5.2.3 libtiff.so; }; })

[... snipped ...]

dh_install: usr/share/doc/libtiff-doc/ChangeLog exists in debian/tmp but is not 
installed to anywhere
dh_install: usr/share/doc/libtiff-doc/TODO exists in debian/tmp but is not 
installed to anywhere
dh_install: usr/share/doc/libtiff-doc/VERSION exists in debian/tmp but is not 
installed to anywhere
# tiffgt is in libtiff-opengl so libtiff-tools doesn't have to have
# all the X and opengl dependencies.
rm debian/libtiff-tools/usr/bin/tiffgt
rm: cannot remove 'debian/libtiff-tools/usr/bin/tiffgt': No such file or 
directory
debian/rules:22: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: tiff
Source-Version: 4.0.6-3

We believe that the bug you reported is fixed in the latest version of
tiff, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 806...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of u

Bug#841343: marked as done (rakudo: FTBFS on arm64, powerpc and ppc64 - testsuite errors)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 18:04:37 +
with message-id 
and subject line Bug#841343: fixed in moarvm 2016.10+dfsg-1
has caused the Debian Bug report #841343,
regarding rakudo: FTBFS on arm64, powerpc and ppc64 - testsuite errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rakudo
Version: 2016.09-2
Severity: serious
Tags: sid stretch

Hi,

rakudo FTBFS on arm64, powerpc and ppc64 with errors in the testsuite.

arm64 times out during the 't/04-nativecall/02-simple-args.t' test.

For powerpc the errors are:
t/04-nativecall/01-argless.t . ok
t/04-nativecall/02-simple-args.t . ok
t/04-nativecall/03-simple-returns.t ..
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/11 subtests
t/04-nativecall/04-pointers.t  ok
t/04-nativecall/05-arrays.t .. ok
t/04-nativecall/06-struct.t .. ok
t/04-nativecall/07-writebarrier.t  ok
t/04-nativecall/08-callbacks.t ... ok
t/04-nativecall/09-nativecast.t .. ok
t/04-nativecall/10-cglobals.t  ok
t/04-nativecall/11-cpp.t . ok
t/04-nativecall/12-sizeof.t .. ok
t/04-nativecall/13-cpp-mangling.t  ok
t/04-nativecall/13-union.t ... ok
t/04-nativecall/14-rw-attrs.t 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/16 subtests
t/04-nativecall/15-rw-args.t .
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/22 subtests
t/04-nativecall/16-rt125408.t  ok
t/04-nativecall/16-rt125729.t  ok
t/04-nativecall/17-libnames.t  ok
t/04-nativecall/18-routine-sig-sanity.t .. ok
t/04-nativecall/19-function-pointers.t ... ok

Test Summary Report
---
t/04-nativecall/03-simple-returns.t(Wstat: 1024 Tests: 11 Failed: 4)
  Failed tests:  2-3, 9-10
  Non-zero exit status: 4
t/04-nativecall/14-rw-attrs.t  (Wstat: 256 Tests: 16 Failed: 1)
  Failed test:  15
  Non-zero exit status: 1
t/04-nativecall/15-rw-args.t   (Wstat: 1024 Tests: 22 Failed: 4)
  Failed tests:  2, 4, 14, 16
  Non-zero exit status: 4
Files=45, Tests=600, 139 wallclock secs ( 0.30 usr  0.06 sys + 136.86
cusr  1.64 csys = 138.86 CPU)
Result: FAIL

The ppc64 errors are all in the nativecall tests as well.

Full build logs:
https://buildd.debian.org/status/package.php?p=rakudo

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: moarvm
Source-Version: 2016.10+dfsg-1

We believe that the bug you reported is fixed in the latest version of
moarvm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated moarvm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Oct 2016 18:25:01 +0200
Source: moarvm
Binary: moarvm moarvm-dev
Architecture: source amd64
Version: 2016.10+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Description:
 moarvm - virtual machine for Rakudo Perl 6 and NQP
 moarvm-dev - development files for moarvm
Closes: 841343
Changes:
 moarvm (2016.10+dfsg-1) unstable; urgency=medium
 .
   Many thanks to Tobias Leich (FROGGS) who did a terrific job
   porting moar on all architectures supported by Debian.
   * New upstream version 2016.10+dfsg
   * remove patches applied upstream
   + new patch: use ffi_arg type to fix powerpc build
 (Closes: #841343)
   + add patch to fix nqp tests on mips
   + added patch to fix build without dyncall source
   + added patch to fix s390x build
   * control:
 * enable s390x
 * enable mips mipsel mips64el (cf: #841346)
   * copyright: remove excluded dyncall (cme)
Checksums-Sha1:
 07fa0e07ff20a3895e05f0c85bf82cdbe8ea3395 2453 moarvm_2016.10+dfsg-1.dsc
 05515cd768edcefc2066c76c0ee9d181d22c2565 1714162 
moarvm_2016.10+dfsg.orig.tar.gz
 e737c3b0b60ab8d3e374ef70f1d83f764498a8b4 13872 

Bug#842722: marked as done (kgb-bot: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 18:04:00 +
with message-id 
and subject line Bug#842722: fixed in kgb-bot 1.34-2
has caused the Debian Bug report #842722,
regarding kgb-bot: FTBFS (failing tests)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
842722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kgb-bot
Version: 1.34-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking prerequisites...
  test_requires:
!  Test::Perl::Critic is not installed

ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
of the modules indicated above before proceeding with this installation

Run 'Build installdeps' to install missing prerequisites.

Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'App-KGB' version '1.34'
   dh_auto_build -i
perl Build
Building App-KGB
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
LANG=bg_BG.utf8 LC_ALL=bg_BG.utf8 dh_auto_test
perl Build test --verbose 1
t/00-compile.t . 
ok 1 - blib/lib/App/KGB.pm compiles
ok 2 - blib/lib/WWW/Shorten/Debli.pm compiles
ok 3 - blib/lib/App/KGB/Client.pm compiles
ok 4 - blib/lib/App/KGB/API.pm compiles
ok 5 - blib/lib/App/KGB/Commit.pm compiles
ok 6 - blib/lib/App/KGB/Painter.pm compiles
ok 7 - blib/lib/App/KGB/Change.pm compiles
ok 8 - blib/lib/App/KGB/Commit/Tag.pm compiles
ok 9 - blib/lib/App/KGB/Client/ServerRef.pm compiles
ok 10 - blib/lib/App/KGB/Client/Subversion.pm compiles
ok 11 - blib/lib/App/KGB/Client/Fake.pm compiles
ok 12 - blib/lib/App/KGB/Client/RelayMsg.pm compiles
ok 13 - blib/lib/App/KGB/Client/Git.pm compiles
ok 14 - blib/lib/App/KGB/Client/CVS.pm compiles
ok 15 - blib/lib/JSON/RPC/Client/Any.pm compiles
1..15
ok
script/kgb-add-project syntax OK
script/kgb-ci-report syntax OK
script/kgb-bot syntax OK
script/kgb-client syntax OK
script/kgb-split-config syntax OK
t/00-compile_scripts.t . 
1..5
ok 1 - script/kgb-add-project compiles
ok 2 - script/kgb-ci-report compiles
ok 3 - script/kgb-bot compiles
ok 4 - script/kgb-client compiles
ok 5 - script/kgb-split-config compiles
ok
t/00-compile_shell_scripts.t ... 
ok 1
1..1
ok
t/30-bot-changes.t . 
ok 1
ok 2
ok 3
1..3
ok
# trying port 5392
# test bot listening on 127.0.0.1:5392, pid: 2593  at t/TestBot.pm line 117.
# Test bot started on 127.0.0.1:5392
# $>=924 $<=924 $ENV{USER}=buildd getpwuid($>)=buildd
# stopping test bot, pid 2593
# Removing directory /<>/t/bot
t/50-client.t .. 
Checked out revision 0.
A file
Adding file
Transmitting file data .done
Committing transaction...
Committed revision 1.
Sendingfile
Transmitting file data .done
Committing transaction...
Committed revision 2.
D file
A file
Replacing  file
Transmitting file data .done
Committing transaction...
Committed revision 3.
ok 1 - Test repository prepared
ok 2 - An object of class 'App::KGB::Client::Subversion' isa 
'App::KGB::Client::Subversion'
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 25 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 26 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 27 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 28 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 29 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 30 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 31
1..31
ok
t/51-client_branch_module.t  
ok 1 - An object of class 'App::KGB::Client::Subversion' isa 
'App::KGB::Client::Subversion'
ok 2 - branch detection in [module and branch] (/kgb/trunk/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 3

Bug#841420: Patch to allow build

[Raymond Burkholder]

> -Original Message-
> From: Arthur Gautier [mailto:ba...@gandi.net]

> On Sun, Oct 30, 2016 at 01:32:14AM -0300, Raymond Burkholder wrote:
> > Step 1:
> >
> > scripts/config --disable CC_STACKPROTECTOR_STRONG
> 
> This is a step forward security, we can not just disable it on production
> systems.

Another test shows that there is no need to disable
CC_STACKPROTECTOR_STRONG.  It appears to have been a red-herring on the way
to determining the real solution (if only a work around for now)

~/linux-4.8.6$ grep CC_STACKPROTECTOR_STRONG .config
CONFIG_CC_STACKPROTECTOR_STRONG=y

Using gcc-6 6.2.0-9 with kernel 4.8.6.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Processed: [bts-link] source package src:pen

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:pen
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #828492 (http://bugs.debian.org/828492)
> # Bug title: pen: FTBFS with openssl 1.1.0
> #  * https://github.com/UlricE/pen/issues/28
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 828492 + fixed-upstream
Bug #828492 [src:pen] pen: FTBFS with openssl 1.1.0
Added tag(s) fixed-upstream.
> usertags 828492 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 828492 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
828492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840664: marked as done (ruby-faker: FTBFS randomly (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 17:49:30 +
with message-id 
and subject line Bug#840664: fixed in ruby-faker 1.6.6-1
has caused the Debian Bug report #840664,
regarding ruby-faker: FTBFS randomly (failing tests)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-faker
Version: 1.5.0-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed.

The package builds ok, but then the tests fail randomly, because they
are not designed to never fail (as they should).

At least the following tests seem to be wrongly designed:

  => 14: assert Faker::Internet.email.match(/.+@[^.].+\.\w+/)
  => 70: assert period_range.include?(result.hour.to_i), 
"\"#{result.hour}\" expected to be included in 
Faker::Time::TIME_RANGES[:#{period}] range"

so I suggest that they are just disabled.

I'm attaching 9 different build logs. Sorry, I can't provide a way to
"reproduce" this because the failures are random, but if you look at
the build logs and look at the code, maybe you could tell why they
fail without having to build this package yourself a lot of times.

Thanks.

ruby-faker_1.5.0-1_amd64-20161012T212217Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161012T213114Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161012T213145Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161012T213155Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153231Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153254Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153256Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153315Z.gz
Description: application/gzip


ruby-faker_1.5.0-1_amd64-20161013T153320Z.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-faker
Source-Version: 1.6.6-1

We believe that the bug you reported is fixed in the latest version of
ruby-faker, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-faker package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 31 Oct 2016 16:34:30 +0530
Source: ruby-faker
Binary: ruby-faker
Architecture: source
Version: 1.6.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-faker - easily generate fake data
Closes: 840664
Changes:
 ruby-faker (1.6.6-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
   * Fix/disable failing tests (Closes: #840664)
   * Enable more locales for tests
   * Disable test/test_es_locale.rb (needs locale path fix)
Checksums-Sha1:
 4d84d472d7b5ca3ca96e6be5bdbc299e15ba67a3 2044 ruby-faker_1.6.6-1.dsc
 e4ccfd3f509f9680a7fad3c72b7436cd62b6560d 279776 ruby-faker_1.6.6.orig.tar.gz
 997cd9a1c945a55a66093880660b4974acc378a3 3292 ruby-faker_1.6.6-1.debian.tar.xz
Checksums-Sha256:
 9d65ec5133ba6aad281ee406ebd4463e5645a77b93f5ae05c184e5a1f1c478d4 2044 
ruby-faker_1.6.6-1.dsc
 cb98de744ea6f566096b2be3e113afcc98b031464d5f6cb1b3447088a2d4c4dc 279776 
ruby-faker_1.6.6.orig.tar.gz
 d417a180239426ce01b311f299241e530037fc1f0f26883caf7b53da2c1b1383 3292 
ruby-faker_1.6.6-1.debian.tar.xz
Files:
 517fc0883af1a4d66f2878662b0f1a6d 2044 ruby optional ruby-faker_1.6.6-1.dsc
 973687840e8671ed96841c4b0e1bf0bf 279776 ruby optional 
ruby-faker_1.6.6.orig.tar.gz
 09a9c99954a3a6b611b2889af2c1cd62 3292 ruby optional 
ruby-faker_1.6.6-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYF34LAAoJEM4fnGdFEsIqcv0P/3Dv8wp3n51P8BvDw2dzQUBs
1ZlxT6pplTNTqr6fbfhn4MRVb8gPqXtDMopksb18jxRUv/guxGF10lpugYcg6xwW
40XGwvCQ9nS6Hqq7GJ1Z1QR2bed5M/v2yjcPaksW3dqXBk2GIrLuQqUIue6GbQQo
SizSou/YYis1R10zuHb8gWKsF5DBHC4jsDglqNy7IQ0L4oyGZIQRAuzdRVkDxa+/
57A+MelTvjUIYiWrKWq8d8X4

Processed: [bts-link] source package esniper

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package esniper
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #841748 (http://bugs.debian.org/841748)
> # Bug title: esniper: needs update for recent eBay changes
> #  * https://sourceforge.net/p/esniper/bugs/709/
> #  * remote status changed: open -> closed-fixed
> #  * closed upstream
> tags 841748 + fixed-upstream
Bug #841748 [esniper] esniper: needs update for recent eBay changes
Added tag(s) fixed-upstream.
> usertags 841748 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 841748 + status-closed-fixed
There were no usertags set.
Usertags are now: status-closed-fixed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
841748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#841614: node-es6-promise: FTBFS: compile-modules shows help

[Julien Puydt]

Hi,

On 31/10/2016 08:01, Lucas Nussbaum wrote:

On 29/10/16 at 11:14 +0200, Julien Puydt wrote:

Hi,

I tried to "pbuilder create" a new base.tgz, but it still had tzdata and
lsb-base, so I had to "pbuilder login --save-after-login" and remove them by
hand using "dpkg --purge" (then "apt-get autoremove" that did nothing). I
still had no problem building node-es6-promise.

How can I get the clean, minimal and up-to-date chroot you mention in your
report?


Hi Julien,

You can install debfoster in the chroot, and then run
debfoster -o UseRecommends=no -o MaxPriority=required

to clean up the chroot from non-essential packages.


I made several tests with your debfoster line :

(*) if I let dpkg-dev go, pbuilder can't even try to compile packages 
because it's missing dpkg-architecture


(*) if I let gcc go, dpkg-architecture can't determine the system type ;

(*) if I let aptitude go, pbuilder can't install the build deps ;

(*) if I let build-essential go, pbuilder will install the build deps, 
but dpkg-buildpackage will fail because of unmet build dependencies (on 
build-essential: native !)


So I kept apt, aptitude and build-essential : no problem building 
node-es6-promise with pbuilder.


Since I really wanted to fix that bug, I thought I could get a smaller 
chroot by doing things by hand -- after all I have less needs than 
pbuilder : using debfoster I kept only apt, then installed nano so I 
could edit the sources.list (enable the deb-src line) and apt-get 
update, then installed the build-dep for node-es6-promise, apt-get 
source node-es6-promise, then dpkg-buildpackage -b -us -uc... no problem!


I don't manage to reproduce the failure, and I don't know what I could 
try next. Do you have more ideas?


Snark on #debian-js

Processed: [bts-link] source package src:pythonmagick

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:pythonmagick
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #840428 (http://bugs.debian.org/840428)
> # Bug title: pythonmagick: FTBFS with newer experimental version of 
> imagemagick
> #  * https://github.com/ImageMagick/PythonMagick/issues/5
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 840428 + fixed-upstream
Bug #840428 [src:pythonmagick] pythonmagick: FTBFS with newer experimental 
version of imagemagick
Added tag(s) fixed-upstream.
> usertags 840428 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package src:ettercap

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:ettercap
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #828298 (http://bugs.debian.org/828298)
> # Bug title: ettercap: FTBFS with openssl 1.1.0
> #  * https://github.com/Ettercap/ettercap/issues/739
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 828298 + fixed-upstream
Bug #828298 {Done: Gianfranco Costamagna } 
[src:ettercap] ettercap: FTBFS with openssl 1.1.0
Added tag(s) fixed-upstream.
> usertags 828298 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 828298 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
828298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#774082: What is the solution/workaround ?

[Benoit Plessis]

Hi,

I am also affected by this issue, where the initramfs only activate the
root/usr lv's

what is the recommended jessie workaround, disabling lvmetad ?

-- 
Benoit Plessis +33 6 77 42 78 32
4096R/44E6FA9A 486D 2804 3EAB 3D74 5D05  826D 997F 26D9 44E6 FA9A

Bug#842722: [kgb-maintainers] Bug#842722: kgb-bot: FTBFS (failing tests)

[gregor herrmann]

Control: tag -1 + confirmed

On Mon, 31 Oct 2016 16:42:43 +, Santiago Vila wrote:

> Package: src:kgb-bot
> Version: 1.34-1
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

I'm seeing the same failures when building in a sid amd64 cowbuilder
chroot:
 
> # trying port 5392
> # test bot listening on 127.0.0.1:5392, pid: 2634  at t/TestBot.pm line 117.
> fatal:  ??     ??
> merge allnew: command returned error: 128
> # stopping test bot, pid 2634
> # Removing directory /<>/t/bot
> # Tests were run but no plan was declared and done_testing() was not seen.
> t/52-client-git.t .. 
> Initialized empty Git repository in /tmp/kgb-UxHeMBc/there.git/
> Initialized empty Git repository in /tmp/kgb-UxHeMBc/here/.git/
> ok 1 - local repository allocated
> ok 2 - An object of class 'Git' isa 'Git'
> ok 3 - An object of class 'App::KGB::Client::Git' isa 'App::KGB::Client::Git'
> ok 4 - post-receive hook logs
> ok 5 - commit 1 present
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10
> ok 11
> ok 12 - commit 2 present
> ok 13
> ok 14
> ok 15
> ok 16
> ok 17
> ok 18
> ok 19
> ok 20 - commit 3 present
> ok 21 - commit 3 branch is "master"
> ok 22
> ok 23
> ok 24
> ok 25
> ok 26
> ok 27 - commit 4 present
> ok 28
> ok 29
> ok 30
> ok 31
> ok 32
> ok 33
> ok 34
> ok 35 - commit 5 present
> ok 36 - commit 5 id
> ok 37 - commit 5 branch
> ok 38 - commit 5 log
> ok 39 - commit 5 author
> ok 40 - commit 5 changes
> ok 41 - commit 6 present
> ok 42
> ok 43
> ok 44
> ok 45
> ok 46
> ok 47
> ok 48 - annotated tag here
> ok 49
> ok 50
> ok 51
> ok 52
> ok 53 - annotated tag log
> ok 54 - hollow branch described
> ok 55 - hollow commit is 2884f56
> ok 56 - hollow commit branch is 'hollow'
> ok 57 - no changes in hollow commit
> ok 58 - hollow commit log is 'branch created'
> ok 59 - hollow branch has no commits
> ok 60 - UTF-8 commit exists
> ok 61
> ok 62
> ok 63
> ok 64
> ok 65 - empty branch creation commit exists
> ok 66 - empty branch name
> ok 67 - empty branch log
> ok 68
> Dubious, test returned 254 (wstat 65024, 0xfe00)
> All 68 subtests passed 

Interestingly this has worked not long ago when I uploaded 1.34-1
(ok, a month ago already).
Let's find out what has changed behind our back :)


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Leonard Cohen: Tower of Song


signature.asc
Description: Digital Signature

Processed: Re: [kgb-maintainers] Bug#842722: kgb-bot: FTBFS (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #842722 [src:kgb-bot] kgb-bot: FTBFS (failing tests)
Added tag(s) confirmed.

-- 
842722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#842722: kgb-bot: FTBFS (failing tests)

[Santiago Vila]

Package: src:kgb-bot
Version: 1.34-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Checking prerequisites...
  test_requires:
!  Test::Perl::Critic is not installed

ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
of the modules indicated above before proceeding with this installation

Run 'Build installdeps' to install missing prerequisites.

Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'App-KGB' version '1.34'
   dh_auto_build -i
perl Build
Building App-KGB
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
LANG=bg_BG.utf8 LC_ALL=bg_BG.utf8 dh_auto_test
perl Build test --verbose 1
t/00-compile.t . 
ok 1 - blib/lib/App/KGB.pm compiles
ok 2 - blib/lib/WWW/Shorten/Debli.pm compiles
ok 3 - blib/lib/App/KGB/Client.pm compiles
ok 4 - blib/lib/App/KGB/API.pm compiles
ok 5 - blib/lib/App/KGB/Commit.pm compiles
ok 6 - blib/lib/App/KGB/Painter.pm compiles
ok 7 - blib/lib/App/KGB/Change.pm compiles
ok 8 - blib/lib/App/KGB/Commit/Tag.pm compiles
ok 9 - blib/lib/App/KGB/Client/ServerRef.pm compiles
ok 10 - blib/lib/App/KGB/Client/Subversion.pm compiles
ok 11 - blib/lib/App/KGB/Client/Fake.pm compiles
ok 12 - blib/lib/App/KGB/Client/RelayMsg.pm compiles
ok 13 - blib/lib/App/KGB/Client/Git.pm compiles
ok 14 - blib/lib/App/KGB/Client/CVS.pm compiles
ok 15 - blib/lib/JSON/RPC/Client/Any.pm compiles
1..15
ok
script/kgb-add-project syntax OK
script/kgb-ci-report syntax OK
script/kgb-bot syntax OK
script/kgb-client syntax OK
script/kgb-split-config syntax OK
t/00-compile_scripts.t . 
1..5
ok 1 - script/kgb-add-project compiles
ok 2 - script/kgb-ci-report compiles
ok 3 - script/kgb-bot compiles
ok 4 - script/kgb-client compiles
ok 5 - script/kgb-split-config compiles
ok
t/00-compile_shell_scripts.t ... 
ok 1
1..1
ok
t/30-bot-changes.t . 
ok 1
ok 2
ok 3
1..3
ok
# trying port 5392
# test bot listening on 127.0.0.1:5392, pid: 2593  at t/TestBot.pm line 117.
# Test bot started on 127.0.0.1:5392
# $>=924 $<=924 $ENV{USER}=buildd getpwuid($>)=buildd
# stopping test bot, pid 2593
# Removing directory /<>/t/bot
t/50-client.t .. 
Checked out revision 0.
A file
Adding file
Transmitting file data .done
Committing transaction...
Committed revision 1.
Sendingfile
Transmitting file data .done
Committing transaction...
Committed revision 2.
D file
A file
Replacing  file
Transmitting file data .done
Committing transaction...
Committed revision 3.
ok 1 - Test repository prepared
ok 2 - An object of class 'App::KGB::Client::Subversion' isa 
'App::KGB::Client::Subversion'
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 25 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 26 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 27 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 28 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 29 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 30 # skip UTF-8 locale needed for the test with UTF-8 commit message
ok 31
1..31
ok
t/51-client_branch_module.t  
ok 1 - An object of class 'App::KGB::Client::Subversion' isa 
'App::KGB::Client::Subversion'
ok 2 - branch detection in [module and branch] (/kgb/trunk/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 3 - module detection in [module and branch] (/kgb/trunk/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 4 - file list for [module and branch]
ok 5 - branch detection in [branch and module] (/trunk/kgb/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 6 - module detection in [branch and module] (/trunk/kgb/some/file) =~ 
(^/([^/]+)/([^/]+)/)
ok 7 - file list for [branch and module]
ok 8 - branch detection in [branch only] (/trunk/some/file) =~ (^/([^/]+)/())
ok 9 - module detection in [branch only] (/trunk/some/file) =~ (^/([^/]+)/())
ok 10 - file list for [branch only]
ok 11 - branch detection in [module only] (/website/some/file) =~ 
(^/(website)/())
ok 12 - module detection in [module only] (/website/some/file) =~ 
(^/(website)/())
ok 13 - file list for [module only]
ok 14 - branch detection in [real 

Bug#842723: python-pytils: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-pytils
Version: 0.3-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh --with python2,python3 build-indep --buildsystem=pybuild
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)

[... snipped ...]

  File "/<>/pytils/test/test_dt.py", line 182, in 
testDOTIWDefaultToTimeAcc1
self.ckDefaultToTime("2day_ago", 1, u"позавчера")
  File "/<>/pytils/test/test_dt.py", line 95, in ckDefaultToTime
self.assertEquals(res, estimated)
AssertionError: u'\u0432\u0447\u0435\u0440\u0430' != 
u'\u043f\u043e\u0437\u0430\u0432\u0447\u0435\u0440\u0430'
- \u0432\u0447\u0435\u0440\u0430
+ \u043f\u043e\u0437\u0430\u0432\u0447\u0435\u0440\u0430
? 


==
FAIL: testDOTIWDefaultToTimeAcc2 
(pytils.test.test_dt.DistanceOfTimeInWordsTestCase)
--
Traceback (most recent call last):
  File "/<>/pytils/test/test_dt.py", line 211, in 
testDOTIWDefaultToTimeAcc2
self.ckDefaultToTime("2day_ago", 2, u"позавчера")
  File "/<>/pytils/test/test_dt.py", line 95, in ckDefaultToTime
self.assertEquals(res, estimated)
AssertionError: u'1 \u0434\u0435\u043d\u044c 23 \u0447\u0430\u0441\u0430 
\u043d\u0430\u0437\u043 [truncated]... != 
u'\u043f\u043e\u0437\u0430\u0432\u0447\u0435\u0440\u0430'
- 1 \u0434\u0435\u043d\u044c 23 \u0447\u0430\u0441\u0430 
\u043d\u0430\u0437\u0430\u0434
+ \u043f\u043e\u0437\u0430\u0432\u0447\u0435\u0440\u0430


==
FAIL: testDOTIWDefaultToTimeAcc3 
(pytils.test.test_dt.DistanceOfTimeInWordsTestCase)
--
Traceback (most recent call last):
  File "/<>/pytils/test/test_dt.py", line 243, in 
testDOTIWDefaultToTimeAcc3
u"2 дня 0 часов 40 минут назад")
  File "/<>/pytils/test/test_dt.py", line 95, in ckDefaultToTime
self.assertEquals(res, estimated)
AssertionError: u'1 \u0434\u0435\u043d\u044c 23 \u0447\u0430\u0441\u0430 40 
\u043c\u0438\u043d\u [truncated]... != u'2 \u0434\u043d\u044f 0 
\u0447\u0430\u0441\u043e\u0432 40 \u043c\u0438\u043d\u0 [truncated]...
- 1 \u0434\u0435\u043d\u044c 23 \u0447\u0430\u0441\u0430 40 
\u043c\u0438\u043d\u0443\u0442 \u043d\u0430\u0437\u0430\u0434
? ^  - ^
+ 2 \u0434\u043d\u044f 0 \u0447\u0430\u0441\u043e\u0432 40 
\u043c\u0438\u043d\u0443\u0442 \u043d\u0430\u0437\u0430\u0434
? ^   ^^^^^


--
Ran 71 tests in 0.039s

FAILED (failures=5)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).

Thanks.

Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

[Santiago Vila]

Package: src:jayway-jsonpath
Version: 2.0.0-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle --with maven-repo-helper
   dh_testdir -i -O--buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- jar install -x :json-path-web-test:jar -x :json-path:javadoc
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian jar install -x :json-path-web-test:jar -x :json-path:javadoc
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using BuildScriptTransformer.
Loading the Maven rules...
Compiling settings file '/<>/settings.gradle' using 
SubsetScriptTransformer.
Compiling settings file '/<>/settings.gradle' using 
BuildScriptTransformer.
Settings evaluated using settings file '/<>/settings.gradle'.
Projects loaded. Root project using build file '/<>/build.gradle'.
Included projects: [root project 'json-path-parent', project ':json-path', 
project ':json-path-assert', project ':json-path-web-test']
Keep-alive timer started
Adding Debian repository to project 'json-path-parent'
Adding Debian repository to project 'json-path'
Adding Debian repository to project 'json-path-assert'
Adding Debian repository to project 'json-path-web-test'
Evaluating root project 'json-path-parent' using build file 
'/<>/build.gradle'.
Compiling build file '/<>/build.gradle' using 
SubsetScriptTransformer.
Ignoring me.champeau.gradle:gradle-javadoc-hotfix-plugin:jar:0.1
Ignoring com.github.jengelman.gradle.plugins:shadow:jar:1.2.1
Ignoring me.champeau.gradle:japicmp-gradle-plugin:jar:0.1.0
Compiling build file '/<>/build.gradle' using 
BuildScriptTransformer.
Evaluating project ':json-path' using build file 
'/<>/json-path/build.gradle'.
Compiling build file '/<>/json-path/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/json-path/build.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/gradle/publishMaven.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/gradle/publishMaven.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'json-path'
Configuring javadoc links
Evaluating project ':json-path-assert' using build file 
'/<>/json-path-assert/build.gradle'.
Compiling build file '/<>/json-path-assert/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/json-path-assert/build.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'json-path-assert'
Configuring javadoc links
Evaluating project ':json-path-web-test' using build file 
'/<>/json-path-web-test/build.gradle'.
Compiling build file '/<>/json-path-web-test/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/json-path-web-test/build.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'json-path-web-test'
Configuring javadoc links
All projects evaluated.
Selected primary task 'jar' from project :
Selected primary task 'install' from project :
Tasks to be executed: [task ':json-path:compileJava', task 
':json-path:processResources', task ':json-path:classes', task 
':json-path:debianMavenPom', task ':json-path:jar', task 
':json-path-assert:compileJava', task ':json-path-assert:processResources', 
task ':json-path-assert:classes', task ':json-path-assert:debianMavenPom', task 
':json-path-assert:jar', task ':json-path:javadocJar', task 
':json-path:sourcesJar', task ':json-path:signArchives', task 
':json-path:install', task ':json-path-assert:javadoc', task 
':json-path-assert:javadocJar', task ':json-path-assert:sourcesJar', task 
':json-path-assert:signArchives', task ':json-path-assert:install', task 
':json-path-web-test:startScripts', task ':json-path-web-test:distTar', task 
':json-path-web-test:distZip', task ':json-path-web-test:compileJava', task 
':json-path-web-test:processResources', task ':json-path-web-test:classes', 
task ':json-path-web-test:javadoc', task ':json-path-web-test:javadocJar', task 
':json-path-web-test:sou
 rcesJar', task ':json-path-web-test:signArchives', task 
':json-path-web-test:install']
:json-path:compileJava (Thread[main,5,main]) started.
:json-path:compileJava
Replacing net.minidev:json-smart:jar:2.1.1  ->  

Bug#841420: Patch to allow build

[Arthur Gautier]

On Sun, Oct 30, 2016 at 01:32:14AM -0300, Raymond Burkholder wrote:
> Step 1:
> 
> scripts/config --disable CC_STACKPROTECTOR_STRONG

This cannot be a serious step.

The original commit message and message on LKML:
http://lkml.iu.edu/hypermail/linux/kernel/1312.2/03960.html

This is a step forward security, we can not just disable it on
production systems.



-- 
\o/ Arthur
 G  Gandi.net

Bug#828298: marked as done (ettercap: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 16:33:38 +
with message-id 
and subject line Bug#828298: fixed in ettercap 1:0.8.2-3
has caused the Debian Bug report #828298,
regarding ettercap: FTBFS with openssl 1.1.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
828298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ettercap
Version: 0.8.2-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/ettercap_0.8.2-2_amd64-20160529-1417

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: ettercap
Source-Version: 1:0.8.2-3

We believe that the bug you reported is fixed in the latest version of
ettercap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 828...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated ettercap 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 31 Oct 2016 16:36:37 +0100
Source: ettercap
Binary: ettercap-common ettercap-text-only ettercap-graphical ettercap-dbg
Architecture: source
Version: 1:0.8.2-3
Distribution: unstable
Urgency: low
Maintainer: Barak A. Pearlmutter 
Changed-By: Gianfranco Costamagna 
Description:
 ettercap-common - Multipurpose sniffer/interceptor/logger for switched LAN
 ettercap-dbg - Debug symbols for Ettercap
 ettercap-graphical - Ettercap GUI-enabled executable
 ettercap-text-only - Ettercap console-mode executable
Closes: 828298
Changes:
 ettercap (1:0.8.2-3) unstable; urgency=low
 .
   * debian/patches/740.patch: fix openssl 1.1 build failure
 with upstream patch (Closes: #828298)
   * Bump compat level to 10.
   * Use my d.org mail address
   * Bump std-version to 3.9.8, no changes required.
Checksums-Sha1:
 0ed864f9faac2f95aefb37dd008cb308fc17564a 2417 ettercap_0.8.2-3.dsc
 8b59ad84701853ddebd176f00c5b8837e77d141b 13688 ettercap_0.8.2-3.debian.tar.xz
Checksums-Sha256:
 edcfeb711099083015ba7931cb4284a4b85b91ca0bf74169560681ec3f5e3313 2417 
ettercap_0.8.2-3.dsc
 c59eea154ba1385ea00ceb605be747a320fa034d6e6189eb5220e6619546c594 13688 
ettercap_0.8.2-3.debian.tar.xz
Files:
 9e4afea9f6b50e15acfba730dc9310f2 2417 net optional ettercap_0.8.2-3.dsc
 d6503d52ec7be6b4e7c8591cb3686317 13688 net optional 
ettercap_0.8.2-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYF2WhAAoJEPNPCXROn13ZiIAP/A/eJ01MP0kKRJ3arwlY1UH3
tFIM87UnUNnGQ/X5ziGPLgTECETpkB2JA25SFV28kstamRYQia0+mbd+HVu9GdxX
1GkSDZ7yOk48Hte4JpHl0d9AVPl7m5WMEHFONhJBB6QhA++N17ypU8OhE24UUFFq
yz8jXQVf0doki+opVBQx1ZqmZDqWi+2LUawOcx4poGjtUcqbfJKvBabJskY8HAtj
9zKx6pesf1JeUrSuvACfBANary4fQtd1V8iEIt6fZR2p8m/yllaUva2IT0IkYh76
By7Bcx4HrBVuWEyaKXaqcNRRMPJ33ik5CjFULDMze+cJIaR1duspMnfupcDlUdGa
whab6eVMCap4yba1VJhy4L7g5x7+6g5L8NWuFZBfvvQ3Yhp3OSHkVuziyQYvJ0Px
n7+S5lHCrft4o+c3PZgLs3ycHTOhlAK83P8S8fR8jIIe6wvfIwsL5i47p3eG/J/C
PQJ26R0YT2ag3zQEK+RcnjItCn71L2DZymza0TIgNk/UWSnX+OWo6LZHKDFc8XfQ
ifVUDHhOTBX6LCJgdbVnmg1gPXZnVphh++YjSK2FLQLkTl69MHNVYtuUxDXqnYwP
D9/SBdCuEHEt7c/rkZC7yp92MH0QtYdebcw/+VlGKFa1PHcE2yxPyOyrYbGRN6Qi
elXTTOGnVLlLqVy1DcXy
=zUxK
-END PGP SIGNATURE End Message ---

Bug#828584: marked as done (unbound: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 16:01:04 +
with message-id 
and subject line Bug#828584: fixed in unbound 1.5.10-1
has caused the Debian Bug report #828584,
regarding unbound: FTBFS with openssl 1.1.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
828584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unbound
Version: 1.5.8-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/unbound_1.5.8-1_amd64-20160529-1547

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: unbound
Source-Version: 1.5.10-1

We believe that the bug you reported is fixed in the latest version of
unbound, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 828...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert Edmonds  (supplier of updated unbound package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 04 Oct 2016 03:43:45 -0400
Source: unbound
Binary: libunbound-dev libunbound2 python-unbound python3-unbound unbound 
unbound-anchor unbound-host
Architecture: source amd64
Version: 1.5.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Robert Edmonds 
Description:
 libunbound-dev - static library, header files, and docs for libunbound
 libunbound2 - library implementing DNS resolution and validation
 python-unbound - library implementing DNS resolution and validation (Python 
bindin
 python3-unbound - library implementing DNS resolution and validation (Python3 
bindi
 unbound- validating, recursive, caching DNS resolver
 unbound-anchor - utility to securely fetch the root DNS trust anchor
 unbound-host - reimplementation of the 'host' command
Closes: 828584 828699 835972
Changes:
 unbound (1.5.10-1) unstable; urgency=medium
 .
   * New upstream version 1.5.10
 - Fixes FTBFS with OpenSSL 1.1.0 (Closes: #828584)
   * debian/: Build libunbound against nettle (Closes: #828699)
   * debian/: Support Python 3 (Closes: #835972)
   * debian/rules: Install libunbound.pc into the libunbound-dev package
   * debian/copyright: Update
Checksums-Sha1:
 34c7aa45d44c83f34dffcf3b0321e299f93f6bad 2514 unbound_1.5.10-1.dsc
 6102849c400db3a4195b1f16df8f312568a6ec57 4941299 unbound_1.5.10.orig.tar.gz
 42970ed11fc657f0ffb5e98065b758285526fabb 15740 unbound_1.5.10-1.debian.tar.xz
 6c302410bceab90fbc979ab943428d54a25f0c38 5098808 
libunbound-dev_1.5.10-1_amd64.deb
 93ebcc3abb978a37df00bd6f78f2f24a1588cce7 802104 
libunbound2-dbgsym_1.5.10-1_amd64.deb
 23a07411c32126df474e7013e43a3935b222cafc 338224 libunbound2_1.5.10-1_amd64.deb
 e6b4cd33eb2079679babf7b3368bf3eb606268c7 81282 
python-unbound-dbgsym_1.5.10-1_amd64.deb
 f5e55ed330dd7352e4010046fbddeb0a895e5c06 132236 
python-unbound_1.5.10-1_amd64.deb
 aa1fbd268db045e04dceb5029a783c1c09c6096d 77232 
python3-unbound-dbgsym_1.5.10-1_amd64.deb
 7d9842bc523d8468962079f28a9eec118ed0ddc5 132050 
python3-unbound_1.5.10-1_amd64.deb
 e8ff321ebf9c4b48c5a03cd249e21ed9c55d63a3 86166 
unbound-anchor-dbgsym_1.5.10-1_amd64.deb
 030185f1094918f3f4585a1d17eee955b0cd6d9d 119102 
unbound-anchor_1.5.10-1_amd64.deb
 eeb09f6044da14285697235f26cac836258f0854 1280906 
unbound-dbgsym_1.5.10-1_amd64.deb
 8e5239efc00c5fce059d58e60052247611df5507 46990 
unbound-host-dbgsym_1.5.10-1_amd64.deb
 da8c9923d255764856d08f93ee0d78533e16dbeb 117450 unbound-host_1.5.10-1_amd64.deb
 d0bb5e7c1dfcd99743b39fc1cbfe34d208482e98 492450 unbound_1.5.10-1_amd64.deb
Chec

Bug#811988: marked as done (libcgicc: FTBFS with GCC 6: call overloaded is ambiguous)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 16:00:24 +
with message-id 
and subject line Bug#811988: fixed in libcgicc 3.2.16-0.1
has caused the Debian Bug report #811988,
regarding libcgicc: FTBFS with GCC 6: call overloaded is ambiguous
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
811988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcgicc
Version: 3.2.9-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-overloaded-ambiguous

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /bin/bash ../libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
> -DHAVE_CONFIG_H -I. -I.. -I.. -x c++-Wall -W -pedantic -g -O2 -MT 
> libcgicc_la-Cgicc.lo -MD -MP -MF .deps/libcgicc_la-Cgicc.Tpo -c -o 
> libcgicc_la-Cgicc.lo `test -f 'Cgicc.cpp' || echo './'`Cgicc.cpp
> libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I.. -x c++ 
> -Wall -W -pedantic -g -O2 -MT libcgicc_la-Cgicc.lo -MD -MP -MF 
> .deps/libcgicc_la-Cgicc.Tpo -c Cgicc.cpp  -fPIC -DPIC -o 
> .libs/libcgicc_la-Cgicc.o
> Cgicc.cpp: In member function 'bool cgicc::Cgicc::findEntries(const string&, 
> bool, std::vector&) const':
> Cgicc.cpp:328:54: error: call of overloaded 
> 'copy_if(std::vector::const_iterator, 
> std::vector::const_iterator, 
> std::back_insert_iterator >, 
> cgicc::FE_nameCompare)' is ambiguous
>   std::back_inserter(result),FE_nameCompare(param));
>   ^
> 
> Cgicc.cpp:99:3: note: candidate: Out cgicc::copy_if(In, In, Out, Pred) [with 
> In = __gnu_cxx::__normal_iterator std::vector >; Out = 
> std::back_insert_iterator >; Pred = 
> cgicc::FE_nameCompare]
>copy_if(In first,
>^~~
> 
> In file included from /usr/include/c++/6/algorithm:62:0,
>  from Cgicc.cpp:29:
> /usr/include/c++/6/bits/stl_algo.h:734:5: note: candidate: _OIter 
> std::copy_if(_IIter, _IIter, _OIter, _Predicate) [with _IIter = 
> __gnu_cxx::__normal_iterator std::vector >; _OIter = 
> std::back_insert_iterator >; _Predicate = 
> cgicc::FE_nameCompare]
>  copy_if(_InputIterator __first, _InputIterator __last,
>  ^~~
> 
> Cgicc.cpp:332:56: error: call of overloaded 
> 'copy_if(std::vector::const_iterator, 
> std::vector::const_iterator, 
> std::back_insert_iterator >, 
> cgicc::FE_valueCompare)' is ambiguous
>   std::back_inserter(result), FE_valueCompare(param));
> ^
> 
> Cgicc.cpp:99:3: note: candidate: Out cgicc::copy_if(In, In, Out, Pred) [with 
> In = __gnu_cxx::__normal_iterator std::vector >; Out = 
> std::back_insert_iterator >; Pred = 
> cgicc::FE_valueCompare]
>copy_if(In first,
>^~~
> 
> In file included from /usr/include/c++/6/algorithm:62:0,
>  from Cgicc.cpp:29:
> /usr/include/c++/6/bits/stl_algo.h:734:5: note: candidate: _OIter 
> std::copy_if(_IIter, _IIter, _OIter, _Predicate) [with _IIter = 
> __gnu_cxx::__normal_iterator std::vector >; _OIter = 
> std::back_insert_iterator >; _Predicate = 
> cgicc::FE_valueCompare]
>  copy_if(_InputIterator __first, _InputIterator __last,
>  ^~~
> 
> Makefile:534: recipe for target 'libcgicc_la-Cgicc.lo' failed
> make[3]: *** [libcgicc_la-Cgicc.lo] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: libcgicc
Source-Version: 3.2.16-0.1

We believe that the bug you reported is fixed in the latest version of
libcgicc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Pircher  (supplier of updated libcgicc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
a

Bug#842591: debootstrap-udeb: fails to validate InRelease (BADSIG)

[Lennart Sorensen]

On Mon, Oct 31, 2016 at 04:18:55PM +0100, Cyril Brulebois wrote:
> No, the “certainly did” and “worked fine” bits are wrong.
> 
> And that's not just me, we've had users report it, Philip Hands saw it
> as well. So no it did *NOT* work (in the specific case where it actually
> matters).

Yes, turns out sed doesn't do \a, but it does work if \a in sed is
replaced by [[:cntrl:]].  Doesn't make the line any prettier.

> Well that's the case in Debian right now, even in d-i! So your “busybox
> head does not appear to support it.” was wrong (that happens, no big
> deal), and I'm not so fond of being called a liar when I report test
> results for stuff I actually checked.

Well the version I looked at didn't have it, so apparently it was slightly
more than 3 years old.  It is a recent addition.

> Anyway, back to getting the next d-i release ready now that this issue
> is fixed.

Yep.

-- 
Len Sorensen

Processed: limit source to dacs, tagging 737641, tagging 828277, tagging 729475

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source dacs
Limiting to bugs with field 'source' containing at least one of 'dacs'
Limit currently set to 'source':'dacs'

> tags 737641 + pending
Bug #737641 [dacs] dacs: [PATCH] Enable build on newer arches
Added tag(s) pending.
> tags 828277 + pending
Bug #828277 [src:dacs] dacs: FTBFS with openssl 1.1.0
Added tag(s) pending.
> tags 729475 + pending
Bug #729475 [dacs] dacs: Missing dacsinit command
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
729475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729475
737641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737641
828277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#829477: courier-mta: fails to install: Invalid command 'gendh'

[Stefan Hornburg (Racke)]

On 07/03/2016 07:07 PM, Andreas Beckmann wrote:
> Package: courier-mta
> Version: 0.76.1-3+exp1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
> 
>>From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package courier-mta.
>   (Reading database ... 
> (Reading database ... 10293 files and directories currently installed.)
>   Preparing to unpack .../courier-mta_0.76.1-3+exp1_amd64.deb ...
>   Adding 'diversion of /usr/bin/addcr to /usr/bin/addcr.ucspi-tcp by 
> courier-mta'
>   Adding 'diversion of /usr/share/man/man1/addcr.1.gz to 
> /usr/share/man/man1/addcr.ucspi-tcp.1.gz by courier-mta'
>   Unpacking courier-mta (0.76.1-3+exp1) ...
>   Setting up courier-mta (0.76.1-3+exp1) ...
>   update-alternatives: using /usr/bin/lockmail.courier to provide 
> /usr/bin/lockmail (lockmail) in auto mode
>   update-alternatives: using /usr/bin/preline.courier to provide 
> /usr/bin/preline (preline) in auto mode
>   /run/courier/esmtpd.pid.lock: No such file or directory
>   Generating a 4096 bit RSA private key
>   ..++
>   
> .++
>   writing new private key to '/etc/courier/esmtpd.pem'
>   -
>   Invalid command 'gendh'; type "help" for a list.
>   dpkg: error processing package courier-mta (--configure):
>subprocess installed post-installation script returned error exit status 1
>   Errors were encountered while processing:
>courier-mta
> 
> 
> cheers,
> 
> Andreas
> 

I believe this line in the script /usr/lib/courier/mkesmtpdcert
causes the error:

/usr/bin/openssl gendh -rand "$PEMFILE".rand 512 >>"$PEMFILE" || cleanup

Why openssl doesn't know about it on piuparts eludes me.

Regards
 Racke

Bug#842586: git: FTBFS on mips64el (fatal: Out of memory, getdelim failed)

[James Cowgill]

Hi,

I've had a bit of a look at this bug. I've now tried to build git on two
different machines running different hardware (octeon and loongson) and
it built fine both times so I'm not too sure what's going on here.

All 3 builds which failed were Loongson machines running 3.16 kernels.
While I know they have FPU problems, I wouldn't have thought that would
give an out of memory error.

It would be good to get the package rebuilt on an Octeon to see if it is
a hardware problem.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#842500: marked as done (python-launchpadlib: FTBFS: error: Could not find suitable distribution for Requirement.parse('secretstorage'))

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 15:25:16 +
with message-id 
and subject line Bug#842500: fixed in python-keyring 10.0.2-2
has caused the Debian Bug report #842500,
regarding python-launchpadlib: FTBFS: error: Could not find suitable 
distribution for Requirement.parse('secretstorage')
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
842500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-launchpadlib
Version: 1.10.4-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-launchpadlib fails to build from source in unstable/amd64:

  […]


  I: pybuild base:184: python2.7 setup.py test 
  running test
  /usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py:359: 
UserWarning: Unbuilt egg for launchpadlib [unknown version] 
(/home/lamby/temp/cdt.20161029191345.tOhqeow9yO.db.python-launchpadlib/python-launchpadlib-1.10.4/src)
self.local_index = Environment(self.shadow_path + sys.path)
  Searching for secretstorage
  
  Note: Bypassing https://pypi.python.org/simple/secretstorage/ (disallowed 
host; see http://bit.ly/1dg9ijs for details).
  
  Couldn't find index page for 'secretstorage' (maybe misspelled?)
  Scanning index of all packages (this may take a while)
  
  Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).
  
  No local packages or working download links found for secretstorage
  error: Could not find suitable distribution for 
Requirement.parse('secretstorage')
  E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
  debian/rules:9: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161029191345.tOhqeow9yO.db.python-launchpadlib/python-launchpadlib-1.10.4'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


python-launchpadlib.1.10.4-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-keyring
Source-Version: 10.0.2-2

We believe that the bug you reported is fixed in the latest version of
python-keyring, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 842...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated python-keyring 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 31 Oct 2016 16:29:42 +0300
Source: python-keyring
Binary: python-keyring python3-keyring
Architecture: source
Version: 10.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Description:
 python-keyring - store and access your passwords safely
 python3-keyring - store and access your passwords safely - Python 3 version of 
the
Closes: 842500
Changes:
 python-keyring (10.0.2-2) unstable; urgency=medium
 .
   * Promote python[3]-secretstorage from Recommends to Depends,
 following upstream (closes: #842500).
Checksums-Sha1:
 a95a7895381601eaa4a85b561b11a26297990a43 2343 python-keyring_10.0.2-2.dsc
 63315340f879c734b925093fc7e8223f166c51f1 36587 
python-keyring_10.0.2.orig.tar.gz
 22c5bf03b6dfea66a4c72ddbeac6953350b006c0 7764 
python-keyring_10.0.2-2.debian.tar.xz
Checksums-Sha256:
 0d06ce2df11375f588c6dc1f4aba58c79d2fa781ac6e6a74180cb8745a8bc205 2343 
python-keyring_10.0.2-2.dsc
 91c31fd805b3ce6343406c7c51437f7505f3e9abb6e14ccac8242ea1fc912d77 36587 
python-keyring_10.0.2.orig.tar.gz
 6219704953a51ba20c3dc7af498a83ec066a8e3191a6e78e2c1b753b389e 7764 
python-keyring_10.0.2-2.debian.tar.xz
Files:
 1e8f726ccaa1e13060ed98789c3d4859 2343 python optional 

Bug#842591: debootstrap-udeb: fails to validate InRelease (BADSIG)

[Cyril Brulebois]

Lennart Sorensen  (2016-10-31):
> On Sun, Oct 30, 2016 at 05:28:57PM +0100, Cyril Brulebois wrote:
> > The (re)addition of InRelease support broke debootstrap(-udeb) in a d-i
> > context. The sed|tr|sed dance doesn't kill the final newline, which
> > leads to a BAD signature.
> 
> The one I proposed certainly did.  It worked fine and was portable.
> Just a touch ugly perhaps.

No, the “certainly did” and “worked fine” bits are wrong.

And that's not just me, we've had users report it, Philip Hands saw it
as well. So no it did *NOT* work (in the specific case where it actually
matters).

> > My original proposal was to use head -c -1, which while not specified by
> > posix actually just works. Reasons include:
> >  1. Tests agree.
> >  2. busybox's coreutils/head.c has:
> > case 'c':
> > count_bytes = 1;
> > …
> > if (negative_N) {
> > if (count_bytes) {
> > print_except_N_last_bytes(fp, 
> > count);
> > } else {
> > print_except_N_last_lines(fp, 
> > count);
> > }
> > } else {
> > print_first_N(fp, count, count_bytes);
> > }
> 
> Well only if you have ENABLE_FEATURE_FANCY_HEAD and it was only added
> in 2013, so rather recent addition.

Well that's the case in Debian right now, even in d-i! So your “busybox
head does not appear to support it.” was wrong (that happens, no big
deal), and I'm not so fond of being called a liar when I report test
results for stuff I actually checked.

Anyway, back to getting the next d-i release ready now that this issue
is fixed.


KiBi.


signature.asc
Description: Digital signature

Processed: closing 838216

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 838216 12.14.60-1
Bug #838216 [chef] Could not find 'chef-zero' (~> 4.5) - did find: 
[chef-zero-5.0.0] (Gem::LoadError)
Marked as fixed in versions chef/12.14.60-1.
Bug #838216 [chef] Could not find 'chef-zero' (~> 4.5) - did find: 
[chef-zero-5.0.0] (Gem::LoadError)
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
838216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 834126 open-gram

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 834126 open-gram
Bug #834126 {Done: Liang Guo } [sunpinyin-utils] 
open-gram: FTBFS: make[1]: *** [lm_sc.t3g] Aborted (core dumped)
Bug reassigned from package 'sunpinyin-utils' to 'open-gram'.
Ignoring request to alter found versions of bug #834126 to the same values 
previously set
No longer marked as fixed in versions open-gram/0.1.22+20131212-2.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
834126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: src:librsync: FTBFS on big-endian architectures

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 780507 src:librsync: FTBFS on big-endian architectures
Bug #780507 [src:librsync] src:librsync: FTBFS on BE
Changed Bug title to 'src:librsync: FTBFS on big-endian architectures' from 
'src:librsync: FTBFS on BE'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
780507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#780507: src:librsync: FTBFS on big-endian architectures

[Chris Lamb]

retitle 780507 src:librsync: FTBFS on big-endian architectures
thanks

Renaming for clarity.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#842713: ocamlbuild: FTBFS: E: Error: unit Ocamlbuild exported in ocamlbuild but already exported by ocaml-nox/ocaml-base-nox v4.02.3-7+b1

[Chris Lamb]

Source: ocamlbuild
Version: 0.9.3-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ocamlbuild fails to build from source in experimental/amd64:

  […]

 dh_strip
 dh_makeshlibs
 dh_shlibdeps
 dh_installdeb
 dh_ocaml
  E: Error: unit Ocamlbuild exported in ocamlbuild but already exported by 
ocaml-nox/ocaml-base-nox v4.02.3-7+b1
  E: Error running /usr/bin/ocaml-md5sums   --package ocamlbuild dep < 
debian/ocamlbuild.olist.debhelper at /usr/bin/dh_ocaml line 487.
  debian/rules:8: recipe for target 'binary' failed
  make: *** [binary] Error 255

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ocamlbuild.0.9.3-2.experimental.amd64.log.txt.gz
Description: Binary data

Bug#842591: debootstrap-udeb: fails to validate InRelease (BADSIG)

[Lennart Sorensen]

On Sun, Oct 30, 2016 at 05:28:57PM +0100, Cyril Brulebois wrote:
> Package: debootstrap-udeb
> Version: 1.0.85
> Severity: grave
> Justification: renders package unusable
> 
> The (re)addition of InRelease support broke debootstrap(-udeb) in a d-i
> context. The sed|tr|sed dance doesn't kill the final newline, which
> leads to a BAD signature.

The one I proposed certainly did.  It worked fine and was portable.
Just a touch ugly perhaps.

> My original proposal was to use head -c -1, which while not specified by
> posix actually just works. Reasons include:
>  1. Tests agree.
>  2. busybox's coreutils/head.c has:
> case 'c':
> count_bytes = 1;
>   …
> if (negative_N) {
> if (count_bytes) {
> print_except_N_last_bytes(fp, count);
> } else {
> print_except_N_last_lines(fp, count);
> }
> } else {
> print_first_N(fp, count, count_bytes);
> }

Well only if you have ENABLE_FEATURE_FANCY_HEAD and it was only added
in 2013, so rather recent addition.

> It might be suboptimal to use this for the time being, as it /might/
> limit portability. On the other hand, the idea was to get a d-i release
> out of the door.
> 
> I'll give it some thoughts in the upcoming hours, and decide how to fix.

-- 
Len Sorensen

Bug#842710: [gcc-6] Fails to compile OpenWrt/LEDE prereq-build

[Charlemagne Lasse]

Package: gcc-6
Version: 6.2.0-10
Severity: serious
X-Debbugs-CC: lede-...@lists.infradead.org

There is a regression after gcc-6 6.2.0-6. I get following output when
trying to compile LEDE/OpenWrt "Please install a static zlib"

This is wrong

$ ls -ltr /usr/lib/x86_64-linux-gnu/libz.a
-rw-r--r-- 1 root root 149834 Nov 27  2014 /usr/lib/x86_64-linux-gnu/libz.a

Following can be found in their include/prereq-build.mk

ifeq ($(HOST_OS),Linux)
  zlib_link_flags := -Wl,-Bstatic -lz -Wl,-Bdynamic
else
  zlib_link_flags := -lz
endif

$(eval $(call TestHostCommand,zlib, \
Please install a static zlib. (Missing libz.a or zlib.h), \
echo 'int main(int argc, char **argv) { gzdopen(0, "rb"); return 0; }' | \
gcc -include zlib.h -x c -o $(TMP_DIR)/a.out - $(zlib_link_flags)))

Testing it with gcc-6 6.2.0-6 works:

$ echo 'int main(int argc, char **argv) { gzdopen(0, "rb"); return 0;
}' | gcc -include zlib.h -x c -o a.out - -Wl,-Bstatic -lz
-Wl,-Bdynamic
$ echo $?
0

with gcc-6 6.2.0-10 fails:

$ echo 'int main(int argc, char **argv) { gzdopen(0, "rb"); return 0;
}' | gcc -include zlib.h -x c -o a.out - -Wl,-Bstatic -lz
-Wl,-Bdynamic
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libz.a(gzlib.o):
relocation R_X86_64_32S against `.rodata' can not be used when making
a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
$ echo $?
1

Processed: Bug#842500 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 842500 pending
Bug #842500 [python-keyring] python-launchpadlib: FTBFS: error: Could not find 
suitable distribution for Requirement.parse('secretstorage')
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#842500: marked as pending

[Dmitry Shachnev]

tag 842500 pending
thanks

Hello,

Bug #842500 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/python-keyring.git;a=commitdiff;h=4577db6

---
commit 4577db603ddfb507a72d9c2bb015c89fef53ceba
Author: Dmitry Shachnev 
Date:   Mon Oct 31 16:30:37 2016 +0300

Promote python[3]-secretstorage from Recommends to Depends.

This matches upstream changes, see:
- https://github.com/jaraco/keyring/commit/e6a05713
- https://github.com/jaraco/keyring/issues/231

Closes: #842500.

diff --git a/debian/changelog b/debian/changelog
index 774fffd..45e594a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-keyring (10.0.2-2) UNRELEASED; urgency=medium
+
+  * Promote python[3]-secretstorage from Recommends to Depends,
+following upstream (closes: #842500).
+
+ -- Dmitry Shachnev   Mon, 31 Oct 2016 16:29:42 +0300
+
 python-keyring (10.0.2-1) unstable; urgency=medium
 
   * New upstream release.

Processed: forwarded upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 840664 https://github.com/stympy/faker/issues/737
Bug #840664 [src:ruby-faker] ruby-faker: FTBFS randomly (failing tests)
Set Bug forwarded-to-address to 'https://github.com/stympy/faker/issues/737'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
840664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: ncmpc: NMU uploaded in deferred/queue

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #842326 [ncmpc] [PATCH] [RC] Fix FTBS for when building against upcoming 
lirc-0.9.4
Added tag(s) pending.

-- 
842326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#842500: python-launchpadlib: FTBFS: error: Could not find suitable distribution for Requirement.parse('secretstorage')

[Dmitry Shachnev]

Control: reassign -1 python-keyring 10.0.2-1
Control: affects -1 src:python-launchpadlib

Hi Chris,

On Sat, Oct 29, 2016 at 07:15:19PM +0100, Chris Lamb wrote:
> Dear Maintainer,
>
> python-launchpadlib fails to build from source in unstable/amd64:
>
>   […]
>   error: Could not find suitable distribution for 
> Requirement.parse('secretstorage')

This probably comes from the requires.txt file of python-keyring, which
lists secretstorage as the required dependency on Linux.

I will promote python-secretstorage from Recommends to Depends in
python-keyring packages.

--
Dmitry Shachnev


signature.asc
Description: PGP signature