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#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#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#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: 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

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 

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
 

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

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#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

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

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#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

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

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

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

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.

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#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: 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

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 

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 

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#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

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

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

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#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#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

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#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 

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#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
 

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

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#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#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#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#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=all=0.690-1=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#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=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,,);
 ^
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 ) 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 ) 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 ) 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 ) 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 ) 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 ) 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 ) 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 ) 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*}'

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#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

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#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

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

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

Bug#842248: marked as pending

[Michal Čihař]

tag 842248 pending
thanks

Hello,

Bug #842248 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/urlgrabber.git;a=commitdiff;h=a65262e

---
commit a65262e3183673fcd25991f37cc4ba9178b4a879
Author: Michal Čihař 
Date:   Mon Oct 31 09:05:26 2016 +0100

Switch to debhelper 9.

- fixes lintian warning about deprecated level
- avoids running testsuite through dh_auto_test (Closes: #842248)

diff --git a/debian/changelog b/debian/changelog
index ada6cf2..21f02ae 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+urlgrabber (3.10.1-2) UNRELEASED; urgency=medium
+
+  * Switch to debhelper 9.
+- fixes lintian warning about deprecated level
+- avoids running testsuite through dh_auto_test (Closes: #842248)
+
+ -- Michal Čihař   Mon, 31 Oct 2016 09:05:12 +0100
+
 urlgrabber (3.10.1-1) unstable; urgency=low
 
   * Team upload.

Bug#839138: Ceph maintainership status

[Dmitry Smirnov]

On Monday, 17 October 2016 8:53:30 PM AEDT László Böszörményi (GCS) wrote:
> I'd a discussion with Dmitry and if I understood correctly, he no
> longer wants to be a close contributor - but I let him speak about his
> intentions.

I confirm that. I had terrible experience with Ceph and I do not wish to 
touch it ever again... :(

-- 
Cheers,
 Dmitry Smirnov.

---

Human beings, who are almost unique in having the ability to learn from the
experience of others, are also remarkable for their apparent disinclination
to do so.
-- Mahatma Gandhi


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

Bug#828139: marked as done (cyrus-sasl2: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:21:47 +0100
with message-id 
<1477902107.1789783.772328257.7e0ef...@webmail.messagingengine.com>
and subject line OpenSSL 1.1.0
has caused the Debian Bug report #828139,
regarding cyrus-sasl2: 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.)


-- 
828139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-sasl2
Version: 2.1.26.dfsg1-15
Severity: important
Control: block 827061 by -1

Hi,

Your package is failing to build with openssl 1.1:
otp.c: In function 'otp_hash':
otp.c:121:16: error: storage size of 'mdctx' isn't known
 EVP_MD_CTX mdctx;

The struct has been made opaque and you now needs to allocate it
with EVP_MD_CTX_new().


See the manpages and
https://wiki.openssl.org/index.php/1.1_API_Changes for more
information.

openssl 1.1.0 is currently in experimental.


Kurt
--- End Message ---
--- Begin Message ---
Version: 2.1.27~72-g88d82a3+dfsg-1 

OpenSSL 1.1.0 support was added in upcoming 2.1.27 release (and we have
git snapshot of that).

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu--- End Message ---

Bug#841631: marked as done (bandit: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:48:32 +
with message-id 
and subject line Bug#841631: fixed in bandit 1.1.0-3
has caused the Debian Bug report #841631,
regarding bandit: FTBFS: Tests failures
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.)


-- 
841631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bandit
Version: 1.1.0-2
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):
> --
> _StringException: Traceback (most recent call last):
>   File "tests/unit/cli/test_baseline.py", line 146, in 
> test_main_git_command_failure
> mock_git_repo_commit.side_effect = git.exc.GitCommandError('', '')
>   File "/usr/lib/python2.7/dist-packages/git/exc.py", line 74, in __init__
> super(GitCommandError, self).__init__(command, status, stderr, stdout)
>   File "/usr/lib/python2.7/dist-packages/git/exc.py", line 51, in __init__
> self._cmd = safe_decode(command[0])
> IndexError: list index out of range
> 
> 
> --
> Ran 211 tests in 2.251s
> 
> FAILED (failures=2)
> debian/rules:18: 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/21/bandit_1.1.0-2_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: bandit
Source-Version: 1.1.0-3

We believe that the bug you reported is fixed in the latest version of
bandit, 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.
Thomas Goirand  (supplier of updated bandit 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 09:41:01 +0100
Source: bandit
Binary: python-bandit python3-bandit bandit
Architecture: source all
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 bandit - Security oriented static analyzer for Python code - Metapackage
 python-bandit - Security oriented static analyzer for Python code - Python 2.7
 python3-bandit - Security oriented static analyzer for Python code - Python 3.x
Closes: 841631
Changes:
 bandit (1.1.0-3) unstable; urgency=medium
 .
   * Add remove failing tests patch (Closes: #841631).
Checksums-Sha1:
 2945a30c5b57ba9f09b73c1c15c308f007e996c4 2824 bandit_1.1.0-3.dsc
 20c3fa18327d9844c497e1c54e038cc32580dc5f 4940 bandit_1.1.0-3.debian.tar.xz
 70f9ef69989fdef12b06b3dc0c2098f0d242d3d4 5296 bandit_1.1.0-3_all.deb
 6d04b3f2093c6d1cef8dd0c3248ba8fe78128c43 58736 python-bandit_1.1.0-3_all.deb
 36cecbd1fd52fd53aebf441bb8641e53eebee338 58796 python3-bandit_1.1.0-3_all.deb
Checksums-Sha256:
 d5d758031ccdae8c102c4cea4e0ca61eb8790935b90872e32d45f5feaafd4545 2824 
bandit_1.1.0-3.dsc
 a0eaf7b53b89c4be34cb4435f7a93095c9cc0d6e26284fed675236d94fc2e741 4940 

Bug#841471: marked as done (fim: FTBFS on several architectures: default_font_byte_array.h:349:1: error: narrowing conversion of '905969664' from 'int' to 'unsigned char' inside { } [-Wnarrowing])

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:48:40 +
with message-id 
and subject line Bug#841471: fixed in fim 0.5~rc2-2
has caused the Debian Bug report #841471,
regarding fim: FTBFS on several architectures: default_font_byte_array.h:349:1: 
error: narrowing conversion of '905969664' from 'int' to 'unsigned char' inside 
{ } [-Wnarrowing]
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.)


-- 
841471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fim
Version: 0.5~rc2-1
Severity: serious

Your package failed to build on several architectures with this errors:

g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libpng16 -I/usr/include -I/usr/include/SDL -D_GNU_SOURCE=1 
-D_REENTRANT -c -o FontServer.o FontServer.cpp
In file included from FontServer.cpp:184:0:
default_font_byte_array.h: In static member function 'static fim::fs_font* 
fim::FontServer::fs_consolefont(const fim_char_t**)':
default_font_byte_array.h:349:1: error: narrowing conversion of '905969664' 
from 'int' to 'unsigned char' inside { } [-Wnarrowing]
 };
 ^
default_font_byte_array.h:349:1: error: narrowing conversion of '67108864' from 
'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '33554432' from 
'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '268435456' 
from 'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '2852126720u' 
from 'unsigned int' to 'unsigned char' inside { } [-Wnarrowing]
[...]

This seems to be happening on big-endian architectures, so may be an
endianness issue.

Full 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)
--- End Message ---
--- Begin Message ---
Source: fim
Source-Version: 0.5~rc2-2

We believe that the bug you reported is fixed in the latest version of
fim, 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.
Rafael Laboissiere  (supplier of updated fim 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 06:49:34 -0200
Source: fim
Binary: fim
Architecture: source amd64
Version: 0.5~rc2-2
Distribution: unstable
Urgency: medium
Maintainer: Michele Martone 
Changed-By: Rafael Laboissiere 
Description:
 fim- scriptable frame buffer and ascii art image viewer
Closes: 841471
Changes:
 fim (0.5~rc2-2) unstable; urgency=medium
 .
   * Bump debhelper compatibility level to 10
   * d/control:
 + Add Vcs-* URL fields
 + Add myself to the list of Uploaders
 + Bump Standards-Version to 3.9.8 (no changes needed)
 + Drop article at the beginning of package synopsis
   * d/rules:
 + Avoid installation of duplicated upstream changelog
 + Use hardening flags
 + Build-depends on groff
   * d/watch: Ignore the "-trunk" upstream tarballs
   * Use upstream tarball cryptographic signature
 + d/watch: Add pgpsigurlmangle option
 + d/u/signing-key.asc: Add file with GPG key of upstream author
   * d/s/options: Add file with extend-diff-ignore list
   * d/docs: Drop duplicated entry
   * d/p/endianness-robust.patch: Add patch (Closes: 841471)
Checksums-Sha1:
 23d4b75c5a5e569084c1ba2f337f2aa19fecf5c4 2008 fim_0.5~rc2-2.dsc
 5a54e603885915632b0502e8e44da97c0a8856fa 6528 fim_0.5~rc2-2.debian.tar.xz
 

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

[Sebastiaan Couwenberg]

On 10/31/2016 05:13 AM, Anders Kaseorg wrote:
> On Sun, 30 Oct 2016, Bas Couwenberg wrote:
>> The recent git upload FTBFS on mips64el due to OOM, the missing build on
>> mips64el is preventing the qgis rebuild as part of the ongoing gdal
>> transition (#842288).
>>
>> The build was performed on mipsel-manda-02 which is known to have issues
>> like these (although git built successfully on this buildd before).
>> Perhaps a rebuild on another buildd will be sufficient.
> 
> Eep.
> 
> Looking at 
> https://buildd.debian.org/status/logs.php?pkg=git=mips64el, the build 
> has been attempted three times now, including once on mipsel-aql-02, 
> failing all three times with out of memory errors.  None of the failing 
> tests (t0023-crlf-am.sh, t0064-sha1-array.sh, t0302-credential-store.sh) 
> have changed between 2.10.1 and 2.10.2, and 2.10.1 built with no trouble.  
> These tests should be using basically no memory (about 4 MB each).
> 
> Maybe another test running in parallel is using memory and causing these 
> tests to fail?  Could these build machines be so underpowered that they 
> shouldn’t be setting DEB_BUILD_OPTIONS=parallel=4?
> 
> Unless someone familiar with the mips64el buildd situation has a better 
> plan, I’m unsure how to proceed except by disabling individual failing 
> tests, or the entire test suite, for mips64el.
> 
> Any ideas?

Disabling the tests on mips64el is reasonable.

You can also do a build on the mips64el porterbox if that succeeds
without changes you can just upload that.

Kind Regards,

Bas

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

Bug#817523: libarray-refelem-perl: Removal of debhelper compat 4

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Bump to 10.
  * debian/control:
- Build-depend on debhelper (>= 10).
- Depend on ${misc:Depends}.
  * debian/rules:
- Switch to dh sequencer.
  * debian/docs: Add README.

Thanks for considering the patch.

Logan Rosen
diff -u libarray-refelem-perl-1.00/debian/compat libarray-refelem-perl-1.00/debian/compat
--- libarray-refelem-perl-1.00/debian/compat
+++ libarray-refelem-perl-1.00/debian/compat
@@ -1 +1 @@
-4
+10
diff -u libarray-refelem-perl-1.00/debian/control libarray-refelem-perl-1.00/debian/control
--- libarray-refelem-perl-1.00/debian/control
+++ libarray-refelem-perl-1.00/debian/control
@@ -1,13 +1,13 @@
 Source: libarray-refelem-perl
 Section: perl
 Priority: optional
-Build-Depends: debhelper (>= 4.0.2), perl (>= 5.8.0-7)
+Build-Depends: debhelper (>= 10), perl (>= 5.8.0-7)
 Maintainer: Matthias Urlichs 
 Standards-Version: 3.6.2
 
 Package: libarray-refelem-perl
 Architecture: any
-Depends: ${perl:Depends}, ${shlibs:Depends}
+Depends: ${perl:Depends}, ${shlibs:Depends}, ${misc:Depends}
 Description:  Set up array elements as aliases
  This module gives you direct access to the internal perl routines that
  let you store reference to things in arrays and hashes.
diff -u libarray-refelem-perl-1.00/debian/rules libarray-refelem-perl-1.00/debian/rules
--- libarray-refelem-perl-1.00/debian/rules
+++ libarray-refelem-perl-1.00/debian/rules
@@ -2,82 +2,2 @@
-
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
-
-# If set to a true value then MakeMaker's prompt function will
-# always return the default without waiting for user input.
-export PERL_MM_USE_DEFAULT=1
-
-PACKAGE=$(shell dh_listpackages)
-
-ifndef PERL
-PERL = /usr/bin/perl
-endif
-
-TMP =$(CURDIR)/debian/$(PACKAGE)
-
-# Allow disabling build optimation by setting noopt in
-# $DEB_BUILD_OPTIONS
-CFLAGS = -Wall -g
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
-CFLAGS += -O0
-else
-CFLAGS += -O2
-endif
-
-build: build-stamp
-build-stamp:
-	dh_testdir
-
-	$(PERL) Makefile.PL INSTALLDIRS=vendor
-	$(MAKE) OPTIMIZE="$(CFLAGS)" LD_RUN_PATH=""
-
-	touch build-stamp
-
-clean:
-	dh_testdir
-	dh_testroot
-
-	-$(MAKE) realclean
-
-	dh_clean build-stamp install-stamp
-
-install: install-stamp
-install-stamp:
-	dh_testdir
-	dh_testroot
-	dh_clean -k
-
-	$(MAKE) test
-	$(MAKE) install DESTDIR=$(TMP) PREFIX=/usr
-	
-	# As this is a architecture dependent package, we are not supposed to install
-	# stuff to /usr/share/perl5. MakeMaker creates the dirs, we delete them from 
-	# the deb:
-	[ ! -d $(TMP)/usr/share/perl5 ] || rmdir --ignore-fail-on-non-empty --parents $(TMP)/usr/share/perl5
-	
-	touch install-stamp
-
-# Build architecture-independent files here.
-binary-indep: build install
-# We have nothing to do by default.
-
-# Build architecture-dependent files here.
-binary-arch: build install
-	dh_testdir
-	dh_testroot
-	dh_installdocs README
-	dh_installchangelogs Changes
-	dh_link
-	dh_strip
-	dh_compress
-	dh_fixperms
-	dh_makeshlibs
-	dh_installdeb
-	dh_perl 
-	dh_shlibdeps
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary
+%:
+	dh $@
only in patch2:
unchanged:
--- libarray-refelem-perl-1.00.orig/debian/docs
+++ libarray-refelem-perl-1.00/debian/docs
@@ -0,0 +1 @@
+README

Processed: Re: libarray-refelem-perl: Removal of debhelper compat 4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #817523 [src:libarray-refelem-perl] libarray-refelem-perl: Removal of 
debhelper compat 4
Bug #827681 [src:libarray-refelem-perl] libarray-refelem-perl: FTBFS: dh_clean: 
Compatibility levels before 5 are no longer supported (level 4 requested)
Added tag(s) patch.
Added tag(s) patch.

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

Processed: reassign 841343 to moarvm

[Debian Bug Tracking System]

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

> reassign 841343 moarvm
Bug #841343 [src:rakudo] rakudo: FTBFS on arm64, powerpc and ppc64 - testsuite 
errors
Bug reassigned from package 'src:rakudo' to 'moarvm'.
No longer marked as found in versions rakudo/2016.09-2.
Ignoring request to alter fixed versions of bug #841343 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#828516: marked as done (pure-ftpd: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:50:31 +
with message-id 
and subject line Bug#828516: fixed in pure-ftpd 1.0.43-2
has caused the Debian Bug report #828516,
regarding pure-ftpd: 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.)


-- 
828516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pure-ftpd
Version: 1.0.36-3.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/pure-ftpd_1.0.36-3.2_amd64-20160529-1512

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: pure-ftpd
Source-Version: 1.0.43-2

We believe that the bug you reported is fixed in the latest version of
pure-ftpd, 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.
Stefan Hornburg (Racke)  (supplier of updated pure-ftpd 
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: Thu, 27 Oct 2016 14:29:26 +0200
Source: pure-ftpd
Binary: pure-ftpd-common pure-ftpd pure-ftpd-mysql pure-ftpd-postgresql 
pure-ftpd-ldap
Architecture: source all amd64
Version: 1.0.43-2
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Stefan Hornburg (Racke) 
Description:
 pure-ftpd  - Secure and efficient FTP server
 pure-ftpd-common - Pure-FTPd FTP server (Common Files)
 pure-ftpd-ldap - Secure and efficient FTP server with LDAP user authentication
 pure-ftpd-mysql - Secure and efficient FTP server with MySQL user 
authentication
 pure-ftpd-postgresql - Secure and efficient FTP server with PostgreSQL user 
authenticati
Closes: 828516
Changes:
 pure-ftpd (1.0.43-2) unstable; urgency=medium
 .
   * Add upstream patch for OpenSSL 1.1.x compatibility (Closes: #828516).
   * Add Debian watch file.
   * Fix build dependency on obsolete package libmysqlclient-dev.
   * Remove incorrect Vcs-* fields from control file.
   * Add NoTruncate to POD of pure-ftpd-wrapper script (Ubuntu #1166330).
   * Bump up Standards-Version to 3.9.8.
Checksums-Sha1:
 09a5db3f2275291f39d29d0f39650dab346c47a9 2123 pure-ftpd_1.0.43-2.dsc
 8bd08f16d96833b14027ec6565ecfe77f11a2886 49399 pure-ftpd_1.0.43-2.diff.gz
 d2a1915264300fdac2bcc9c9463c45e42f014c30 187736 
pure-ftpd-common_1.0.43-2_all.deb
 8d8fcaf0e4476846cb4944ef047c708151031c92 18748 
pure-ftpd-dbgsym_1.0.43-2_amd64.deb
 a38817db81b6c13e63ffc0bf4f29a047e2ce2493 19678 
pure-ftpd-ldap-dbgsym_1.0.43-2_amd64.deb
 ff116eddfc4eceb4c9afb4b30c6a7e2920fda11b 128676 
pure-ftpd-ldap_1.0.43-2_amd64.deb
 a35389724c2c3d80660adb6bcc381046d5def647 19680 
pure-ftpd-mysql-dbgsym_1.0.43-2_amd64.deb
 fc9c8fb38e990d171c7341f14d0e4cd2c89ae057 129036 
pure-ftpd-mysql_1.0.43-2_amd64.deb
 fa5ab389b1b9b873b8ab034f4751aa94b5ee0ddc 19572 
pure-ftpd-postgresql-dbgsym_1.0.43-2_amd64.deb
 8ae058044a1cb84781149fde77a4a993db223d76 128890 
pure-ftpd-postgresql_1.0.43-2_amd64.deb
 fff8499779fc6e17bf4406b20b67c2a743481eae 117430 pure-ftpd_1.0.43-2_amd64.deb
Checksums-Sha256:
 7a53bf3149718d1ab4860b3ab1b59ed349c07fd080c5bd6f1c0d66c7cf8a5f93 2123 
pure-ftpd_1.0.43-2.dsc
 813da95077300a4c8e2c0fe342bc427e09428f6d67a5f310cb241d47119efa58 49399 
pure-ftpd_1.0.43-2.diff.gz
 94918f4b2bbf53cd244d254d406fa8c9bde1950022471720211f311d87ac16bf 187736 
pure-ftpd-common_1.0.43-2_all.deb
 9a970f6e1a71ba80a7cd32a0e9c592d3d7c813db2a58a174cd39ab87e50eafb1 18748 

Bug#841516: marked as done (python-dogpile.cache: FTBFS randomly (AssertionError: 1 != 0))

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:50:42 +
with message-id 
and subject line Bug#841516: fixed in python-dogpile.cache 0.6.2-4
has caused the Debian Bug report #841516,
regarding python-dogpile.cache: FTBFS randomly (AssertionError: 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.)


-- 
841516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-dogpile.cache
Version: 0.6.2-3
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
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,python3,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

tests/cache/test_region.py::CustomInvalidationStrategyTest::test_should_delete_multiple_values
 PASSED
tests/cache/test_region.py::CustomInvalidationStrategyTest::test_should_get_multiple_values
 PASSED
tests/cache/test_region.py::CustomInvalidationStrategyTest::test_should_set_multiple_values
 PASSED
tests/cache/test_region.py::CustomInvalidationStrategyTest::test_soft_invalidate_get
 PASSED
tests/cache/test_region.py::CustomInvalidationStrategyTest::test_soft_invalidate_get_or_create
 PASSED
tests/cache/test_region.py::CustomInvalidationStrategyTest::test_soft_invalidate_get_or_create_multi
 PASSED
tests/cache/test_region.py::CustomInvalidationStrategyTest::test_soft_invalidate_requires_expire_time_get
 PASSED
tests/cache/test_region.py::CustomInvalidationStrategyTest::test_soft_invalidate_requires_expire_time_get_multi
 PASSED
tests/cache/test_region.py::ProxyBackendTest::test_argument_proxies PASSED
tests/cache/test_region.py::ProxyBackendTest::test_cachedvalue_passed PASSED
tests/cache/test_region.py::ProxyBackendTest::test_counter_proxies PASSED
tests/cache/test_region.py::ProxyBackendTest::test_instance_proxies PASSED
tests/cache/plugins/test_mako_cache.py::TestMakoPlugin::test_basic PASSED
tests/cache/plugins/test_mako_cache.py::TestMakoPlugin::test_timeout PASSED
tests/util/test_nameregistry.py::NameRegistryTest::test_name_registry PASSED
=== short test summary info 
FAIL 
tests/cache/test_memcached_backend.py::LocalThreadTest::test_client_cleanup_1
FAIL 
tests/cache/test_memcached_backend.py::LocalThreadTest::test_client_cleanup_3

=== FAILURES ===
 LocalThreadTest.test_client_cleanup_1 _
Traceback (most recent call last):
  File "/<>/tests/cache/test_memcached_backend.py", line 273, in 
test_client_cleanup_1
self._test_client_cleanup(1)
  File "/<>/tests/cache/test_memcached_backend.py", line 299, in 
_test_client_cleanup
eq_(MockClient.number_of_clients(), 0)
  File "/<>/tests/cache/__init__.py", line 11, in eq_
assert a == b, msg or "%r != %r" % (a, b)
AssertionError: 1 != 0
 LocalThreadTest.test_client_cleanup_3 _
Traceback (most recent call last):
  File "/<>/tests/cache/test_memcached_backend.py", line 276, in 
test_client_cleanup_3
self._test_client_cleanup(3)
  File "/<>/tests/cache/test_memcached_backend.py", line 299, in 
_test_client_cleanup
eq_(MockClient.number_of_clients(), 0)
  File "/<>/tests/cache/__init__.py", line 11, in eq_
assert a == b, msg or "%r != %r" % (a, b)
AssertionError: 1 != 0
 pytest-warning summary 
WC1 None [pytest] section in setup.cfg files is deprecated, use [tool:pytest] 
instead.
 2 failed, 290 passed, 

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

[Emilio Pozuelo Monfort]

On Mon, 31 Oct 2016 07:39:48 +0100 Sebastiaan Couwenberg  
wrote:
> On 10/31/2016 05:13 AM, Anders Kaseorg wrote:
> > On Sun, 30 Oct 2016, Bas Couwenberg wrote:
> >> The recent git upload FTBFS on mips64el due to OOM, the missing build on
> >> mips64el is preventing the qgis rebuild as part of the ongoing gdal
> >> transition (#842288).
> >>
> >> The build was performed on mipsel-manda-02 which is known to have issues
> >> like these (although git built successfully on this buildd before).
> >> Perhaps a rebuild on another buildd will be sufficient.
> > 
> > Eep.
> > 
> > Looking at 
> > https://buildd.debian.org/status/logs.php?pkg=git=mips64el, the build 
> > has been attempted three times now, including once on mipsel-aql-02, 
> > failing all three times with out of memory errors.  None of the failing 
> > tests (t0023-crlf-am.sh, t0064-sha1-array.sh, t0302-credential-store.sh) 
> > have changed between 2.10.1 and 2.10.2, and 2.10.1 built with no trouble.  
> > These tests should be using basically no memory (about 4 MB each).
> > 
> > Maybe another test running in parallel is using memory and causing these 
> > tests to fail?  Could these build machines be so underpowered that they 
> > shouldn’t be setting DEB_BUILD_OPTIONS=parallel=4?
> > 
> > Unless someone familiar with the mips64el buildd situation has a better 
> > plan, I’m unsure how to proceed except by disabling individual failing 
> > tests, or the entire test suite, for mips64el.
> > 
> > Any ideas?
> 
> Disabling the tests on mips64el is reasonable.
> 
> You can also do a build on the mips64el porterbox if that succeeds
> without changes you can just upload that.

It is better to understand what is going on first. git is an important piece of
software and the tests are here for a reason. As Bas said, we have porterboxes
where it is very easy to install packages and try to reproduce this, so I'd
suggest that as a first step.

The machines should be fine, they have 8GB of memory, which should be sufficient
for parallel=4.

Cheers,
Emilio

Bug#839138: Ceph maintainership status

[Dmitry Smirnov]

On Monday, 17 October 2016 9:34:35 PM AEDT Adrian Bunk wrote:
> It would also be OK if you would state that there is noone left active
> among the Ceph Maintainers, and that I can orphan the package for
> finding new maintainers.

I'm not going to maintain Ceph any more. I'm utterly disappointed in this 
technology...


> Regarding ceph-dkms, this is only in experimental and has an RC bug
> that it doesn't work with the jessie kernel.
> Is there anything left that is not in the upstream kernel?

In the current state of packaging most certainly not. However kernel was 
behind recent changes in Ceph so package was useful for troubleshooting for 
some time... I only wanted to keep the package in experimental to avoid 
bothering ftp-masters again in case someone wants to use it... As far as I'm 
concerned nobody needs it so it is safe to remove...

Thanks.

-- 
Regards,
 Dmitry Smirnov.


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

Processed: Bug#842248 marked as pending

[Debian Bug Tracking System]

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

> tag 842248 pending
Bug #842248 [src:urlgrabber] urlgrabber: FTBFS randomly (build hangs)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#827811: marked as done (signond: FTBFS: dh_makeshlibs: failing due to earlier errors)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 10:02:18 +0100
with message-id <20161031090158.oiltodajxjtji...@gnuservers.com.ar>
and subject line Re: Bug#827811: signond: FTBFS: dh_makeshlibs: failing due to 
earlier errors
has caused the Debian Bug report #827811,
regarding signond: FTBFS: dh_makeshlibs: failing due to earlier 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.)


-- 
827811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: signond
Version: 8.57+20150423-3
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,

signond fails to build from source in unstable/amd64:

  [..]

  Running dot for graph 184/204
  Running dot for graph 185/204
  Running dot for graph 186/204
  Running dot for graph 187/204
  Running dot for graph 188/204
  Running dot for graph 189/204
  Running dot for graph 190/204
  Running dot for graph 191/204
  Running dot for graph 192/204
  Running dot for graph 193/204
  Running dot for graph 194/204
  Running dot for graph 195/204
  Running dot for graph 196/204
  Running dot for graph 197/204
  Running dot for graph 198/204
  Running dot for graph 199/204
  Running dot for graph 200/204
  Running dot for graph 201/204
  Running dot for graph 202/204
  Running dot for graph 203/204
  Running dot for graph 204/204
  Patching output file 1/104
  Patching output file 2/104
  Patching output file 3/104
  Patching output file 4/104
  Patching output file 5/104
  Patching output file 6/104
  Patching output file 7/104
  Patching output file 8/104
  Patching output file 9/104
  Patching output file 10/104
  Patching output file 11/104
  Patching output file 12/104
  Patching output file 13/104
  Patching output file 14/104
  Patching output file 15/104
  Patching output file 16/104
  Patching output file 17/104
  Patching output file 18/104
  Patching output file 19/104
  Patching output file 20/104
  Patching output file 21/104
  Patching output file 22/104
  Patching output file 23/104
  Patching output file 24/104
  Patching output file 25/104
  Patching output file 26/104
  Patching output file 27/104
  Patching output file 28/104
  Patching output file 29/104
  Patching output file 30/104
  Patching output file 31/104
  Patching output file 32/104
  Patching output file 33/104
  Patching output file 34/104
  Patching output file 35/104
  Patching output file 36/104
  Patching output file 37/104
  PatchingBuilding up file structure...
  Insert custom filters...
  Insert help data for filter section (1 of 1)...
  Insert files...
  Insert contents...
  Insert indices...
  Documentation successfully generated.
   output file 38/104
  Patching output file 39/104
  Patching output file 40/104
  Patching output file 41/104
  Patching output file 42/104
  Patching output file 43/104
  Patching output file 44/104
  Patching output file 45/104
  Patching output file 46/104
  Patching output file 47/104
  Patching output file 48/104
  Patching output file 49/104
  Patching output file 50/104
  Patching output file 51/104
  Patching output file 52/104
  Patching output file 53/104
  Patching output file 54/104
  Patching output file 55/104
  Patching output file 56/104
  Patching output file 57/104
  Patching output file 58/104
  Patching output file 59/104
  Patching output file 60/104
  Patching output file 61/104
  Patching output file 62/104
  Patching output file 63/104
  Patching output file 64/104
  Patching output file 65/104
  Patching output file 66/104
  Patching output file 67/104
  Patching output file 68/104
  Patching output file 69/104
  Patching output file 70/104
  Patching output file 71/104
  Patching output file 72/104
  Patching output file 73/104
  Patching output file 74/104
  Patching output file 75/104
  Patching output file 76/104
  Patching output file 77/104
  Patching output file 78/104
  Patching output file 79/104
  Patching output file 80/104
  Patching output file 81/104
  Patching output file 82/104
  Patching output file 83/104
  Patching output file 84/104
  Patching output file 85/104
  Patching output file 86/104
  Patching output file 87/104
  Patching output file 88/104
  Patching output file 89/104
  Patching output file 90/104
  Patching output file 91/104
  Patching output file 92/104
  Patching output file 93/104
  Patching output file 94/104
  Patching output file 95/104
  Patching output file 96/104
  Patching output file 

Bug#828396: marked as done (libisds: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:18:47 +
with message-id 
and subject line Bug#828396: fixed in libisds 0.10.6-1
has caused the Debian Bug report #828396,
regarding libisds: 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.)


-- 
828396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libisds
Version: 0.10.1-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/libisds_0.10.1-1_amd64-20160529-1441

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: libisds
Source-Version: 0.10.6-1

We believe that the bug you reported is fixed in the latest version of
libisds, 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 libisds 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 09:52:13 +0100
Source: libisds
Binary: libisds5 libisds-dev
Architecture: source
Version: 0.10.6-1
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description:
 libisds-dev - Czech Data Boxes access library (development files)
 libisds5   - Czech Data Boxes access library (shared library)
Closes: 828396
Changes:
 libisds (0.10.6-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.10.6
+ OpenSSL 1.1.0 compatibility (Closes: #828396)
Checksums-Sha1:
 1cadda95eaa066ef893221d54278804d86fbf181 2069 libisds_0.10.6-1.dsc
 c0cd855ebdd4b4ac9ea70631a0ddb1eb122cb8a5 724120 libisds_0.10.6.orig.tar.xz
 7e20803ec897bb38a88b6018244482d68f7b4341 6544 libisds_0.10.6-1.debian.tar.xz
Checksums-Sha256:
 589b10f6d1b591468c29bed139ce0e889e498734658bf9ed1f2a00b234f54e11 2069 
libisds_0.10.6-1.dsc
 49ca70acef5dd5d092a03643f4d2f96ff8250b135eb8a5f62fa1fd3f8a8a 724120 
libisds_0.10.6.orig.tar.xz
 387d7703d70bf856a949a71ed08718df1c59ef72264a1acda25d5c82b67aeb59 6544 
libisds_0.10.6-1.debian.tar.xz
Files:
 02e28ce59b18866a04e74d1653e3dcca 2069 libs optional libisds_0.10.6-1.dsc
 3691cc8d7a0d8acb3cd561d19364fc0e 724120 libs optional 
libisds_0.10.6.orig.tar.xz
 1ecaad2a186df5aa19aaf26085aa7cef 6544 libs optional 
libisds_0.10.6-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYFwfTXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHmDIP/RNpD5F0YWYbXTa3nyDR0kqe
zliCP5AZrJsI/82QRqztpl6lNWmTmP2O5ejYFgPmuXlv2uONsCTWGB+FuMfJ4WB/
IZVdybVjYrveH8U5hHbDUeL/eP9OAh9lLBg86zJUWp80IG27IS/zaeJU9rtgjZQL
YPGPJ7FFVktEyiHAk6VdSzlyWW93g175FdVE/CesYuQaR+UEwAmKlWw1BPLLRKyv
Xu1hiNnt0jnQvSt2n9H07LmJ+rRH8/1ylPmLUiCshdD10K8+t0Id9ebK8C6lc9Gv
7RX9PC1rNjb2tm3F3LVv6xJtWtREG3GfFpzbS+UzjVd/yKiVKRsxj4N4o2SA7PUA
ae+qHVMju/S8L8PTzRwhlY9RQPF3p9qgYyXj8J8UpkfLRrd7s/H/Yn0NrRoDS48W
x19a9MSkO95E+Ja/3dzBiZY99Od65BRB3+e5G63agLAp7WqEi0EEPQmE8qctHJpK
cIAqPlxyt3IzxxudUKvHzoCVraNgJA/JWc3NekPVlzxFpcDac6CYpuO2MXmQ3hmY
JNVvOem4r7qtIdtaJC/xkCuJLwBGH3tjjDK3rBFDDB1iUeFjVbKu1NGGFDtiCvJu
BFWfHEW4FiOV2MndtlljtsE8MVX02jXvzt1O7+T674dt2xmaKc5XJcSyN5EFT0TZ
o6sheizfHievMTWxrYuM
=gI1y
-END PGP SIGNATURE End Message ---

Processed: bug 828607 is forwarded to https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2016-October/004315.html

[Debian Bug Tracking System]

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

> forwarded 828607 
> https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2016-October/004315.html
Bug #828607 [src:xml-security-c] xml-security-c: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 
'https://lists.alioth.debian.org/pipermail/pkg-shibboleth-devel/2016-October/004315.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
828607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828607
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]

On Mon, 31 Oct 2016, Sebastiaan Couwenberg wrote:
> Disabling the tests on mips64el is reasonable.
> 
> You can also do a build on the mips64el porterbox if that succeeds
> without changes you can just upload that.

Alright.  I am still a DM in the process of applying to be a DD, but I’ve 
now requested a DM guest account (https://nm.debian.org/process/114), and 
I’ll see if that is granted quickly.

Anders

Processed: fixed 835752 in 4:16.08.2-1

[Debian Bug Tracking System]

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

> fixed 835752 4:16.08.2-1
Bug #835752 {Done: Maximiliano Curia } [src:dolphin] dolphin: 
FTBFS: dh_install: missing files, aborting
Marked as fixed in versions dolphin/4:16.08.2-1.
> thanks
Stopping processing here.

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

Bug#842668: node-extend-shallow: FTBFS (Cannot find module 'is-extendable')

[Santiago Vila]

Package: src:node-extend-shallow
Version: 2.0.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
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'is-extendable'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/index.js:3:16)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/test.js:13:14)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
at Array.forEach (native)
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:139:18)
at node.js:974:3
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Looks like a missing build-depends.

Thanks.

Bug#842669: node-map-visit: FTBFS (Cannot find module 'should')

[Santiago Vila]

Package: src:node-map-visit
Version: 0.1.5-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
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'should'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/test.js:4:1)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
at Array.forEach (native)
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:139:18)
at node.js:974:3
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Looks like a missing build-depends.

Thanks.

Bug#842667: node-collection-visit: FTBFS (Cannot find module 'should')

[Santiago Vila]

Package: src:node-collection-visit
Version: 0.2.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 build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'should'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/test.js:4:1)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
at Array.forEach (native)
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:139:18)
at node.js:974:3
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Looks like a missing build-depends.

Thanks.

Bug#828552: spamassassin: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-10-29 14:15:30 [-0700], Noah Meyerhans wrote:
> Control: tags -1 - patch + upstream
> Control: forwarded -1 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7361
> 
> Unfortunately, this patch breaks compatibility with OpenSSL < 1.1.0, as
> the CRYPTO_zalloc function does not exist there.  We want to still
> support backports, etc, without too much effort, so I'm thinking of
> using CRYPTO_malloc instead, which exists in at least 1.0.2j-1 as
> provided in stable.

I'm sorry. I was looking for symbol which is available in both version
and somehow I missed that.

Sebastian

Bug#841748: esniper: needs update for recent eBay changes

[Dima Barsky]

On 29/10/16 15:52, Dmitry Smirnov wrote:

Hi Dima,

I've prepared esniper updates for to upload:

 https://anonscm.debian.org/cgit/collab-maint/esniper.git

I intend to upload soon... Please review. Thanks.


Hi Dmitry,

Thanks for your help, I'm going to apply your changes to the newly 
released esniper 2.32.0. I'll upload it a couple of days.


Regards,
Dima.

Bug#842248: marked as done (urlgrabber: FTBFS randomly (build hangs))

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:08:05 +
with message-id 
and subject line Bug#842248: fixed in urlgrabber 3.10.1-2
has caused the Debian Bug report #842248,
regarding urlgrabber: FTBFS randomly (build hangs)
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.)


-- 
842248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:urlgrabber
Version: 3.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 --with quilt build-indep
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i
   dh_update_autotools_config -i
   dh_quilt_patch -i
File series fully applied, ends at patch libexec.diff
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_auto_build -i
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
make -j1
make[1]: Entering directory '/<>'
TARGETS: changelog release clean test
make[1]: Leaving directory '/<>'
   dh_auto_test -i
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
make -j1 test
make[1]: Entering directory '/<>'
E.EE.E.s...ssEsssEEEsEEEs..Emake[1]: *** wait: No child 
processes.  Stop.
make[1]: *** Waiting for unfinished jobs
make[1]: *** wait: No child processes.  Stop.
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
E: Build killed with signal TERM after 60 minutes of inactivity


Tha above is just an example.

I tried to build it five times and it failed five times, on different 
autobuilders.
I'm attaching the build logs.

The builds were made on a QEMU/KVM virtual machine with a single CPU,
using sbuild.

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).

While we are at it, please consider uploading this package in
source-only form next time, so that we get official build logs here:

https://buildd.debian.org/status/package.php?p=urlgrabber

Thanks.

urlgrabber_3.10.1-1_amd64-20161027T034028Z.gz
Description: application/gzip


urlgrabber_3.10.1-1_amd64-20161027T094331Z.gz
Description: application/gzip


urlgrabber_3.10.1-1_amd64-20161027T094501Z.gz
Description: application/gzip


urlgrabber_3.10.1-1_amd64-20161027T094742Z.gz
Description: application/gzip


urlgrabber_3.10.1-1_amd64-20161027T094921Z.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: urlgrabber
Source-Version: 3.10.1-2

We believe that the bug you reported is fixed in the latest version of
urlgrabber, 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.
Michal Čihař  (supplier of updated urlgrabber 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 09:09:20 +0100
Source: urlgrabber
Binary: python-urlgrabber
Architecture: source
Version: 3.10.1-2
Distribution: unstable
Urgency: medium
Maintainer: Kevin Coyner 
Changed-By: Michal Čihař 
Description:
 python-urlgrabber - high-level URL transfer library
Closes: 842248
Changes:
 urlgrabber (3.10.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Switch to debhelper 9.
 - fixes lintian warning about deprecated level
 

Bug#835786: marked as done (lua-openssl: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:05:49 +
with message-id 
and subject line Bug#835786: fixed in lua-openssl 20161029-1-g8caed30-1
has caused the Debian Bug report #835786,
regarding lua-openssl: 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.)


-- 
835786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-openssl
Version: 20151221-2
Severity: important

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-08-26/failed/lua-openssl_20151221-2_amd64-2016-08-26T19%3A13%3A40Z

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.

Experimental has the libssl-dev 1.1.0 packages in it. 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: lua-openssl
Source-Version: 20161029-1-g8caed30-1

We believe that the bug you reported is fixed in the latest version of
lua-openssl, 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 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated lua-openssl 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 08:57:00 +0100
Source: lua-openssl
Binary: lua-openssl lua-openssl-dev
Architecture: source
Version: 20161029-1-g8caed30-1
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description:
 lua-openssl - event loop for Lua
 lua-openssl-dev - event loop for Lua (development package)
Closes: 835786
Changes:
 lua-openssl (20161029-1-g8caed30-1) unstable; urgency=medium
 .
   * Imported Upstream version 20161029-1-g8caed30
+ OpenSSL 1.1.0 support (Closes: #835786)
   * Remove arc4random patch as it was merged upstream
Checksums-Sha1:
 48f5af4a3b77ca3cc12105e18ca5b61be6d0da52 2192 
lua-openssl_20161029-1-g8caed30-1.dsc
 cb703b289b2e62ef4a6ce54c71073367a1bc0cba 361928 
lua-openssl_20161029-1-g8caed30.orig.tar.xz
 15fa01f761df867b1dfeab5fc3a8911aff636b28 2712 
lua-openssl_20161029-1-g8caed30-1.debian.tar.xz
Checksums-Sha256:
 698fb501c0f2ec010056eb2ef4c049d1c0f5208cb7287b2299ed068037e050d8 2192 
lua-openssl_20161029-1-g8caed30-1.dsc
 8370ab8ea6142d0fd0531a15335d21920081ddfa46a3a950ac8ce2f84a8d2231 361928 
lua-openssl_20161029-1-g8caed30.orig.tar.xz
 b4d190fadd21878774fa40cfff499049f0c4942d60e764ddb66490e6d04e3785 2712 
lua-openssl_20161029-1-g8caed30-1.debian.tar.xz
Files:
 325af6ec2cae80594e9a03e38a6050e1 2192 interpreters optional 
lua-openssl_20161029-1-g8caed30-1.dsc
 7cdc00d591a66ba7a7edcbe19722bf0e 361928 interpreters optional 
lua-openssl_20161029-1-g8caed30.orig.tar.xz
 91223c5693014e8992c5be5f1459584c 2712 interpreters optional 
lua-openssl_20161029-1-g8caed30-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYFv1xXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHFLQQALlwqC/rcOQUOnl+bg0LRnRs
0H76pSjO7XA301SBl/Xg1ufLorgXEKcjJIEAESVhnWIvI9JH9W9ZFV2SMdtj2X4j
6XSC6TunsC+8I8z3FN/kT2VcmIJFlquIO+cmYJMVIcAakZ3CNAF//CFbdc3S/tvS
TxkMKyS/OPJgm8/rt4vMxCiZZC1+ps5nzFusTgMIyhnoBiLNxgk0HmPANj4AHQPM
LOdiUquLoVu0XsfDKXns8LCRp4GUEmOcITex2VX0ZSxa2txfGRLXPdeP6ktptHBo
WP+8fqTp1PmCD0PX/dNyeJXoujJWFcs7JN3yC2/UNF8JCndcE+faUtDWyuVcqS/Y
JySzKDvfQNus/6ZFcKVLoy10id0LtMQkgpzT7mzLimd9NdJl+qRZfHJUtlQiMxzG
GaNw7zGFoEa1G7b9NFjUwITzbTktUTmJCIju990uzcfpZJn/8U14YYCfKPDBPz9r
kaXjxn+ntIUw8/L5crltftcC+Y8Js6rhjXsvuj87AVvsKqq3RJMFrY6O26yHaSmb
/uZ8RQnzlLhzN/+KJdLafQgONNpP7kVELyJHOf+IHVnVUgkXhCo3/b8/iy80n4qJ

Bug#835785: marked as done (lua-cqueues: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:05:43 +
with message-id 
and subject line Bug#835785: fixed in lua-cqueues 20161018-1
has caused the Debian Bug report #835785,
regarding lua-cqueues: 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.)


-- 
835785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-cqueues
Version: 20160812-1
Severity: important

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-08-26/failed/lua-cqueues_20160812-1_amd64-2016-08-26T19%3A13%3A17Z

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.

Experimental has the libssl-dev 1.1.0 packages in it. 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: lua-cqueues
Source-Version: 20161018-1

We believe that the bug you reported is fixed in the latest version of
lua-cqueues, 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 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated lua-cqueues 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: Thu, 27 Oct 2016 17:23:20 +0200
Source: lua-cqueues
Binary: lua-cqueues lua-cqueues-dev
Architecture: source
Version: 20161018-1
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description:
 lua-cqueues - event loop for Lua
 lua-cqueues-dev - event loop for Lua (development package)
Closes: 835785
Changes:
 lua-cqueues (20161018-1) unstable; urgency=medium
 .
   * Imported Upstream version 20161018
+ Includes openssl 1.1.0 support (Closes: #835785)
   * Remove __typeof__ patch merged upstream
Checksums-Sha1:
 1c44c1b8327427e5ab3215266ca5b6e26f34e01d 2123 lua-cqueues_20161018-1.dsc
 1177df96ebb92ebc7fd7e20207568238f3c823e4 590553 
lua-cqueues_20161018.orig.tar.gz
 c01244aae5586e48a0ad6ba0253dfe17d022bdc6 3032 
lua-cqueues_20161018-1.debian.tar.xz
Checksums-Sha256:
 9ffa0175cfa13b35cc1477df171a9d1b5a5c9a9752c83794e7761e99293a2aae 2123 
lua-cqueues_20161018-1.dsc
 16f6608b9d89327008aa960a8cbb0b48ab4f434f4bcf6647f50765d061d899a9 590553 
lua-cqueues_20161018.orig.tar.gz
 22959000266e8132c5e56241c9d989d11b115e651ee454c549b0d54c79c51fb8 3032 
lua-cqueues_20161018-1.debian.tar.xz
Files:
 4eae03745ccb49bbe620a17166e6583d 2123 interpreters optional 
lua-cqueues_20161018-1.dsc
 e8c08dd692cfc214fd37951f6b3c778a 590553 interpreters optional 
lua-cqueues_20161018.orig.tar.gz
 3b3708b489512c8b2ae8ced0516bfac8 3032 interpreters optional 
lua-cqueues_20161018-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYFv/sXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHh2cQAMJo7SyDt3UAGpBtugwVtuc1
yT6Rxa+zhn478Y0b8LUti0pk2SZMQUP/AQtOsQWRvyjyuPzalzZwt1VY3452O/gJ
vyepEhLws1/+bGUdp1F6QVrKGSjkxC12/OUDnnxhDJf/hQqR2AJ9rFUEtuMgsxou
Mo7+61DhvRyejzTyNbqVU2IB5Nu5oy800tbkwTnmmO376tiQKkYNX3UWQrayCefB
CJRZd/8dzUckcN1BW1R7Ekq2HuKI+n/ETr9oafQ8rAMhlE909GnINDOcWyG4VWIs
EW2ajlMdSbk1RoJvM/otIlu4JTD0hibg5wdm2N4uru2uW4LzzrwvbdKI/cTFn24J
9j6TGAeGCqcyOeQsiub/U+zsGMgaxv9S9cKc1v9R37UGSnC9Kqa2Eb4c3U57dQPB
FIyarhSFcK9UcmF6bAgCmJBBccfG8JBh5yL7h7ik8R0/KqWxRCoCsoXM3k/+xqit
/L6J5+EK71xep6bOuALJTpqsgr+DdsT8i+PZPHNIqM1gIcZ9ruOKwdFWK9g+w/Qm
UGq7OUUbFHHXd1bn2zjVOiGrHtNpyJewfvepmLye7vY+zjM3/ajEhXOvqAqhco3k
hFfM65/ry0zsSBirKtIYiyiKds3K/rCigQJHqIOO1lgGDyRKfe4Mmrq3CjBC503T
2Q6J+rJRvsEmGA2++LKl
=SHAv
-END PGP SIGNATURE End Message ---

Bug#828377: marked as done (ldns: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 09:05:37 +
with message-id 
and subject line Bug#828377: fixed in ldns 1.6.17-10
has caused the Debian Bug report #828377,
regarding ldns: 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.)


-- 
828377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldns
Version: 1.6.17-8
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/ldns_1.6.17-8_amd64-20160529-1438

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: ldns
Source-Version: 1.6.17-10

We believe that the bug you reported is fixed in the latest version of
ldns, 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 ldns 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: Thu, 27 Oct 2016 16:53:07 +0200
Source: ldns
Binary: libldns1 libldns1-dbg libldns-dev ldnsutils python-ldns
Architecture: source
Version: 1.6.17-10
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Ondřej Surý 
Description:
 ldnsutils  - ldns library for DNS programming
 libldns-dev - ldns library for DNS programming
 libldns1   - ldns library for DNS programming
 libldns1-dbg - ldns library for DNS programming (debug symbols)
 python-ldns - Python bindings for the ldns library for DNS programming
Closes: 828377
Changes:
 ldns (1.6.17-10) unstable; urgency=medium
 .
   [ A. Schulze ]
   * experimental support openssl-1.1.x (Closes: #828377)
Checksums-Sha1:
 2f6cfb6fdf6fe950ca570155351a2203977f5d6a 2261 ldns_1.6.17-10.dsc
 2cec4f565c0acf637ed00340033eab47363d5c15 22288 ldns_1.6.17-10.debian.tar.xz
Checksums-Sha256:
 b912a6d0b78723d96760250fd666b3f864b64614c9928cefe949866b8eed146c 2261 
ldns_1.6.17-10.dsc
 7d1378aba1442b95a16b10859306b656041a267f6f3b7c9954ad626095706066 22288 
ldns_1.6.17-10.debian.tar.xz
Files:
 e70ad53b9d8cce3740976379ae2d2a75 2261 net extra ldns_1.6.17-10.dsc
 147753b62d67f8166a5eafd509dfdfa7 22288 net extra ldns_1.6.17-10.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYFv+nXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHQooQAJLvhksbpj0thdTvj27KPLRy
LfxRXWfiTmcTig8hPx21pjDDPji16KyLF4/9W3XZDSiFBKW1hYatKnnS8GZdLuQt
iLoexWLLsaBnXMsbRrKg/TcWLN4t0U+CZ8cN0C9RrkVoRXeVXgeWaWeTPRc39S9L
dM3CN5izS94vMtMAj+wfw2TmFZwA5jGYweb1EQavLSkz1p+juqcVe3GikTiGBXM+
rxI0Z5oI7nrOiN2s1QfTwZK5b1/Gh/7deZwPOJgmkHQ7ePSIy/NcmBsi/K4Ag8TA
idenxCgkIjtoPHw7383ZR4+9JN3zxbAirEpfFj9rwG45ZfXNiDuYx76/ETRDZ7Ce
ivaitYHK9jtxOzEjnBs5KAvhAkELllwsavFzCzftPCvHEOfwslIaBsos7O2FjBBB
mZEi+tVbQRdiVvd2LhWW4Q24bI3ZLDgl3sE91wfiSb7AAayFxl9RQdDtxUsvZ0fu
8PRRfU+rdqhZ0ruPiqAh2+bMLJ0g3R/ly+6ugaZxRhEV7db54lZE9Sznwb6MArqW
vQlWhT8dNIpN0U+TY9CmjeUNYsKc+c4bElnaA+s57BjCgPrUg5jKxWeBOq42v7xW
gkGwe3BqN0lRf/01lujDrLtUCEnok2OdpzSSd6YZYZhjYzgyS74TB6dMbyJydgV1
EehKsYuEGvN0gJtcF9UE
=dihB
-END PGP SIGNATURE End Message ---

Bug#842669: marked as done (node-map-visit: FTBFS (Cannot find module 'should'))

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 10:49:59 +
with message-id 
and subject line Bug#842669: fixed in node-map-visit 0.1.5-2
has caused the Debian Bug report #842669,
regarding node-map-visit: FTBFS (Cannot find module 'should')
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.)


-- 
842669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-map-visit
Version: 0.1.5-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
   dh_auto_build -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha
module.js:327
throw err;
^

Error: Cannot find module 'should'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/<>/test.js:4:1)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
at Array.forEach (native)
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:139:18)
at node.js:974:3
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Looks like a missing build-depends.

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-map-visit
Source-Version: 0.1.5-2

We believe that the bug you reported is fixed in the latest version of
node-map-visit, 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.
Sruthi Chandran  (supplier of updated node-map-visit 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 15:13:13 +0530
Source: node-map-visit
Binary: node-map-visit
Architecture: source
Version: 0.1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Sruthi Chandran 
Description:
 node-map-visit - Map `visit` over an array of objects
Closes: 842669
Changes:
 node-map-visit (0.1.5-2) unstable; urgency=medium
 .
   * Add node-should to builddeps (Closes: #842669)
Checksums-Sha1:
 accdc5f9e8f30ed717304e1e83f5ff655bf34cc1 2094 node-map-visit_0.1.5-2.dsc
 0b133d5ff4d148708d28b3865c219e377d917db4 2108 
node-map-visit_0.1.5-2.debian.tar.xz
Checksums-Sha256:
 d0e512628acfd853727cacf8d331f641efa087c052267fe70f903eb798871854 2094 
node-map-visit_0.1.5-2.dsc
 e8a54701a6a681c1224d746e88d834eeeddd7b4083ca5dc2d5e6dded5ae1621a 2108 
node-map-visit_0.1.5-2.debian.tar.xz
Files:
 4d1bc04bdd4e48c8f8da7aa5a27236b2 2094 web optional node-map-visit_0.1.5-2.dsc
 c07a4f6b504f0adf2f3ce007a9653a51 2108 web optional 
node-map-visit_0.1.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#841772: marked as done (grub-common: grub-mkconfig generates root= with empty UUID, making system unbootable)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 10:48:58 +
with message-id 
and subject line Bug#841741: fixed in grub2 2.02~beta3-2
has caused the Debian Bug report #841741,
regarding grub-common: grub-mkconfig generates root= with empty UUID, making 
system unbootable
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.)


-- 
841741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-common
Version: 2.02~beta3-1
Severity: important

After the most recent upgrade, grub-mkconfig generates an incorrect grub.cfg
with a root= line with empty UUID. In /etc/grub.d/10_linux, l. 68,
uses_abstraction generates an error and returns false, therefore the empty 
UUID in ${GRUB_DEVICE_UUID} is accepted and used.

# /usr/sbin/grub-probe --device /dev/mapper/larus_vg-root --target=abstraction
/usr/sbin/grub-probe: error: disk 
`lvmid/22gcC4-S1nG-73eR-J097-sq3j-0Oly-wg4g2I/iNky0F-bFml-277M-dAuH-0Q2L-6aCh-AXU4ws'
 not found.

/dev/mapper/larus_vg-root is an LVM inside a crypt device.

If I remove 
 && uses_abstraction "${GRUB_DEVICE}" lvm
in 10_linux, then grub-mkconfig uses the device name and booting works.

What I don't understand:
 Why does grub-probe not work?
 Why does 10_linux accept empty UUIDs if uses_abstraction returns false?


-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mapper/larus_vg-root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/larus_vg-usr /usr ext4 rw,relatime,data=ordered 0 0
/dev/sda2 /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 0
/dev/sda1 /boot/efi vfat 
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/mapper/larus_vg-home /home ext4 rw,relatime,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  
ad0ce2a4-4956-4eb8-ab83-6a2eb4720dc5
else
  search --no-floppy --fs-uuid --set=root ad0ce2a4-4956-4eb8-ab83-6a2eb4720dc5
fi
font="/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=de_DE
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  
ad0ce2a4-4956-4eb8-ab83-6a2eb4720dc5
else
  search --no-floppy --fs-uuid --set=root ad0ce2a4-4956-4eb8-ab83-6a2eb4720dc5
fi
insmod png
if background_image /grub/.background_cache.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function 

Bug#842693: npgsql: FTBFS: CSC: error CS0518: The predefined type `System.Object' is not defined or imported

[Chris Lamb]

Source: npgsql
Version: 2.2.7+dfsg3-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,

npgsql fails to build from source in unstable/amd64:

  […]

  Setting up libmono-system-web-http-selfhost4.0-cil (4.6.1.3+dfsg-4) ...
  Setting up libnunit-console-runner2.6.3-cil (2.6.4+dfsg-1) ...
  * Installing 1 assembly from libnunit-console-runner2.6.3-cil into Mono
  Setting up libmono-system-web-webpages-razor2.0-cil (4.6.1.3+dfsg-4) ...
  Setting up libmono-system-web-dynamicdata4.0-cil (4.6.1.3+dfsg-4) ...
  Setting up libmono-system-servicemodel-web4.0-cil (4.6.1.3+dfsg-4) ...
  Setting up libnunit-cil-dev (2.6.4+dfsg-1) ...
  Setting up libmono-system-web-mvc3.0-cil (4.6.1.3+dfsg-4) ...
  Setting up libmono-system-data-services4.0-cil (4.6.1.3+dfsg-4) ...
  Setting up libmono-cil-dev (4.6.1.3+dfsg-4) ...
  Setting up mono-devel (4.6.1.3+dfsg-4) ...
  update-alternatives: using /usr/bin/mono-csc to provide /usr/bin/cli-csc 
(c-sharp-compiler) in auto mode
  update-alternatives: using /usr/bin/resgen to provide /usr/bin/cli-resgen 
(resource-file-generator) in auto mode
  update-alternatives: using /usr/bin/al to provide /usr/bin/cli-al 
(assembly-linker) in auto mode
  update-alternatives: using /usr/bin/sn to provide /usr/bin/cli-sn 
(strong-name-tool) in auto mode
  Setting up cli-common-dev (0.9+nmu1) ...
  Setting up npgsql-build-deps (2.2.7+dfsg3-1) ...
  Processing triggers for libc-bin (2.24-5) ...
  Processing triggers for ca-certificates (20160104) ...
  Updating certificates in /etc/ssl/certs...
  173 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=2512b42bb926
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20161031112522.S3seSzzFeI.db.npgsql/npgsql-2.2.7+dfsg3
  OLDPWD=/home/lamby/temp/cdt.20161031112522.S3seSzzFeI.db.npgsql
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building npgsql 2.2.7+dfsg3-1 on amd64 
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package npgsql
  dpkg-buildpackage: info: source version 2.2.7+dfsg3-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Jo Shields 
   dpkg-source --before-build npgsql-2.2.7+dfsg3
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh --with cli clean 
  dh: Compatibility levels before 9 are deprecated (level 7 in use)
 dh_testdir
 debian/rules override_dh_auto_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161031112522.S3seSzzFeI.db.npgsql/npgsql-2.2.7+dfsg3'
  xbuild Npgsql/Npgsql.csproj /property:Configuration=Release-net45 
/target:clean
  XBuild Engine Version 14.0
  Mono, Version 4.6.1.0
  Copyright (C) 2005-2013 Various Mono authors
  
  Build started 10/31/2016 11:26:46.
  __
  Build succeeded.
 0 Warning(s)
 0 Error(s)
  
  Time Elapsed 00:00:00.1905460
  rm -fr Npgsql/bin/
  rm -fr Npgsql/obj/
  dh_auto_clean
  dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use)
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161031112522.S3seSzzFeI.db.npgsql/npgsql-2.2.7+dfsg3'
 dh_clean
  dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules build
  dh --with cli build 
  dh: Compatibility levels before 9 are deprecated (level 7 in use)
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
  dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in 
use)
 debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161031112522.S3seSzzFeI.db.npgsql/npgsql-2.2.7+dfsg3'
  xbuild Npgsql/Npgsql.csproj /property:Configuration=Release-net45
  XBuild Engine Version 14.0
  

Bug#841622: marked as done (tiledarray: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 13:29:31 +0200
with message-id 
and subject line Re: tiledarray: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create'
has caused the Debian Bug report #841622,
regarding tiledarray: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create'
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.)


-- 
841622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledarray
Version: 0.4.4-2
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):
> /usr/bin/cc  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro  
> CMakeFiles/cmTC_b1b5f.dir/CheckSymbolExists.c.o  -o cmTC_b1b5f -rdynamic 
> CMakeFiles/cmTC_b1b5f.dir/CheckSymbolExists.c.o: In function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
> reference to `pthread_create'
> collect2: error: ld returned 1 exit status

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/tiledarray_0.4.4-2_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 ---

I am unable to reproduce this failure.

I believe this is the relevant section of the log:

/usr/bin/ld: 
/usr/lib/x86_64-linux-gnu/libMADworld.a(libMADworld_a-madness_exception.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
CMakeFiles/cmTC_b8c33.dir/build.make:105: recipe for target 'cmTC_b8c33' 
failed


It was fixed by #837699.--- End Message ---

Bug#842339: marked as done (tar: CVE-2016-6321: Bypassing the extract path name)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 13:06:42 +
with message-id 
and subject line Bug#842339: fixed in tar 1.29b-1.1
has caused the Debian Bug report #842339,
regarding tar: CVE-2016-6321: Bypassing the extract path name
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.)


-- 
842339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tar
Version: 1.29b-1
Severity: grave
Tags: security

This has been assigned CVE-2016-6321:
https://sintonen.fi/advisories/tar-extract-pathname-bypass.txt

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: tar
Source-Version: 1.29b-1.1

We believe that the bug you reported is fixed in the latest version of
tar, 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.
Salvatore Bonaccorso  (supplier of updated tar 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: Sun, 30 Oct 2016 07:35:31 +0100
Source: tar
Binary: tar tar-scripts
Architecture: source
Version: 1.29b-1.1
Distribution: unstable
Urgency: medium
Maintainer: Bdale Garbee 
Changed-By: Salvatore Bonaccorso 
Closes: 842339
Description: 
 tar- GNU version of the tar archiving utility
 tar-scripts - optional scripts for GNU version of the tar archiving utility
Changes:
 tar (1.29b-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * CVE-2016-6321: Bypassing the extract path name.
 When extracting, member names containing '..' components are skipped.
 (Closes: #842339)
Checksums-Sha1: 
 f29387983be4c4e187844b31a3dca5d9ba682350 2057 tar_1.29b-1.1.dsc
 b173024f3ab1f2ba77df662654ec588a19b85058 28484 tar_1.29b-1.1.debian.tar.xz
Checksums-Sha256: 
 9474ed422017e23e8208785c071b9f7765d73d704b9bb19da22699c6581d73ef 2057 
tar_1.29b-1.1.dsc
 380f80af0e87446796f05ba384c5d130ea2ad5978b8cfdcf315503966333ebb9 28484 
tar_1.29b-1.1.debian.tar.xz
Files: 
 038053747784adbbb0b56b1e58b0397c 2057 utils required tar_1.29b-1.1.dsc
 8ca20689e54964b05c6c4c51440762d1 28484 utils required 
tar_1.29b-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKPBAEBCgB5BQJYFZaYXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NjQ0NDA5ODA4QzE3MUUwNTUzMURERUUw
NTRDQjhGMzEzNDNDRjQ0EhxjYXJuaWxAZGViaWFuLm9yZwAKCRAFTLjzE0PPRLW/
D/9rczehCKrzLD1yuYf+eDcxW0exnR4+94FVD6GPXn/JELgfe1dWHEq8H98QIHjw
sSFPlJJU1l0Yaqs1AlIdufQKs+okpEZRSjWJ4aam/2q0KLHyGHyFddQzCLaNxVDT
19AoJzbqXMRSS1e8fPqJZWInMRHk93usmR9OOwG/RAYuC57x79P6SquzYvfjQ6iH
j04Kb1KiNRwyE9AMHitBCipI5vLBin8DWa8IUWfvYp1gUBtURuasf2eqC5lvm3oS
y9mR4t6WBhgqEcfXVE6w+YH1LqKnXMKGO6coXOLJpHwEHE32W4CZ4c6YRHI47IGJ
669jpED+kYYlEJdnXWo4CtnmdiQWQdAqsjQxO6iCPxk4W8uB8MMXlxeWiBDqahW1
PVWrvF8Qf4ozqfaFMS9p2MvkvOD+arUAH5uOr+QIVZBjyecMPasDuP+TAzWffMaf
KYMcCupcwr27iF2nHkfG9NquqegcBZxbXJyGdClGRLcmckiuj0HOpHL3H06HP0B7
+mStvTLjUM6CKDu+YxwZ04przULv26sG9FlfFnAUTnVKlI0rN15HJO225LpbXvFF
CXcWsQtZkKxHZdJWsn9hsHXZeqe+cLuIUMjzR5oVT2Mygy32pAQmVnGil6wOBoMW
vyPN7PWdO6IyrBHgIdpXBShH+59QJFYyONidX6eizJmjog==
=qb9Q
-END PGP SIGNATURE End Message ---

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

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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python-keyring 10.0.2-1
Bug #842500 [src:python-launchpadlib] python-launchpadlib: FTBFS: error: Could 
not find suitable distribution for Requirement.parse('secretstorage')
Bug reassigned from package 'src:python-launchpadlib' to 'python-keyring'.
No longer marked as found in versions python-launchpadlib/1.10.4-1.
Ignoring request to alter fixed versions of bug #842500 to the same values 
previously set
Bug #842500 [python-keyring] python-launchpadlib: FTBFS: error: Could not find 
suitable distribution for Requirement.parse('secretstorage')
Marked as found in versions python-keyring/10.0.2-1.
> affects -1 src:python-launchpadlib
Bug #842500 [python-keyring] python-launchpadlib: FTBFS: error: Could not find 
suitable distribution for Requirement.parse('secretstorage')
Added indication that 842500 affects src:python-launchpadlib

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

Bug#837228: marked as done (chef: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 31 Oct 2016 13:03:39 +
with message-id 
and subject line Bug#837228: fixed in chef 12.14.60-1
has caused the Debian Bug report #837228,
regarding chef: FTBFS: ERROR: Test "ruby2.3" failed.
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.)


-- 
837228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chef
Version: 12.10.24-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 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):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-chef-config/usr/share/rubygems-integration/all:debian/chef/usr/share/rubygems-integration/all:/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\ \"chef\"
> /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
> 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError)
> Checked in 
> 'GEM_PATH=debian/ruby-chef-config/usr/share/rubygems-integration/all:debian/chef/usr/share/rubygems-integration/all:/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/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)
> bundler (1.12.5)
> chef-config (12.10.24)
> chef-zero (5.0.0)
> cheffish (2.0.4)
> compat_resource (12.10.5)
> did_you_mean (1.0.0)
> diff-lcs (1.2.5)
> erubis (2.7.0)
> ffi (1.9.10)
> ffi-yajl (2.2.3)
> fuzzyurl (0.8.0)
> hashie (3.4.4)
> highline (1.7.8)
> io-console (0.4.5)
> ipaddress (0.8.3)
> json (1.8.3)
> mime-types (2.6.1)
> minitest (5.9.0)
> mixlib-authentication (1.4.1)
> mixlib-cli (1.5.0)
> mixlib-config (2.2.1)
> mixlib-log (1.6.0)
> mixlib-shellout (2.2.6)
> molinillo (0.5.0)
> multi_json (1.11.2)
> net-http-persistent (2.9.4)
> net-scp (1.2.1)
> net-sftp (2.1.2)
> net-ssh (3.2.0)
> net-ssh-gateway (1.2.0)
> net-ssh-multi (1.2.1)
> net-telnet (0.1.1)
> ohai (8.10.0)
> plist (3.2.0)
> power_assert (0.2.7)
> proxifier (1.0.3)
> psych (2.0.17)
> rack (1.6.4)
> rake (10.5.0)
> rdoc (4.2.1)
> rspec (3.4.0)
> rspec-core (3.4.3)
> rspec-expectations (3.4.0)
> rspec-its (1.2.0)
> rspec-mocks (3.4.1)
> rspec-support (3.4.1)
> serverspec (2.18.0)
> sigar (0.7.3)
> specinfra (2.35.1)
> syslog-logger (1.6.8)
> systemu (2.6.5)
> test-unit (3.1.7)
> thor (0.19.1)
> thread_order (1.1.0)
> uuidtools (2.1.5)
> ERROR: Test "ruby2.3" failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/chef_12.10.24-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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: chef
Source-Version: 12.14.60-1

We believe that the bug you reported is fixed in the latest version of
chef, 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 

Processed: fixed 840806 in 2.1.0-5+deb8u7

[Debian Bug Tracking System]

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

> fixed 840806 2.1.0-5+deb8u7
Bug #840806 [src:libgd2] libgd2: CVE-2016-6911: invalid read in 
gdImageCreateFromTiffPtr()
Marked as fixed in versions libgd2/2.1.0-5+deb8u7.
> thanks
Stopping processing here.

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

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

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

[Pirate Praveen]

On Mon, 31 Oct 2016 13:06:09 +0100 (CET) Santiago Vila 
wrote:
what's wrong while trying.
> 
> Stupid question: Should this really be [^.].+\. or maybe [^.]+\. ?

I'm not good with ruby either, ccing Balu. Also asking upstream for help
https://github.com/stympy/faker/issues/737



signature.asc
Description: OpenPGP digital signature

Bug#841748: esniper: needs update for recent eBay changes

[Dmitry Smirnov]

On Monday, 31 October 2016 8:48:30 AM AEDT Dima Barsky wrote:
> Thanks for your help, I'm going to apply your changes to the newly
> released esniper 2.32.0. I'll upload it a couple of days.

Fantastic. :) Thank you. Upstream most likely incorporated authentication 
patch into new release but I suppose it is worth double checking...

-- 
All the best,
 Dmitry Smirnov.

---

A wise man proportions his belief to the evidence.
-- David Hume, "An Inquiry Concerning Human Understanding"



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

Bug#842702: Remote Code Execution on Zabbix 2.2 < 3.0.3

[rogeriobastos]

Package: zabbix-frontend-php
Version: 1:2.2.7+dfsg-2+deb8u1
Severity: grave

Zabbix on Jessie is vulnerable to remote code execution through exploit 
available in [1] (valid zabbix user/password is needed).
I do not find any CVE related to this bug.

[1] https://www.exploit-db.com/exploits/39937/

-- 
Rogerio Bastos
PoP-BA/RNP

Processed: Bug #842679 affects haskell-debian

[Debian Bug Tracking System]

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

> affects 842679 + haskell-debian
Bug #842679 [ghc] haskell-debian: FTBFS: ghc: panic! (the 'impossible' happened)
Added indication that 842679 affects haskell-debian
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
842679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842679
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#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

Bug#840806: closed by Ondřej Surý <ond...@debian.org> (Bug#840806: fixed in libgd2 2.2.3-87-gd0fec80-1)

[Salvatore Bonaccorso]

Control: reopen -1 

Hi Ondřej,

While updating the security-tracker information I noticed:

On Mon, Oct 31, 2016 at 10:21:15AM +, Debian Bug Tracking System wrote:
[...]
> + [CVE-2016-6911]: invalid read in gdImageCreateFromTiffPtr()
[...]

For the recently uploaded Version 2.2.3-87-gd0fec80-1. But comparing
this with the patch applied in jessie-security, named
0020-Fix-invalid-read-in-gdImageCreateFromTiffPtr.patch

Is this patch missing for the unstable upload?

I'm reopening the bug just to be on the safe side, but happy to be
corrected if I'm wrong!

Regards,
Salvatore

Processed: squeezelite: NMU ongoing

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #842330 [squeezelite] [PATCH] [RC] Fix syslog.h conflict with upcoming 
lirc-0.9.4
Added tag(s) pending.

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

Processed: Re: Bug#840806 closed by Ondřej Surý <ond...@debian.org> (Bug#840806: fixed in libgd2 2.2.3-87-gd0fec80-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #840806 {Done: Ondřej Surý } [src:libgd2] libgd2: 
CVE-2016-6911: invalid read in gdImageCreateFromTiffPtr()
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libgd2/2.1.0-5+deb8u7 and 
libgd2/2.2.3-87-gd0fec80-1.

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

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

[Lucas Nussbaum]

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.
 
Lucas