Bug#877670: marked as done (bcftools FTBFS on armel, armhf and ppc64el)

[Debian Bug Tracking System]

Your message dated Wed, 08 Nov 2017 07:50:18 +
with message-id 
and subject line Bug#877670: fixed in htslib 1.5-2
has caused the Debian Bug report #877670,
regarding bcftools FTBFS on armel, armhf and ppc64el
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.)


-- 
877670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: bcftools
Version: 1.5-1
Severity: serious

The new version of bcftools no longer builds on ppc64el, it is suffering from 
test failures.


test_mpileup:
/<>/bcftools mpileup -a AD -f /<>/test/mpileup/indel-AD.1.fa 
/<>/test/mpileup/indel-AD.1.bam 2>/dev/null | grep -v ^##bcftools | grep -v ^##reference

The outputs differ:
/<>/test/mpileup/indel-AD.1.out
/<>/test/mpileup/indel-AD.1.out.new
.. failed ...

test_mpileup:
/<>/bcftools mpileup -a AD -f /<>/test/mpileup/indel-AD.1.fa -Ob 
/<>/test/mpileup/indel-AD.1.bam 2>/dev/null | /<>/bcftools view  | grep -v 
^##bcftools | grep -v ^##reference

The outputs differ:
/<>/test/mpileup/indel-AD.1.out
/<>/test/mpileup/indel-AD.1.out.new
.. failed ...

test_mpileup:
/<>/bcftools mpileup -a AD -f /<>/test/mpileup/indel-AD.1.fa 
/<>/test/mpileup/indel-AD.1.cram 2>/dev/null | grep -v ^##bcftools | grep -v ^##reference

The outputs differ:
/<>/test/mpileup/indel-AD.1.out
/<>/test/mpileup/indel-AD.1.out.new
.. failed ...

test_mpileup:
/<>/bcftools mpileup -a AD -f /<>/test/mpileup/indel-AD.1.fa -Ob 
/<>/test/mpileup/indel-AD.1.cram 2>/dev/null | /<>/bcftools view  | grep -v 
^##bcftools | grep -v ^##reference

The outputs differ:
/<>/test/mpileup/indel-AD.1.out
/<>/test/mpileup/indel-AD.1.out.new
.. failed ...
--- End Message ---
--- Begin Message ---
Source: htslib
Source-Version: 1.5-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated htslib 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: Wed, 08 Nov 2017 08:24:26 +0100
Source: htslib
Binary: libhts2 libhts-dev htslib-test tabix
Architecture: source all amd64
Version: 1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 htslib-test - Test data for HTSlib
 libhts-dev - Development files for the HTSlib
 libhts2- C library for high-throughput sequencing data formats
 tabix  - generic indexer for TAB-delimited genome position files
Closes: 877670
Changes:
 htslib (1.5-2) unstable; urgency=medium
 .
   * Apply patch provided by Graham Inggs  to fix FTBFS
 on armel armhf and ppc64el of bcftools
 Closes: #877670
   * Standards-Version: 4.1.1
Checksums-Sha1:
 c4a610f521283243267e4f18bb171bcdcbc09c89 2272 htslib_1.5-2.dsc
 c56ffdffbeac204cb925d717547e8635e6aef538 10172 htslib_1.5-2.debian.tar.xz
 a952ddb9f8062baca02aea7fed74235b33b0866f 798008 htslib-test_1.5-2_all.deb
 d8735e38854bb10b2474eed6e0edaa00be9f9788 7313 htslib_1.5-2_amd64.buildinfo
 01d871a8be3a501cebf79c0d1e5c120233c1c2f4 395964 libhts-dev_1.5-2_amd64.deb
 39d64e59350d405cae1e9c8b2f9533789186ac3f 773008 libhts2-dbgsym_1.5-2_amd64.deb
 2f9e8fdacb12e2019e847761fb5fd9e675000c61 292796 libhts2_1.5-2_amd64.deb
 7d642ef31d4e58b7dd82a8e32f497b5abf75b08e 1904504 tabix-dbgsym_1.5-2_amd64.deb
 cad5f86ff8123b04c70904315578fce2f8bab1ac 316244 tabix_1.5-2_amd64.deb
Checksums-Sha256:
 45b944f3aeecb8fef54507f5546043f35c19a5e12bda2f0e09269f1e760e281a 2272 
htslib_1.5-2.dsc
 51bd1a5d87e79391c07d67414652444a3ea5c54360d0c48ff58603e07f9ac2f8 10172 
htslib_1.5-2.debian.tar.xz
 956d6a847f8b3a15ab83863edcf103a9b3c11ede6a547735ceac29f25348ab2a 798008 
htslib-test_1.5-2_all.deb
 

Bug#878327: marked as done (scons printf regression causes many packages to FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 08 Nov 2017 06:34:58 +
with message-id 
and subject line Bug#878327: fixed in scons 3.0.0-2
has caused the Debian Bug report #878327,
regarding scons printf regression causes many packages to FTBFS
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.)


-- 
878327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scons
Version: 3.0.0-1
Severity: serious
Tags: patch fixed-upstream
Control: affects -1 src:alljoyn-core-1504 src:alljoyn-core-1509 
src:alljoyn-core-1604 src:alljoyn-gateway-1504 src:alljoyn-services-1504 
src:alljoyn-services-1509 src:alljoyn-services-1604 
src:alljoyn-thin-client-1504 src:alljoyn-thin-client-1509 
src:alljoyn-thin-client-1604 src:boswars src:btanks src:create-resources 
src:csstidy src:fceux src:ffmpeg2theora src:glob2 src:globs src:gpsd src:gringo 
src:ibus-sunpinyin src:linuxdcpp src:mixxx src:mongo-cxx-driver-legacy 
src:mypaint src:netpanzer src:nsis src:ori src:opennebula src:pdb2pqr 
src:pingus src:rafkill src:rlvm src:serf src:sndobj src:swift-im src:xboxdrv 
src:xorp src:xsettingsd src:xsunpinyin src:zfs-fuse

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ffmpeg2theora.html

...
scons -c
scons: Reading SConscript files ...
  File "/build/1st/ffmpeg2theora-0.30/SConstruct", line 24

print 'SCons %d.%d.%d or greater is required, but you have an older 
version' % scons_version

   ^

SyntaxError: invalid syntax



The upstream fix is a one-line change (removal) in SConscript.py:
https://github.com/SConsProject/scons/commit/2e0de3c55f22b3eaa7767b69740b898f3d2f46bf
--- End Message ---
--- Begin Message ---
Source: scons
Source-Version: 3.0.0-2

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

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated scons 
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: Fri, 13 Oct 2017 09:08:24 +0200
Source: scons
Binary: scons
Architecture: source all
Version: 3.0.0-2
Distribution: unstable
Urgency: high
Maintainer: Jörg Frings-Fürst 
Changed-By: Jörg Frings-Fürst 
Description:
 scons  - replacement for make
Closes: 878327
Changes:
 scons (3.0.0-2) unstable; urgency=high
 .
   * New patch/0125-printf_regression.patch (Closes: #878327):
 - Support python 2 print statements in SConscripts
   (cherry picked from upstream commit).
   * Declare compliance with Debian Policy 4.1.1. (No changes needed).
Checksums-Sha1:
 6810b538fc00b3ec14da32bcd41a3cadcc29e18e 1899 scons_3.0.0-2.dsc
 1c414e30a3c60a8cb0ce7066676661290ecd0320 11620 scons_3.0.0-2.debian.tar.xz
 8108d7f0edab98f784632825bb28e81016f357dc 534864 scons_3.0.0-2_all.deb
 3e7ba3dc68ecbbaf94c9ecb8a407e1aa6ea0673f 6797 scons_3.0.0-2_amd64.buildinfo
Checksums-Sha256:
 a3904a9f3a12531bdd7f6a17ab94606c498c82b4f8271b58dc5eed5c2dbb6ed5 1899 
scons_3.0.0-2.dsc
 7fc271d4ad03aa4fba359519963c343bd3ca1217b85daa43ae10121238d4e14f 11620 
scons_3.0.0-2.debian.tar.xz
 68bfd9b5b715e444dc6a32ce34072ea953f02e7093911557358ae5792028f959 534864 
scons_3.0.0-2_all.deb
 96d9dda3612b0a3fde86e1cbbb650b486aa7d2e778c3da2999421d01117e060a 6797 
scons_3.0.0-2_amd64.buildinfo
Files:
 929c015e6ed3b4dd8b8b0233d47eba19 1899 devel optional scons_3.0.0-2.dsc
 91a31fd721de4be3241152dc99deb323 11620 devel optional 
scons_3.0.0-2.debian.tar.xz
 42463ebc8b43ec4cbb8c66ec85840c27 534864 devel optional scons_3.0.0-2_all.deb
 816d7c3b8bf921762becbc495e006fbf 6797 devel optional 
scons_3.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAloCoIoACgkQ3OMQ54ZM
yL/YqRAAqqC3dyFG9ubDHyKwDekMviFhQ4elzAK6WsbkzAoLPZde1u0BGnlttS8W
gD698KSTsR+tRDFeFq72ilzs1MNIKdJwg2bmtOFQs8O7+5I/ITda6pQ8Hvl2VA5p
BEnUwFlNELB5iTTMROO7ArTvSXRq7HJG08peUUoEFtb8/tx3Yp3TdTxkYWX6ZtdS

Bug#877844: marked as done (scons printf regression causes many packages to FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 08 Nov 2017 06:34:58 +
with message-id 
and subject line Bug#878327: fixed in scons 3.0.0-2
has caused the Debian Bug report #878327,
regarding scons printf regression causes many packages to FTBFS
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.)


-- 
878327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: d2x-rebirth
Version: 0.58.1-1
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

d2x-rebirth recently started to FTBFS in sid:

   debian/rules override_dh_clean
make[1]: Entering directory '/build/d2x-rebirth-0.58.1'
scons --clean
scons: Reading SConscript files ...
  File "/build/d2x-rebirth-0.58.1/SConstruct", line 134

print "%s: reading SDL settings from `%s`" % (program.PROGRAM_NAME, cmd)

 ^

SyntaxError: invalid syntax

debian/rules:10: recipe for target 'override_dh_clean' failed
make[1]: *** [override_dh_clean] Error 2
make[1]: Leaving directory '/build/d2x-rebirth-0.58.1'


Andreas


d2x-rebirth_0.58.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: scons
Source-Version: 3.0.0-2

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

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated scons 
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: Fri, 13 Oct 2017 09:08:24 +0200
Source: scons
Binary: scons
Architecture: source all
Version: 3.0.0-2
Distribution: unstable
Urgency: high
Maintainer: Jörg Frings-Fürst 
Changed-By: Jörg Frings-Fürst 
Description:
 scons  - replacement for make
Closes: 878327
Changes:
 scons (3.0.0-2) unstable; urgency=high
 .
   * New patch/0125-printf_regression.patch (Closes: #878327):
 - Support python 2 print statements in SConscripts
   (cherry picked from upstream commit).
   * Declare compliance with Debian Policy 4.1.1. (No changes needed).
Checksums-Sha1:
 6810b538fc00b3ec14da32bcd41a3cadcc29e18e 1899 scons_3.0.0-2.dsc
 1c414e30a3c60a8cb0ce7066676661290ecd0320 11620 scons_3.0.0-2.debian.tar.xz
 8108d7f0edab98f784632825bb28e81016f357dc 534864 scons_3.0.0-2_all.deb
 3e7ba3dc68ecbbaf94c9ecb8a407e1aa6ea0673f 6797 scons_3.0.0-2_amd64.buildinfo
Checksums-Sha256:
 a3904a9f3a12531bdd7f6a17ab94606c498c82b4f8271b58dc5eed5c2dbb6ed5 1899 
scons_3.0.0-2.dsc
 7fc271d4ad03aa4fba359519963c343bd3ca1217b85daa43ae10121238d4e14f 11620 
scons_3.0.0-2.debian.tar.xz
 68bfd9b5b715e444dc6a32ce34072ea953f02e7093911557358ae5792028f959 534864 
scons_3.0.0-2_all.deb
 96d9dda3612b0a3fde86e1cbbb650b486aa7d2e778c3da2999421d01117e060a 6797 
scons_3.0.0-2_amd64.buildinfo
Files:
 929c015e6ed3b4dd8b8b0233d47eba19 1899 devel optional scons_3.0.0-2.dsc
 91a31fd721de4be3241152dc99deb323 11620 devel optional 
scons_3.0.0-2.debian.tar.xz
 42463ebc8b43ec4cbb8c66ec85840c27 534864 devel optional scons_3.0.0-2_all.deb
 816d7c3b8bf921762becbc495e006fbf 6797 devel optional 
scons_3.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAloCoIoACgkQ3OMQ54ZM
yL/YqRAAqqC3dyFG9ubDHyKwDekMviFhQ4elzAK6WsbkzAoLPZde1u0BGnlttS8W
gD698KSTsR+tRDFeFq72ilzs1MNIKdJwg2bmtOFQs8O7+5I/ITda6pQ8Hvl2VA5p
BEnUwFlNELB5iTTMROO7ArTvSXRq7HJG08peUUoEFtb8/tx3Yp3TdTxkYWX6ZtdS
4sH+3HofgkN7+GbNpv5g6pfxXffog+WdLhxHTt7KK4gCYcIjf7TEa9naOSrPFw+z
pz1TqmrIC1OZh4/8Bc1GOLOPebBT2oOGqEAXdGwFyHNhUQLQp5/3o/fEICuAp4bT
mu4IsvXZ9UeY0xFhHgougJTCEWSkp6/sDJoYCPHDFfR8fP+ByhB2pDcNg/35cDyD
xHsHMigN++AjyFAU43AP08znPPmVUNUdvvmgHk1ZU9vu+1ptAz+Ifyq8IJ3LNlyI
2aBfvu57221Ps+Z1nu1iEVFD3MQGUv+y3JgFPhgkmgIaeBGGmXhhK+UAgxOhGvol
Ihy8gXS6oS7/qDZ71BZU7jOaOCLbfHHJ82gAQBqN6n5XTUyc9+HP3uB/43g+ZwOM
bU0qQ+4Vr5vinS469aEdYYyoFUU5RnxOaqjl2RZcZECBdtPsQwoCVdntXrcti0Gz
TuLI9zg5eqA0Rztz1/x3NDQAsioXNgaoM8xefyvEpoGHL2xWjkM=
=Dm2U
-END PGP 

Bug#877843: marked as done (scons printf regression causes many packages to FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 08 Nov 2017 06:34:58 +
with message-id 
and subject line Bug#878327: fixed in scons 3.0.0-2
has caused the Debian Bug report #878327,
regarding scons printf regression causes many packages to FTBFS
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.)


-- 
878327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: d1x-rebirth
Version: 0.58.1-1
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

d1x-rebirth recently started to FTBFS in sid:

   debian/rules override_dh_clean
make[1]: Entering directory '/build/d1x-rebirth-0.58.1'
scons --clean
scons: Reading SConscript files ...
  File "/build/d1x-rebirth-0.58.1/SConstruct", line 132

print "%s: reading SDL settings from `%s`" % (program.PROGRAM_NAME, cmd)

 ^

SyntaxError: invalid syntax

debian/rules:10: recipe for target 'override_dh_clean' failed
make[1]: *** [override_dh_clean] Error 2
make[1]: Leaving directory '/build/d1x-rebirth-0.58.1'


Andreas


d1x-rebirth_0.58.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: scons
Source-Version: 3.0.0-2

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

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated scons 
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: Fri, 13 Oct 2017 09:08:24 +0200
Source: scons
Binary: scons
Architecture: source all
Version: 3.0.0-2
Distribution: unstable
Urgency: high
Maintainer: Jörg Frings-Fürst 
Changed-By: Jörg Frings-Fürst 
Description:
 scons  - replacement for make
Closes: 878327
Changes:
 scons (3.0.0-2) unstable; urgency=high
 .
   * New patch/0125-printf_regression.patch (Closes: #878327):
 - Support python 2 print statements in SConscripts
   (cherry picked from upstream commit).
   * Declare compliance with Debian Policy 4.1.1. (No changes needed).
Checksums-Sha1:
 6810b538fc00b3ec14da32bcd41a3cadcc29e18e 1899 scons_3.0.0-2.dsc
 1c414e30a3c60a8cb0ce7066676661290ecd0320 11620 scons_3.0.0-2.debian.tar.xz
 8108d7f0edab98f784632825bb28e81016f357dc 534864 scons_3.0.0-2_all.deb
 3e7ba3dc68ecbbaf94c9ecb8a407e1aa6ea0673f 6797 scons_3.0.0-2_amd64.buildinfo
Checksums-Sha256:
 a3904a9f3a12531bdd7f6a17ab94606c498c82b4f8271b58dc5eed5c2dbb6ed5 1899 
scons_3.0.0-2.dsc
 7fc271d4ad03aa4fba359519963c343bd3ca1217b85daa43ae10121238d4e14f 11620 
scons_3.0.0-2.debian.tar.xz
 68bfd9b5b715e444dc6a32ce34072ea953f02e7093911557358ae5792028f959 534864 
scons_3.0.0-2_all.deb
 96d9dda3612b0a3fde86e1cbbb650b486aa7d2e778c3da2999421d01117e060a 6797 
scons_3.0.0-2_amd64.buildinfo
Files:
 929c015e6ed3b4dd8b8b0233d47eba19 1899 devel optional scons_3.0.0-2.dsc
 91a31fd721de4be3241152dc99deb323 11620 devel optional 
scons_3.0.0-2.debian.tar.xz
 42463ebc8b43ec4cbb8c66ec85840c27 534864 devel optional scons_3.0.0-2_all.deb
 816d7c3b8bf921762becbc495e006fbf 6797 devel optional 
scons_3.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAloCoIoACgkQ3OMQ54ZM
yL/YqRAAqqC3dyFG9ubDHyKwDekMviFhQ4elzAK6WsbkzAoLPZde1u0BGnlttS8W
gD698KSTsR+tRDFeFq72ilzs1MNIKdJwg2bmtOFQs8O7+5I/ITda6pQ8Hvl2VA5p
BEnUwFlNELB5iTTMROO7ArTvSXRq7HJG08peUUoEFtb8/tx3Yp3TdTxkYWX6ZtdS
4sH+3HofgkN7+GbNpv5g6pfxXffog+WdLhxHTt7KK4gCYcIjf7TEa9naOSrPFw+z
pz1TqmrIC1OZh4/8Bc1GOLOPebBT2oOGqEAXdGwFyHNhUQLQp5/3o/fEICuAp4bT
mu4IsvXZ9UeY0xFhHgougJTCEWSkp6/sDJoYCPHDFfR8fP+ByhB2pDcNg/35cDyD
xHsHMigN++AjyFAU43AP08znPPmVUNUdvvmgHk1ZU9vu+1ptAz+Ifyq8IJ3LNlyI
2aBfvu57221Ps+Z1nu1iEVFD3MQGUv+y3JgFPhgkmgIaeBGGmXhhK+UAgxOhGvol
Ihy8gXS6oS7/qDZ71BZU7jOaOCLbfHHJ82gAQBqN6n5XTUyc9+HP3uB/43g+ZwOM
bU0qQ+4Vr5vinS469aEdYYyoFUU5RnxOaqjl2RZcZECBdtPsQwoCVdntXrcti0Gz
TuLI9zg5eqA0Rztz1/x3NDQAsioXNgaoM8xefyvEpoGHL2xWjkM=
=Dm2U
-END PGP 

Processed: your mail

[Debian Bug Tracking System]

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

> owner 880339 !
Bug #880339 [src:golang-github-pingcap-check] golang-github-pingcap-check: 
FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -v -p 16 
github.com/pingcap/check returned exit code 1
Owner recorded as Michael Lustfield .
> thanks
Stopping processing here.

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

Bug#881137: xul-ext-https-everywhere: Please update xul-ext-https-everywhere to version 2017.10.30 by next pu

[Julien Aubin]

Package: xul-ext-https-everywhere
Version: 5.2.8-1
Severity: grave
Justification: renders package unusable

Hi,

Firefox release 59 is coming quite soon to Debian, actually next March for
the
ones using mozilla.debian.net.

By this time current https-everywhere extension won't work anymore as it
does
not
have webext standard. Upstream version 2017.10.30 does follow this standard.

Could you please make it available for next p-u in order to anticipate the
transition ?

Thanks a lot



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

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

Versions of packages xul-ext-https-everywhere depends on:
ii  firefox-esr52.4.0esr-1~deb9u1
ii  icedove1:52.4.0-1~deb9u1
ii  iceweasel  52.4.0esr-1~deb9u1
ii  thunderbird [icedove]  1:52.4.0-1~deb9u1

xul-ext-https-everywhere recommends no packages.

xul-ext-https-everywhere suggests no packages.

-- no debconf information

Bug#881135: xul-ext-ublock-origin: Update ublock-origin to version 1.14.16 by next p-u

[Julien Aubin]

Package: xul-ext-ublock-origin
Version: 1.10.4+dfsg-1
Severity: grave
Justification: renders package unusable

Hi,

Firefox release 59 is coming quite soon to Debian, actually next March for
the
ones using mozilla.debian.net.

By this time current ublock-origin extension won't work anymore as it does
not
have webext standard. Upstream version 1.14.16 does follow this standard.

Could you please make it available for next p-u in order to anticipate the
transition ?

Thanks a lot



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

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

Versions of packages xul-ext-ublock-origin depends on:
ii  firefox-esr52.4.0esr-1~deb9u1
ii  fonts-font-awesome 4.7.0~dfsg-1
ii  icedove1:52.4.0-1~deb9u1
ii  iceweasel  52.4.0esr-1~deb9u1
ii  thunderbird [icedove]  1:52.4.0-1~deb9u1

xul-ext-ublock-origin recommends no packages.

xul-ext-ublock-origin suggests no packages.

-- no debconf information

Bug#880460: marked as done (gnustep-gui-runtime: Depends on gnustep-back0.25)

[Debian Bug Tracking System]

Your message dated Wed, 08 Nov 2017 05:49:19 +
with message-id 
and subject line Bug#880460: fixed in gnustep-gui 0.25.0-5
has caused the Debian Bug report #880460,
regarding gnustep-gui-runtime: Depends on gnustep-back0.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.)


-- 
880460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

We would like to carry out a gnustep-base transition:
libgnustep-base1.24 -> libgnustep-base1.25

The major change is the removal of the garbage collector which was
never used in Debian anyway.  Version 1.25.0-1 is in experimental,
built on all arches except powerpcspe (it looks like it has some
trouble catching up).  We tested all reverse dependencies; there are
two packages which FTBFS [1] but they have been fixed in
unstable/testing so can be binNMUed with the rest.

I don't expect any sourceful uploads for the rdeps.
The automatically generated ben tracker looks correct to me.

Ben file:

title = "gnustep-base";
is_affected = .depends ~ "libgnustep-base1.24" | .depends ~ 
"libgnustep-base1.25";
is_good = .depends ~ "libgnustep-base1.25";
is_bad = .depends ~ "libgnustep-base1.24";

[1] 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag=pkg-gnustep-maintain...@lists.alioth.debian.org=gnustep-base1.25-transition
--- End Message ---
--- Begin Message ---
Source: gnustep-gui
Source-Version: 0.25.0-5

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

Debian distribution maintenance software
pp.
Eric Heintzmann  (supplier of updated gnustep-gui 
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: Wed, 01 Nov 2017 19:47:23 +0100
Source: gnustep-gui
Binary: gnustep-gui-common gnustep-gui-runtime libgnustep-gui0.25 
libgnustep-gui-dev libgnustep-gui0.25-dbg gnustep-gui-doc
Architecture: source all amd64
Version: 0.25.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Eric Heintzmann 
Description:
 gnustep-gui-common - GNUstep GUI Library - common files
 gnustep-gui-doc - Documentation for the GNUstep GUI Library
 gnustep-gui-runtime - GNUstep GUI Library - runtime files
 libgnustep-gui-dev - GNUstep GUI header files and static libraries
 libgnustep-gui0.25 - GNUstep GUI Library
 libgnustep-gui0.25-dbg - GNUstep GUI Library - debugging symbols
Closes: 880460
Changes:
 gnustep-gui (0.25.0-5) unstable; urgency=medium
 .
   * Ensure that gnustep-gui-runtime does not depend on gnustep-back
 (Closes: #880460). Thanks to Yavor Doganov.
Checksums-Sha1:
 976bcb3f6439fd196f5d5e56e52273d8be7763e8 2335 gnustep-gui_0.25.0-5.dsc
 d19766a9592bcacbc14b30dde050177bc9acb945 101892 
gnustep-gui_0.25.0-5.debian.tar.xz
 2c4faf38548a81c5e5da8d727ed08ff0a13b2e5c 793952 
gnustep-gui-common_0.25.0-5_all.deb
 6996d1f4156330b159f7b2cb147d94c6d25209ce 1040444 
gnustep-gui-doc_0.25.0-5_all.deb
 05b17a836970a1137a9ff1af116b7d2b69c8d128 155732 
gnustep-gui-runtime_0.25.0-5_amd64.deb
 900d118a4ceefa26aa756bb7f0a953338527bf72 14036 
gnustep-gui_0.25.0-5_amd64.buildinfo
 157ad8d48f4935cff395e6a6c6dc4497f64f2bee 1778056 
libgnustep-gui-dev_0.25.0-5_amd64.deb
 d9dd30ee4540b3369a4744ce06324d8875e69eed 4346232 
libgnustep-gui0.25-dbg_0.25.0-5_amd64.deb
 6923ec43e398006a478c1fe4b9cb2a0ac5ab7a6e 1573200 
libgnustep-gui0.25_0.25.0-5_amd64.deb
Checksums-Sha256:
 559024020a4a3976237d488d81693aabdfd26c16a0a5c028a5c77e16323d0157 2335 
gnustep-gui_0.25.0-5.dsc
 49f9f556f523fde4d418a587a7db7e8899eb3f2a28342782872e764a2a7b2911 101892 
gnustep-gui_0.25.0-5.debian.tar.xz
 1fba3e6085a44637f80180ec004aadd4d1ecf43d95d4c4111dcfee8cbd5ab635 793952 
gnustep-gui-common_0.25.0-5_all.deb
 983c41c2ee8b629e87d9e03c49b2507fcc61916d075544d026f6ecde4d1575cb 1040444 

Bug#876823: marked as done (isso FTBFS with Sphinx 1.6)

[Debian Bug Tracking System]

Your message dated Wed, 08 Nov 2017 03:52:25 +
with message-id 
and subject line Bug#876823: fixed in isso 0.10.6+git20170928+dfsg-1
has caused the Debian Bug report #876823,
regarding isso FTBFS with Sphinx 1.6
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.)


-- 
876823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isso
Version: 0.10.6-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/isso.html

...
running build_py
creating /build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
copying isso/wsgi.py -> /build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
copying isso/run.py -> /build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
copying isso/migrate.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
copying isso/dispatch.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
copying isso/core.py -> /build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
copying isso/config.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
copying isso/compat.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
copying isso/__init__.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
creating /build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/views
copying isso/views/comments.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/views
copying isso/views/__init__.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/views
creating /build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/utils
copying isso/utils/html.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/utils
copying isso/utils/parse.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/utils
copying isso/utils/http.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/utils
copying isso/utils/hash.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/utils
copying isso/utils/__init__.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/utils
creating /build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/ext
copying isso/ext/notifications.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/ext
copying isso/ext/__init__.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/ext
creating /build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/db
copying isso/db/threads.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/db
copying isso/db/spam.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/db
copying isso/db/preferences.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/db
copying isso/db/comments.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/db
copying isso/db/__init__.py -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso/db
running egg_info
creating isso.egg-info
writing requirements to isso.egg-info/requires.txt
writing isso.egg-info/PKG-INFO
writing top-level names to isso.egg-info/top_level.txt
writing dependency_links to isso.egg-info/dependency_links.txt
writing entry points to isso.egg-info/entry_points.txt
writing manifest file 'isso.egg-info/SOURCES.txt'
reading manifest file 'isso.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'man/man1/isso.1'
warning: no files found matching 'man/man5/isso.conf.5'
warning: no files found matching 'isso/js/embed.min.js'
warning: no files found matching 'isso/js/embed.dev.js'
warning: no files found matching 'isso/js/count.min.js'
warning: no files found matching 'isso/js/count.dev.js'
writing manifest file 'isso.egg-info/SOURCES.txt'
copying isso/defaults.ini -> 
/build/1st/isso-0.10.6/.pybuild/pythonX.Y_2.7/build/isso
PYTHONPATH=. http_proxy='http://127.0.0.1:9/' sphinx-build -N -q -E -bhtml docs 
build/html
WARNING: /build/1st/isso-0.10.6/docs/docs/extras/deployment.rst:216: 
(WARNING/2) Title underline too short.

`Openshift `__
^^
WARNING: /build/1st/isso-0.10.6/docs/docs/extras/deployment.rst:216: 
(WARNING/2) Title underline too short.

`Openshift `__
^^
WARNING: /build/1st/isso-0.10.6/docs/docs/install.rst:9: (ERROR/3) Error in 
"contents" directive:
no content permitted.

.. contents::
:local:
:depth: 1

 .. _install-interludium:
/build/1st/isso-0.10.6/docs/contribute.rst: WARNING: document isn't included in 
any toctree

Bug#872713: marked as done (isso: Missing package dependency python-configparser)

[Debian Bug Tracking System]

Your message dated Wed, 08 Nov 2017 03:52:25 +
with message-id 
and subject line Bug#872713: fixed in isso 0.10.6+git20170928+dfsg-1
has caused the Debian Bug report #872713,
regarding isso: Missing package dependency python-configparser
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.)


-- 
872713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: isso
Version: 0.10.6-2
Severity: normal

Dear Maintainer,

When attempting to run isso, I get the following error message:
$ isso -h
Traceback (most recent call last):
  File "/usr/bin/isso", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", 
line 3049, in 

@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", 
line 3033, in _call_aside

f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", 
line 3062, in _initialize_master_working_set

working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", 
line 658, in _build_master

ws.require(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", 
line 972, in require

needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", 
line 858, in resolve

raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'configparser' distribution was 
not found and is required by isso


After installing python-configparser, it seems to work as expected.
I see that it is listed as a build dependency but looks like it needs
to be added as a dependency for the binary package as well.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages isso depends on:
ii  libjs-sphinxdoc  1.5.6-2
ii  lsb-base 9.20161125
ii  python   2.7.13-2
ii  python-bleach2.0-1
ii  python-html5lib  0.9-1
ii  python-ipaddr2.1.11-2
ii  python-itsdangerous  0.24+dfsg1-2
ii  python-misaka1.0.2-5+b2
ii  python-werkzeug  0.12.2+dfsg1-2

Versions of packages isso recommends:
ii  gunicorn  19.7.1-3

isso suggests no packages.

-- no debconf information

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
--- End Message ---
--- Begin Message ---
Source: isso
Source-Version: 0.10.6+git20170928+dfsg-1

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated isso 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: Sat, 29 Jul 2017 16:35:48 +
Source: isso
Binary: isso
Architecture: source all
Version: 0.10.6+git20170928+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Description:
 isso   - lightweight web-based commenting system
Closes: 872713 876823
Changes:
 isso (0.10.6+git20170928+dfsg-1) unstable; urgency=medium
 .
   * New upstream snapshot.
   * Fix minification.
   * Add missing dependency on python-configobj. Closes: #872713, #876823
   * Drop use of bleach.
   * Bump standards version to 4.1.1 (no changes).
   * Add patch 0004-local-js.patch: Use local copy of embed.min.js
Checksums-Sha1:
 afa92e1c6f0ca866409f779b366255df3bb2c9eb 1872 
isso_0.10.6+git20170928+dfsg-1.dsc
 8237f60aba94329c8f363cc2ef54a2522414af91 149033 
isso_0.10.6+git20170928+dfsg.orig.tar.gz
 a30fdf5eb65e90136f9eb76bb07a03a86eff874a 8900 
isso_0.10.6+git20170928+dfsg-1.debian.tar.xz
 

Bug#880234: marked as done (nibabel: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Wed, 08 Nov 2017 03:54:01 +
with message-id 
and subject line Bug#880234: fixed in nibabel 2.2.0+git11-g2139ce0d-1
has caused the Debian Bug report #880234,
regarding nibabel: FTBFS: Test 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.)


-- 
880234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nibabel
Version: 2.1.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 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):
> ERROR: nibabel.tests.test_orientations.test_io_orientation
> --
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File "/<>/nibabel/tests/test_orientations.py", line 171, in 
> test_io_orientation
> ornt = io_orientation(arr)
>   File "/<>/nibabel/orientations.py", line 71, in io_orientation
> R = np.dot(P[:, keep], Qs[keep])
> IndexError: boolean index did not match indexed array along dimension 0; 
> dimension is 7 but corresponding boolean dimension is 4
> 
> --
> Ran 7311 tests in 42.928s
> 
> FAILED (SKIP=41, errors=1)
> Makefile:94: recipe for target 'unittest' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/nibabel_2.1.0-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: nibabel
Source-Version: 2.2.0+git11-g2139ce0d-1

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated nibabel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 16:43:21 -0500
Source: nibabel
Binary: python-nibabel python3-nibabel python-nibabel-doc
Architecture: source all
Version: 2.2.0+git11-g2139ce0d-1
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Description:
 python-nibabel - Python bindings to various neuroimaging data formats
 python-nibabel-doc - documentation for NiBabel
 python3-nibabel - Python3 bindings to various neuroimaging data formats
Closes: 880234
Changes:
 nibabel (2.2.0+git11-g2139ce0d-1) unstable; urgency=medium
 .
   * New upstream snapshot from 2.2.0-11-g2139ce0d
 - closes some outstanding issues and compatibility problems (Closes:
   #880234)
Checksums-Sha1:
 2e35f2e04fa886d5830e7a3b4bfaede5a9ae189c 2651 
nibabel_2.2.0+git11-g2139ce0d-1.dsc
 675f3db4d84a22f3c751a0f8f1198e6b30556613 3772021 
nibabel_2.2.0+git11-g2139ce0d.orig.tar.gz
 ed2b4d5b76dcacead5da08242d7c49957cda8082 7728 
nibabel_2.2.0+git11-g2139ce0d-1.debian.tar.xz
 baa730442b731bcbcc8642faf94ba9b78de08a00 10861 
nibabel_2.2.0+git11-g2139ce0d-1_amd64.buildinfo
 73476c8c5b583f0af99abd438e2eadf579ad34ad 1698060 
python-nibabel-doc_2.2.0+git11-g2139ce0d-1_all.deb
 0ddaf1d0d5ea714f19a41dd8395de123cc5be057 2211808 
python-nibabel_2.2.0+git11-g2139ce0d-1_all.deb
 edd1d26b06c5b4059f12e0e5a9aa5c1453230f19 2204184 
python3-nibabel_2.2.0+git11-g2139ce0d-1_all.deb
Checksums-Sha256:
 00bee51c413f1a8674a43b7bdb375c904961efbbb1e5d53e7488c527d50bc532 2651 
nibabel_2.2.0+git11-g2139ce0d-1.dsc
 0f7b5e79d6c5daeaea627c90517502bc6c53af9dedaeea1af3fb0be4bb9c7d88 3772021 
nibabel_2.2.0+git11-g2139ce0d.orig.tar.gz
 

Bug#878270: anthy (EUCJP->UTF-8) and *-anthy packages

[dai]

On Tue, Nov 07, 2017 at 11:44:45PM +0900, Osamu Aoki wrote:
> Are *-anthy packages uploaded to cope with this new anthy just like 
> ibus-anthy?
>  fcitx-anthy
>  hime-anthy
>  scim-anthy
>  uim-anthy

They are rebuild with new anthy (libanthy1).

https://release.debian.org/transitions/html/auto-anthy.html

- https://packages.debian.org/unstable/fcitx-anthy (0.2.3-1)
- https://packages.debian.org/unstable/gcin-anthy (2.8.5+dfsg1-4+b1)
- https://packages.debian.org/unstable/hime-anthy 
(0.9.10+git20170427+dfsg1-2+b1)
- https://packages.debian.org/unstable/ibus-anthy (1.5.9-2.1)
- https://packages.debian.org/unstable/scim-anthy (1.2.7-6+b2)
- https://packages.debian.org/unstable/uim-plugins 
(1:1.8.6+gh20161003.0.d63dadd-8)

> Otherwise, they are broken in unstable now. (I did not have time to test
> them yet)

At least, I tested uim-anthy a little, it looks well.

> Even these are updated with manual patches, all these updated package
> needs to move together from unstable to testing.  I am not very familiar
> with this ABI breaking library update.  We may need to add BREAKS: to
> anthy to ensure this.  (I am not sure)  That may reqire to upload -7 for
> anthy.

I am not familiar and not sure, too.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Processed: Bug#867642 marked as pending

[Debian Bug Tracking System]

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

> tag 867642 pending
Bug #867642 [src:capistrano] capistrano: FTBFS: ERROR: Test "ruby2.3" failed:   
   Failure/Error: expect(out).to match(/\bCapistrano Version\b/)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 872713 876823

[Debian Bug Tracking System]

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

> forcemerge 872713 876823
Bug #872713 [isso] isso: Missing package dependency python-configparser
Unable to merge bugs because:
package of #876823 is 'src:isso' not 'isso'
Failed to forcibly merge 872713: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#867642: marked as pending

[Samuel Henrique]

tag 867642 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/pkg-ruby-extras/capistrano.git/commit/?id=33e63eb

---
commit 33e63ebb5f7333bbcb3daa5df002fdd3769641a5
Author: Samuel Henrique 
Date:   Wed Nov 8 01:16:31 2017 -0200

Update changelog

diff --git a/debian/changelog b/debian/changelog
index 540371b..3dac78d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,8 +6,13 @@ capistrano (3.10.0-1) UNRELEASED; urgency=medium
   [ Samuel Henrique ]
   * Add myself to uploaders
   * New upstream version 3.10.0
+  * Bump DH level to 10
+  * Bump Standards-Version to 4.1.1
+  * Bump watch to v4
+  * Use https on d/watch
+  * d/patches/skip_tests: new patch to address FTBFS (closes: #867642)
 
- -- Samuel Henrique   Wed, 08 Nov 2017 00:50:59 -0200
+ -- Samuel Henrique   Wed, 08 Nov 2017 01:15:39 -0200
 
 capistrano (3.6.1-1) unstable; urgency=medium
 

Bug#879886: [Debian-med-packaging] Bug#879886: libhts2: libhts2 needs to handle ABI changes

[Charles Plessy]

Hi Diane and everybody,

Le Tue, Nov 07, 2017 at 05:09:34PM -0800, Diane Trout a écrit :
> 
> I do think we should bring back the symbols file

I think so too.

Symbols file are strange to work with because their update usually goes
through a build failure that outputs a patch, which is not very
intuitive.  And then the patched symbols file has to be edited to remove
the Debian minor version, otherwise it complicates backports etc.
Perhaps it can be simplified, better explained and streamlined.  In any
case, I think that for the htslib it is worth the effort.

> I was wondering if we should split the cram headers into a
> libhts-private-dev so we can at least track what is depending on the
> non-public api.

An ideal solution, and I understand that it may not be easy, would be to
make the upstream users of htslib talk with the htslib developers, so
that they can implement what they want to without needing to access
private functions.  I think that it would fit the aims of both sides.

> I did realize that my thought about updating the SOVERSION might be
> wrong because I was just looking in the source tree for the removed
> functions but I should have been checking the public header files.

Indeed, packages using private functions need to have a tight dependency
on the htslib (unless we are very confident that there are regression
tests that cover this area of the code).  Packages that are more
well-behaved can infer their dependency through the (to be re-added)
symbols file.

Have a nice day,

Charles

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan

Bug#879886: [Debian-med-packaging] libhts2: libhts2 needs to handle ABI changes

[Diane Trout]

Hi everyone,

I talked some with upstream about the symbols issues with htslib2

https://github.com/samtools/htslib/issues/616

They think that cram/*.h are private headers, but because we have a
policy of avoiding convenience copies we made those functions public[1]
because a few applications embed htslib and directly use the private
headers.

I do think we should bring back the symbols file, but I was wondering
if we should split the cram headers into a libhts-private-dev so we can
at least track what is depending on the non-public api.

I did realize that my thought about updating the SOVERSION might be
wrong because I was just looking in the source tree for the removed
functions but I should have been checking the public header files.

Diane

[1] https://anonscm.debian.org/cgit/debian-med/htslib.git/tree/debian/p
atches/htslib-add-cram_to_bam.patch

Processed: Re: [Debian-med-packaging] Bug#877670: Bug#877670: bcftools FTBFS on armel armhf and ppc64el

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 htslib 1.4-1
Bug #877670 [bcftools] bcftools FTBFS on armel, armhf and ppc64el
Bug reassigned from package 'bcftools' to 'htslib'.
No longer marked as found in versions bcftools/1.5-1 and bcftools/1.5-2.
Ignoring request to alter fixed versions of bug #877670 to the same values 
previously set
Bug #877670 [htslib] bcftools FTBFS on armel, armhf and ppc64el
There is no source info for the package 'htslib' at version '1.4-1' with 
architecture ''
Unable to make a source version for version '1.4-1'
Marked as found in versions 1.4-1.
> tags -1 + patch
Bug #877670 [htslib] bcftools FTBFS on armel, armhf and ppc64el
Added tag(s) patch.
> affects -1 bcftools
Bug #877670 [htslib] bcftools FTBFS on armel, armhf and ppc64el
Added indication that 877670 affects bcftools

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

Bug#877670: [Debian-med-packaging] Bug#877670: Bug#877670: bcftools FTBFS on armel armhf and ppc64el

[Graham Inggs]

Control: reassign -1 htslib 1.4-1
Control: tags -1 + patch
Control: affects -1 bcftools

It seems this code appeared in htslib 1.4, but was only tested in bcftools 1.5.
Description: Fix calculation of PLs on ARM and POWER
Bug: https://github.com/samtools/bcftools/issues/702
Bug-Debian: https://bugs.debian.org/877670
Forwarded: https://github.com/samtools/htslib/pull/617
Author: Graham Inggs 
Last-Update: 2017-11-08
--- a/errmod.c
+++ b/errmod.c
@@ -82,10 +82,11 @@
 double le1 = log(1.0 - e);
 for (n = 1; n <= 255; ++n) {
 double *beta = em->beta + (q<<16|n<<8);
-sum1 = sum = 0.0;
-for (k = n; k >= 0; --k, sum1 = sum) {
-sum = sum1 + expl(lC[n<<8|k] + k*le + (n-k)*le1);
-beta[k] = -10. / M_LN10 * logl(sum1 / sum);
+sum1 = lC[n<<8|n] + n*le;
+beta[n] = INFINITY;
+for (k = n - 1; k >= 0; --k, sum1 = sum) {
+sum = sum1 + log1pl(expl(lC[n<<8|k] + k*le + (n-k)*le1 - sum1));
+beta[k] = -10. / M_LN10 * (sum1 - sum);
 }
 }
 }

Bug#881061: python-lz4 FTBFS on big endian: FAIL: test_get_frame_info (test_frame.TestLZ4Frame)

[Thomas Goirand]

Hi James,

I tried to build on zelenka.debian.org, which is a s390 porter box (big
endian), and it failed even more.

Cheers,

Thomas Goirand (zigo)

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> fixed 873860 1.5.9-2.1
Bug #873860 {Done: Takatsugu Nokubi } [src:ibus-anthy] 
ibus-anthy FTBFS: UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in 
position 46: illegal multibyte sequence
Marked as fixed in versions ibus-anthy/1.5.9-2.1.
> tags 873860 buster
Bug #873860 {Done: Takatsugu Nokubi } [src:ibus-anthy] 
ibus-anthy FTBFS: UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in 
position 46: illegal multibyte sequence
Added tag(s) buster.
> thanks
Stopping processing here.

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

Bug#881116: Call trace at debian stretch

[paulo bruck]

Package: linux-image-4.9.0-4-amd64
Version: 4.9.51-1
Severity: critical
Justification: breaks the whole system

Dear Mainteners

Actually I am using kernel from jessie because if I try to use kernel
from strech it hangs at boot  with this message bellow.

Let me know if I could help witn more details.

nov 07 18:10:12 zeus kernel: CPU: 0 PID: 5729 Comm: munin-update
Tainted: G  DO4.9.0-4-amd64 #1
 Debian 4.9.51-1
nov 07 18:10:12 zeus kernel: Hardware name: Gigabyte Technology Co.,
Ltd. P67A-D3-B3/P67A-D3-B3, BIOS F1 03
/03/2011
nov 07 18:10:12 zeus kernel: task: 98ebd40e0040 task.stack: bd4cc8274000
nov 07 18:10:12 zeus kernel: RIP: 0010:[]
[] in_group_p+0x40/0x60
nov 07 18:10:12 zeus kernel: RSP: 0018:bd4cc8277c98  EFLAGS: 00010a07
nov 07 18:10:12 zeus kernel: RAX: 7ced RBX:
41ed RCX: 
nov 07 18:10:13 zeus kernel: RDX: f9db RSI:
7ced RDI: 
nov 07 18:10:13 zeus kernel: RBP: 98ec6f651168 R08:
98eba96d99c0 R09: 2f2f2f2f2f2f2f2f
nov 07 18:10:13 zeus kernel: R10:  R11:
98ebd40e0040 R12: 0081
nov 07 18:10:13 zeus kernel: R13: 0001 R14:
bd4cc8277e90 R15: 
nov 07 18:10:13 zeus kernel: FS:  7f576d6642c0()
GS:98ec7f40() knlGS:
nov 07 18:10:13 zeus kernel: CS:  0010 DS:  ES:  CR0: 80050033
nov 07 18:10:13 zeus kernel: CR2: 98eda96d8d7c CR3:
000232656000 CR4: 000426f0
nov 07 18:10:13 zeus kernel: Stack:
nov 07 18:10:13 zeus kernel:  9320d625 cbf036f6ecc9a92c
98ec6f651168 0081
nov 07 18:10:13 zeus kernel:  bd4cc8277d80 0001
9320d6c4 98ec73ec101d
nov 07 18:10:13 zeus kernel:  fefefefefefefeff bd4cc8277d80
9320fea6 2f2f2f2f2f2f2f2f
nov 07 18:10:13 zeus kernel: Call Trace:
nov 07 18:10:13 zeus kernel:  [] ?
generic_permission+0x105/0x180
nov 07 18:10:13 zeus kernel:  [] ?
__inode_permission+0x24/0xc0
nov 07 18:10:13 zeus kernel:  [] ? link_path_walk+0x86/0x650
nov 07 18:10:13 zeus kernel:  [] ? path_lookupat+0x86/0x120
nov 07 18:10:13 zeus kernel:  [] ? filename_lookup+0xb1/0x180
nov 07 18:10:13 zeus kernel:  [] ?
__check_object_size+0xfa/0x1d8
nov 07 18:10:13 zeus kernel:  [] ?
strncpy_from_user+0x48/0x160
nov 07 18:10:13 zeus kernel:  [] ? getname_flags+0x6a/0x1e0
nov 07 18:10:13 zeus kernel:  [] ? vfs_fstatat+0x59/0xb0
nov 07 18:10:13 zeus kernel:  [] ? SYSC_newstat+0x2a/0x60
nov 07 18:10:13 zeus kernel:  [] ? __do_page_fault+0x2d1/0x510
nov 07 18:10:13 zeus kernel:  [] ?
system_call_fast_compare_end+0xc/0x9b
nov 07 18:10:13 zeus kernel: Code: 3b 78 20 74 38 4c 8b 80 90 00 00 00
4d 85 c0 74 29 41 8b 50 04 85 d2 74 21 31 c9 eb 07 8d 48 01 39 ca 76
16 8d 04 0a d1 e8 89 c6 <41> 3b 7c b0 08 77 eb 73 09 89 c2 39 ca 77 ea
31 c0 c3 b8 01 00
nov 07 18:10:13 zeus kernel: RIP  [] in_group_p+0x40/0x60
nov 07 18:10:13 zeus kernel:  RSP 
nov 07 18:10:13 zeus kernel: CR2: 98eda96d8d7c
nov 07 18:10:13 zeus kernel: ---[ end trace 84c3ad992cd5b40b ]---

-- 
Paulo Ricardo Bruck consultor
tel 011 3596-4881/4882  011 98140-9184 (TIM)
http://www.contatogs.com.br
http://www.protejasuarede.com.br
gpg AAA59989 at wwwkeys.us.pgp.net

Bug#873860: marked as done (ibus-anthy FTBFS: UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in position 46: illegal multibyte sequence)

[Debian Bug Tracking System]

Your message dated Wed, 8 Nov 2017 07:17:50 +0900
with message-id 

and subject line Re: [Pkg-ime-devel] Bug#873860: ibus-anthy FTBFS: 
UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in position 46: 
illegal multibyte sequence
has caused the Debian Bug report #873860,
regarding ibus-anthy FTBFS: UnicodeDecodeError: 'euc_jp' codec can't decode 
byte 0xe5 in position 46: illegal multibyte sequence
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.)


-- 
873860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ibus-anthy
Version: 1.5.9-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes ibus-anthy FTBFS:

https://tests.reproducible-builds.org/debian/history/ibus-anthy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ibus-anthy.html

...
Making all in data
make[3]: Entering directory '/build/1st/ibus-anthy-1.5.9/data'
LC_ALL=C /usr/bin/intltool-merge  -x -u -c ../po/.intltool-merge-cache ../po 
ibus-anthy.appdata.xml.in ibus-anthy.appdata.xml
Generating and caching the translation database
Merging translations into ibus-anthy.appdata.xml.
CREATED ibus-anthy.appdata.xml
Generate emoji.t
Generate zipcode.t
Your file is not eucJP? /usr/share/anthy/zipcode.t
Traceback (most recent call last):
  File "zipcode-textdic.py", line 24, in 
contents = codecs.open(anthy_zipfile, 'r', 'euc_jp').read()
  File "/usr/lib/python3.5/codecs.py", line 698, in read
return self.reader.read(size)
UnicodeDecodeError: 'euc_jp' codec can't decode byte 0xe5 in position 46: 
illegal multibyte sequence

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "zipcode-textdic.py", line 27, in 
contents = open(anthy_zipfile).read()
  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe5 in position 46: 
ordinal not in range(128)
Makefile:653: recipe for target 'zipcode.t' failed
make[3]: *** [zipcode.t] Error 1
--- End Message ---
--- Begin Message ---
On Tue, 31 Oct 2017 23:52:18 +0900 Osamu Aoki  wrote:
> I think 1 should be the way to move forward.
>
> I thought about uploading ibus first but maybe I was wrong.  If you have
> time, please upload fixed package.

I uploaded as -2.1 with the patch. It seems fine according to buildd logs.--- End Message ---

Bug#880982: ifup does not trigger scripts any more after booting

[Guus Sliepen]

On Tue, Nov 07, 2017 at 09:55:17PM +0100, Narcis Garcia wrote:

> Thanks Guus for the suggestion about netplug as alternative.
> Network interface's configurtaion (IP) is already done when hotplugging
> the cable.
> 
> What is not working on same event is the run-parts of scripts in
> /etc/network/if-up.d [...]

Aha. If you are using DHCP, then the DHCP client will probably detect
that the cable is plugged in again at some point, and will assign it an
address. However, ifupdown is never called when that happens, so
ifupdown will not cause any of the scripts to run. Also, ifupdown will
consider the interface to be up all the time, whether the cable is
plugged in or not.

Note that dhclient itself can also run scripts when it gets or loses a
lease, see man dhclient-script.

> (as non-Systemd Debian versions did)

This has nothing to do with systemd vs. sysvinit. Maybe it is caused by
changes in udev. But on my computers, I don't see udev generating any
events when I plug or unplug a network cable...

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature

Bug#880234: Re%3A nibabel%3A FTBFS%3A Test failures

[Yaroslav Halchenko]

Thanks for checking it out!  I will issue an updated package shortly

Cheers and thnks again

On Tue, 07 Nov 2017, Thiago Franco de Moraes wrote:

> Hi

> I cloned the git repo from nibabel and did some tests. I saw the HEAD of 
> upstream doesn't have this problem. The difference from the HEAD to the 2.1.0 
> version in the file with the error is diff I've attached in this email. 
> Applying this diff fix this problem. I think you can send this patch to the 
> guy which packages nibabel.

> Kind regards.



-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#881110: cacti: CVE-2017-16641: arbitrary execution of os commands via path_rrdtool parameter in an action=save request

[Salvatore Bonaccorso]

Source: cacti
Version: 1.1.27+ds1-2
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/Cacti/cacti/issues/1057

Hi,

the following vulnerability was published for cacti.

CVE-2017-16641[0]:
| lib/rrd.php in Cacti 1.1.27 allows remote authenticated administrators
| to execute arbitrary OS commands via the path_rrdtool parameter in an
| action=save request to settings.php.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16641
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16641
[1] https://github.com/Cacti/cacti/issues/1057

Please adjust the affected versions in the BTS as needed, only did
check unstable's version for now source-wise.

Regards,
Salvatore

Bug#880214: marked as done (libjava-gmsh3: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/libjava-gmsh.so)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 21:19:17 +
with message-id 
and subject line Bug#880214: fixed in gmsh 3.0.6+dfsg1-1
has caused the Debian Bug report #880214,
regarding libjava-gmsh3: fails to upgrade from 'testing' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libjava-gmsh.so
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.)


-- 
880214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjava-gmsh3
Version: 3.0.5+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libjava-gmsh3.
  Preparing to unpack .../libjava-gmsh3_3.0.5+dfsg1-1_amd64.deb ...
  Unpacking libjava-gmsh3 (3.0.5+dfsg1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libjava-gmsh3_3.0.5+dfsg1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libjava-gmsh.so', which is 
also in package libjava-gmsh2 2.15.0+dfsg1-3+b2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libjava-gmsh3_3.0.5+dfsg1-1_amd64.deb


cheers,

Andreas


libjava-gmsh2=2.15.0+dfsg1-3+b2_libjava-gmsh3=3.0.5+dfsg1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gmsh
Source-Version: 3.0.6+dfsg1-1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated gmsh 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, 07 Nov 2017 21:08:16 +0100
Source: gmsh
Binary: gmsh gmsh-doc libgmsh-dev libgmsh3 libjava-gmsh3 python-gmsh
Architecture: source
Version: 3.0.6+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 gmsh   - Three-dimensional finite element mesh generator
 gmsh-doc   - Three-dimensional finite element mesh generator - documentation
 libgmsh-dev - Three-dimensional finite element mesh generator. Development file
 libgmsh3   - Three-dimensional finite element mesh generator. Shared library
 libjava-gmsh3 - Three-dimensional finite element mesh generator. Java wrapper
 python-gmsh - Three-dimensional finite element mesh generator. Python wrapper
Closes: 880214
Changes:
 gmsh (3.0.6+dfsg1-1) unstable; urgency=medium
 .
   [ Nico Schlömer ]
   * [ea6f1b0] New upstream version 3.0.6+dfsg1
   * [a3c9b4e] remove upstreamed patches
   * [b80ccf1] add patch for install dirs
   * [a1bcd56] use all hardening options
   * [56a5166] apply multi-arch hints
 .
   [ Anton Gladky ]
   * [b729c42] Add Breaks/Replaces for libjava-gmsh3. (Closes: #880214)
   * [c5a5ac0] Apply cme fix dpkg
Checksums-Sha1:
 72600fdfaf6905e90524e07f71982d40cc602587 2701 gmsh_3.0.6+dfsg1-1.dsc
 0972c945383d04dd7f800f1a93544c5dc1ddffa9 8309592 gmsh_3.0.6+dfsg1.orig.tar.xz
 390ff113ffb429532eb75285091303aaecc9b902 24044 gmsh_3.0.6+dfsg1-1.debian.tar.xz
 4abf2138a59376887941fed9112993922628645a 18167 
gmsh_3.0.6+dfsg1-1_source.buildinfo
Checksums-Sha256:
 9cb6431cfdb74901e8575a4294a433a88ca322fb8684502b91a85c8edf584d75 2701 
gmsh_3.0.6+dfsg1-1.dsc
 109d84ba7d2c82f00d2315755669bb26efd030d91544b38b22e3225b5552ea6f 8309592 
gmsh_3.0.6+dfsg1.orig.tar.xz
 4c5affe1c6107b7a30be54ee353f715699359856aa5975e070795f3b9af103ba 24044 
gmsh_3.0.6+dfsg1-1.debian.tar.xz
 0bcb9cd3b099c61798e961ac9306e7e91860fd86b2043d28e61cc0f2731e52db 18167 

Bug#881095: marked as done (openstack-trove FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 21:20:20 +
with message-id 
and subject line Bug#881095: fixed in openstack-trove 1:8.0.0-1
has caused the Debian Bug report #881095,
regarding openstack-trove FTBFS: test 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.)


-- 
881095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openstack-trove
Version: 1:6.0.0-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes openstack-trove FTBFS:

https://tests.reproducible-builds.org/debian/history/openstack-trove.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openstack-trove.html

...
==
FAIL: common.test_remote.TestCreateNovaClient.test_create_admin_client
common.test_remote.TestCreateNovaClient.test_create_admin_client
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/common/test_remote.py", 
line 423, in test_create_admin_client
self.assertEqual(admin_user, admin_client.client.user)
AttributeError: 'SessionClient' object has no attribute 'user'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_attach_public_ips
taskmanager.test_models.BuiltInstanceTasksTest.test_attach_public_ips
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_attach_replica
taskmanager.test_models.BuiltInstanceTasksTest.test_attach_replica
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: 
taskmanager.test_models.BuiltInstanceTasksTest.test_cleanup_source_on_replica_detach
taskmanager.test_models.BuiltInstanceTasksTest.test_cleanup_source_on_replica_detach
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: 
taskmanager.test_models.BuiltInstanceTasksTest.test_demote_replication_master
taskmanager.test_models.BuiltInstanceTasksTest.test_demote_replication_master
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_detach_public_ips
taskmanager.test_models.BuiltInstanceTasksTest.test_detach_public_ips
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_detach_replica
taskmanager.test_models.BuiltInstanceTasksTest.test_detach_replica
--
_StringException: Traceback (most recent call last):
  File 

Bug#880982: ifup does not trigger scripts any more after booting

[Narcis Garcia]

Thanks Guus for the suggestion about netplug as alternative.
Network interface's configurtaion (IP) is already done when hotplugging
the cable.
What is not working on same event is the run-parts of scripts in
/etc/network/if-up.d (as non-Systemd Debian versions did) and maybe
other directories as:

/etc/network/if-down.d
/etc/network/if-pre-up.d
/etc/network/if-post-down.d

This bad behavior happens when no Desktop/NetworkManager is in effect,
and since Debian 9 is beyond 5 minutes after boot.

I've tried to set TimeoutStartSec=infinity with no success at
/lib/systemd/system/ifup@.service


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.

Bug#881095: marked as pending

[Thomas Goirand]

tag 881095 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/openstack/services/openstack-trove.git/commit/?id=6fa49c5

---
commit 6fa49c5b0353d5d77ecb6e594a3967087c8d0d5e
Author: Thomas Goirand 
Date:   Tue Nov 7 20:59:10 2017 +

Closing #881095

diff --git a/debian/changelog b/debian/changelog
index c3a66f9..a9656af 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 openstack-trove (1:8.0.0-1) unstable; urgency=medium
 
-  * New upstream release.
+  * New upstream release (Closes: #881095).
   * Updating vcs fields.
   * Updating copyright format url.
   * Updating maintainer field.

Processed: Bug#881095 marked as pending

[Debian Bug Tracking System]

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

> tag 881095 pending
Bug #881095 [src:openstack-trove] openstack-trove FTBFS: test failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#881097: libnet-ping-external-perl: long-standing command injection via crafted arguments

[Salvatore Bonaccorso]

Control: retitle -1 libnet-ping-external-perl: CVE-2008-7319: command injection 
via crafted arguments

This issue got assigned CVE-2008-7319.

I have filled #881102 for requesting the removal from unstable.

For stretch and jessie I think the best course would be to have it
removed as well in the next point releases, given no package depends
on it.

Regards,
Salvatore

Processed: Re: Bug#881097: libnet-ping-external-perl: long-standing command injection via crafted arguments

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libnet-ping-external-perl: CVE-2008-7319: command injection via 
> crafted arguments
Bug #881097 [libnet-ping-external-perl] libnet-ping-external-perl: 
long-standing command injection via crafted arguments
Changed Bug title to 'libnet-ping-external-perl: CVE-2008-7319: command 
injection via crafted arguments' from 'libnet-ping-external-perl: long-standing 
command injection via crafted arguments'.

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

Bug#880775: marked as done (mldonkey build depends on removed libgd2*-dev provides)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 20:54:03 +
with message-id 
and subject line Bug#880775: fixed in mldonkey 3.1.6-1
has caused the Debian Bug report #880775,
regarding mldonkey build depends on removed libgd2*-dev provides
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.)


-- 
880775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mldonkey
Version: 3.1.5-3.1
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:mldonkey : Depends: libgd2-xpm-dev but it is not installable


Please change the build dependency to libgd-dev.
--- End Message ---
--- Begin Message ---
Source: mldonkey
Source-Version: 3.1.6-1

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated mldonkey package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 21:18:26 +0100
Source: mldonkey
Binary: mldonkey-server mldonkey-gui
Architecture: source
Version: 3.1.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Description:
 mldonkey-gui - Graphical frontend for mldonkey based on GTK+
 mldonkey-server - Door to the 'donkey' network
Closes: 876735 880775
Changes:
 mldonkey (3.1.6-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream. This release compiles on ocaml 4.05 (closes:  #876735)
 - refreshed patch 0001-Use-usr-bin-see-as-default-previewer.patch
 - dropped patch 0004-Fix-compilation-with-OCaml-4.02.patch
   * Changed build-dependency on libgd2-xpm-dev to libgd-dev (closes: #880775)
   * debian/watch: point to github
   * Debhelper compatibility level 10:
 - dropped build-dependency on autotools-dev
   * Dropped build-dependency on obsolete ocaml-best-compilers
   * Added build-dependency on ocamlbuild
   * Standards-Version 4.1.1
   * - drop debian/mldonkey-gui.menu
Checksums-Sha1:
 ff658fc1bb608b934d7a64cfcf0f0c93ef31 2306 mldonkey_3.1.6-1.dsc
 15bc223a6a38cc5f9e05d14c05d38f624e9aee38 2762882 mldonkey_3.1.6.orig.tar.bz2
 9f0a6fb7b7fae7a634cbebf5f1a6ed8d2689dbf8 107100 mldonkey_3.1.6-1.debian.tar.xz
 56b18bad5067e4ae66c2e44ec68764c71a452dc6 12304 
mldonkey_3.1.6-1_source.buildinfo
Checksums-Sha256:
 cde81dee670ba7ff9a785d46868ddaa67160b45fb1fad3a38a1eba2e6155f824 2306 
mldonkey_3.1.6-1.dsc
 13c458351ea8a1ded92b4f06d749fc23bab50c893891bc92b1566cbafc3c9242 2762882 
mldonkey_3.1.6.orig.tar.bz2
 137b95da4515bf54dafc5a062c5ec9548b33c527d92db77eb7e235162ef30af3 107100 
mldonkey_3.1.6-1.debian.tar.xz
 5c28d3c26125e559524725ef202243080a9f475e7395d47d97f53f146f001fe0 12304 
mldonkey_3.1.6-1_source.buildinfo
Files:
 e463e2bfc2fac423c178923eb57d0acb 2306 net optional mldonkey_3.1.6-1.dsc
 20121d7ec658ff593feb2f09d6350a7b 2762882 net optional 
mldonkey_3.1.6.orig.tar.bz2
 a7f3b79a731e82547f3e97a8f144cf50 107100 net optional 
mldonkey_3.1.6-1.debian.tar.xz
 53ff7c5db667506f5b08f8887e959235 12304 net optional 
mldonkey_3.1.6-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAloCFTQACgkQdFxHZtTK
zf+ePw//bHEE7OjVZceGHO2msY9L4NF6rDMTI+m79Rtt4FoD82T/QHuiX8rWQjUJ
jyGlL2jfLdFqZvDMT6Bd4ixC9Wqc06Mc27JQbXzwXifY0OBkZtlqetJ7u3SfGVS5
s2+hIcV8g0lLEb6uUXwalCzWhIojW9K5ROEJMaq1P9k4GYvyOU6so+v+PFsimW2Y
wwLhqB7pvHqVxb/9vyraEb71Hy4FJiBbiNrXM/ndCYPKmWwG7aDSuNOqwUmCXdi9
31KYsjERJwpG6Nk7snmEK8sG4nuy19GzODfDE7ZxdjCdGYs4UIdcyRdZK4fe/Q12
+MPCt30X1kdSuASJbsDLiZA6S77kalJR6vaZSV16JkoCtpaecUhCNI0aU4V/zyqt
FAl2ZrUmrtsjIiCjAm0aKPaHkErBPP5bIfyl2YOy2iZTgG29c9o05hAJrxvDcnln
6BnJsRV47E8mzAQl5llUt7O3bIKw4/uIMHzzE9gezNLuQzw4R9k/KoN22KrzbAkE
gT1BhFghc/0skzGzPgeSTcS96IWn0Vk4hTK2kknqXFaD2BDhcElS5PlWhgnUyyiC
bvoZCbm0jBNPLLB2PA8628lrSzbNzCMeBMdvk0XxRrn6vdX+Yf9GdT3fzdD/Z0lO
+7+vR754QH3AscOxV4qHr8qG6orkjHoiT75D/1CiHopX1JGr+BY=
=ms9X
-END PGP SIGNATURE End 

Bug#876735: marked as done (mldonkey FTBFS with OCaml 4.05.0)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 20:54:03 +
with message-id 
and subject line Bug#876735: fixed in mldonkey 3.1.6-1
has caused the Debian Bug report #876735,
regarding mldonkey FTBFS with OCaml 4.05.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.)


-- 
876735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mldonkey
Version: 3.1.5-3.1
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make svg_converter.byte utils.opt opt
make[2]: Entering directory '/<>'
/usr/bin/ocamlc.opt -verbose -ccopt "-I /byterun -o src/utils/cdk/zlibstubs.o" 
-ccopt "-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security   -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2  
-pthread" -ccopt "-Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2" -cclib "-lz  " 
-cclib -lbz2 -ccopt "-pthread" -c src/utils/cdk/zlibstubs.c
+ gcc -O2 -fno-strict-aliasing -fwrapv -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
-fPIC -c  -I /byterun -o src/utils/cdk/zlibstubs.o -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security   -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2  -pthread 
-Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -pthread  -I'/usr/lib/ocaml' 
'src/utils/cdk/zlibstubs.c'
src/utils/cdk/zlibstubs.c: In function 'camlzip_update_crc32':
src/utils/cdk/zlibstubs.c:194:28: error: 'uint32' undeclared (first use in this 
function); did you mean 'uint32_t'?
   return copy_int32(crc32((uint32) Int32_val(crc),
^~
uint32_t
src/utils/cdk/zlibstubs.c:194:28: note: each undeclared identifier is reported 
only once for each function it appears in
Makefile:5477: recipe for target 'src/utils/cdk/zlibstubs.o' failed
make[2]: *** [src/utils/cdk/zlibstubs.o] Error 2
--- End Message ---
--- Begin Message ---
Source: mldonkey
Source-Version: 3.1.6-1

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated mldonkey package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 21:18:26 +0100
Source: mldonkey
Binary: mldonkey-server mldonkey-gui
Architecture: source
Version: 3.1.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Description:
 mldonkey-gui - Graphical frontend for mldonkey based on GTK+
 mldonkey-server - Door to the 'donkey' network
Closes: 876735 880775
Changes:
 mldonkey (3.1.6-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream. This release compiles on ocaml 4.05 (closes:  #876735)
 - refreshed patch 0001-Use-usr-bin-see-as-default-previewer.patch
 - dropped patch 0004-Fix-compilation-with-OCaml-4.02.patch
   * Changed build-dependency on libgd2-xpm-dev to libgd-dev (closes: #880775)
   * debian/watch: point to github
   * Debhelper compatibility level 

Bug#880996: ring: FTBFS on mips64el

[James Cowgill]

Hi,

On 06/11/17 19:48, Sebastian Ramacher wrote:
> Source: ring
> Version: 20170912.1.912f772~dfsg1-2
> Severity: serious
> Tags: sid buster
> Control: block 880355 by -1
> 
> ring FTBFS on mips64el during the libva transition:
[...]
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function 
> `ring::RingAccount::useIdentity(std::pair  std::shared_ptr > const&)':
> | ./daemon/src/ringdht/ringaccount.cpp:845: undefined reference to 
> `dht::Value::msgpack_unpack(msgpack::v1::object)'
> | ./daemon/src/ringdht/ringaccount.cpp:845: undefined reference to 
> `dht::Value::msgpack_unpack(msgpack::v1::object)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function 
> `msgpack::v1::type::detail::convert_integer_sign false>::convert(msgpack::v1::object const&)':
> | /usr/include/msgpack/v1/adaptor/int.hpp:46: undefined reference to 
> `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function 
> `dht::IceCandidates::msgpack_unpack(msgpack::v1::object)':
> | /usr/include/opendht/default_types.h:190: undefined reference to 
> `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function 
> `msgpack::v1::type::detail::convert_integer_sign false>::convert(msgpack::v1::object const&)':
> | /usr/include/msgpack/v1/adaptor/int.hpp:46: undefined reference to 
> `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function 
> `dht::IceCandidates::msgpack_unpack(msgpack::v1::object)':
> | /usr/include/opendht/default_types.h:190: undefined reference to 
> `dht::unpackBlob(msgpack::v1::object&)'
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function 
> `msgpack::v1::type::detail::convert_integer_sign false>::convert(msgpack::v1::object const&)':
> | /usr/include/msgpack/v1/adaptor/int.hpp:46: undefined reference to 
> `dht::unpackBlob(msgpack::v1::object&)'
> | 
> ../src/.libs/libring.a(libringacc_la-ringaccount.o):/usr/include/opendht/default_types.h:190:
>  more undefined references to `dht::unpackBlob(msgpack::v1::object&)' follow
> | ../src/.libs/libring.a(libringacc_la-ringaccount.o): In function 
> `msgpack::v1::adaptor::convert void>::operator()(msgpack::v1::object const&, dht::crypto::RevocationList&) 
> const':
> | /usr/include/msgpack/v1/object.hpp:209: undefined reference to 
> `dht::crypto::RevocationList::msgpack_unpack(msgpack::v1::object)'
> | /usr/include/msgpack/v1/object.hpp:209: undefined reference to 
> `dht::crypto::RevocationList::msgpack_unpack(msgpack::v1::object)'
> | collect2: error: ld returned 1 exit status
> | Makefile:628: recipe for target 'dring' failed

The problem is that ring forces the use of the msgpack v1 API, but
opendht uses whatever the default msgpack API was when it was built.
When opendht was originally uploaded this was v1 and everything was
good. Around 1 month ago, opendht was binNMUed on just mips64el and this
caused the mips64el version of opendht to use v2 of the API. Ring then
FTBFS on mips64el because it tried to use the v1 functions which don't
exist anymore.

There needs to be some agreement between ring and opendht as to what
msgpack API to use (both use v1 or v2). I'm not sure what the best
option is, but I would guess that forcing opendht to v1 would fix this.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#867671: libratbag-tools: removal of libratbag-tools/sid makes files disappear from liblur3/testing

[Andreas Beckmann]

On 07/08/2017 03:35 PM, Stephen Kitt wrote:
> As I understand Policy in this case, I’m not convinced this is a violation.
> lur-command.1.gz should never have been in liblur3; it should always have
> been in libratbag-tools. I moved the file from liblur3 to libratbag-tools, and
> added the appropriate Replaces relationship; but as I understand it, Breaks
> isn’t needed because the upgrade doesn’t actually break liblur3.

It breaks anything assuming that a certain file exists if a certain
(buggy) package version is installed.

> Considering
> the behaviour described in footnote 54 (53 doesn’t apply here AFAICT), I don’t
> think there’s a problem: the old liblur3 does end up missing a file, but it’s
> a file it doesn’t need and should never have had, so its disappearance
> doesn’t cause any problems.

"its disappearance doesn’t cause any problems"
That's something very hard to teach some automated tools. These tools
look for things that could be problematic (or become problematic at some
point).

What's the actual problem with adding the matching Breaks?
That's just going to invalidate some version mixtures and downgrade
paths that you don't want to support anyway.


Andreas

Bug#881107: gb (build) depends on the obsolete golang-1.8-go

[Adrian Bunk]

Source: gb
Version: 0.4.4-1
Severity: serious

gb depends and build depends on the obsolete golang-1.8-go.

Bug#881105: golang-github-nebulouslabs-fastrand build depends on the obsolete golang-1.8-go

[Adrian Bunk]

Source: golang-github-nebulouslabs-fastrand
Version: 0.0~git20170420.0.5a1a312-1
Severity: serious

golang-github-nebulouslabs-fastrand build depends on the
obsolete golang-1.8-go.

Bug#881101: eyed3 FTBFS with LC_ALL=C

[Adrian Bunk]

Source: eyed3
Version: 0.8.3-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/eyed3.html

...
dh clean --with python2,python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py clean 
running clean
removing '/build/1st/eyed3-0.8.3/.pybuild/pythonX.Y_2.7/build' (and everything 
under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-2.7' does not exist -- can't clean it
I: pybuild base:184: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 108, in 
PKG_INFO, REQUIREMENTS = getPackageInfo()
  File "setup.py", line 72, in getPackageInfo
history = history_file.read().replace(".. :changelog:", "")
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 11969: 
ordinal not in range(128)
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit code 13
debian/rules:10: recipe for target 'clean' failed
make: *** [clean] Error 25

Processed: Title fix

[Debian Bug Tracking System]

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

> retitle 881096 python-asyncssh FTBFS: test failures
Bug #881096 [src:python-asyncssh] python-asyncssh FTBFS: test falures
Changed Bug title to 'python-asyncssh FTBFS: test failures' from 
'python-asyncssh FTBFS: test falures'.
> thanks
Stopping processing here.

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

Bug#843926: jemalloc hard codes page size during build

[Faidon Liambotis]

On Tue, Nov 07, 2017 at 05:07:42PM +, James Cowgill wrote:
> Ah nevermind - I see it FTBFS in experimental on lots of arches.

Yeah, I've fixed some in git already and been working with upstream on a
lot of those (upstream #761, #979, #985, #999). They've been extremely
collaborative (and even trying to make sure breakages on non-x86 won't
happen again, #1044).

I'm currently waiting for either a backport of one of the fixes or a
release, the latter being blocked on them figuring out their release
strategy (#1049).

Regards,
Faidon

Bug#881065: marked as done (python-django-compressor: B-D on obsolete transitional package python3-appconf)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 19:19:38 +
with message-id 
and subject line Bug#881065: fixed in python-django-compressor 2.2-3
has caused the Debian Bug report #881065,
regarding python-django-compressor: B-D on obsolete transitional package 
python3-appconf
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.)


-- 
881065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-compressor
Version: 2.2-1
Severity: serious
Justification: fails to build from source

python3-appconf is now gone from sid.
Please switch to python3-django-appconf.

Andreas
--- End Message ---
--- Begin Message ---
Source: python-django-compressor
Source-Version: 2.2-3

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-django-compressor 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 15:00:06 +
Source: python-django-compressor
Binary: python-django-compressor python3-django-compressor
Architecture: source all
Version: 2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-django-compressor - Compresses linked, inline JS or CSS into single 
cached files - Py
 python3-django-compressor - Compresses linked, inline JS or CSS into single 
cached files - Py
Closes: 881065
Changes:
 python-django-compressor (2.2-3) unstable; urgency=medium
 .
   * Fixed python{3,}-django-appconf instead of just -appconf (Closes: #881065).
Checksums-Sha1:
 adef1912dcffceba761c61d632ca3cad264913b5 2801 
python-django-compressor_2.2-3.dsc
 7fdc9c5c10f7dc81206fed3380ff04a4c2fccdf3 4552 
python-django-compressor_2.2-3.debian.tar.xz
 fb38be05f6fea2ef1eaa548562fe08c75e01b40b 71980 
python-django-compressor_2.2-3_all.deb
 0d63a2376a8c8495542750cbfd2be30d6119a24d 9771 
python-django-compressor_2.2-3_amd64.buildinfo
 188516de25e7303a93f2d48194a669db15991a70 71812 
python3-django-compressor_2.2-3_all.deb
Checksums-Sha256:
 644ca80559df9ad7a6466c1a89cb00609da1e6c666190cc46765639f74bdb707 2801 
python-django-compressor_2.2-3.dsc
 06e0c60e839c55660b14d4f8f0afcad0dbfffb1433201cf08e9c0a9cf6400721 4552 
python-django-compressor_2.2-3.debian.tar.xz
 a321e524c27f02a7a4adac8cf30a9e68351d2488917520b9f43f2ec9acaa2d0c 71980 
python-django-compressor_2.2-3_all.deb
 4510ef9507e501f1ee007a3158abd0b3fe14de370ca967463992bc2273f898e6 9771 
python-django-compressor_2.2-3_amd64.buildinfo
 f14b7773f3edb5b5d55af5f422fd6f82fa99f2377c17250f489acade6363d50e 71812 
python3-django-compressor_2.2-3_all.deb
Files:
 eb010921eae195b17abd6dab8fc79b91 2801 python optional 
python-django-compressor_2.2-3.dsc
 066e58a323b6090fcc40188ec1ab182c 4552 python optional 
python-django-compressor_2.2-3.debian.tar.xz
 fc7d7991c2291d83d78c96aca875f726 71980 python optional 
python-django-compressor_2.2-3_all.deb
 0d49ac52ffdb1bedf56920ecf6167a3f 9771 python optional 
python-django-compressor_2.2-3_amd64.buildinfo
 2b65b0044545577b6a33b8e59e9a5478 71812 python optional 
python3-django-compressor_2.2-3_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAloCAwQACgkQ1BatFaxr
Q/4T+hAAl4Gazr8M0dBtHajlQakHhqz/bICLYUnlMG6IUWBkBGpE6MtNCKPzvRNN
tJsA0t3XDfL+l8PRrSpLG08Cn04WZmeIth4so6oFcr/f0/Dv9vD0FsJOAtWc4ODi
yoj8/qrESBlLSEY4tRI2IA+1rOtvv8V2rLiOAmRbCLTJTuVUE0TdumdTHTExeMXg
lKRPNgsNrwXJ4P2mhpskUX5OdBDqclt5ePySaks7MlXTgbPJMxn0vlnrhzuJE0R0
XT7bhy7vyOv61hi3w3WMvkb9BZb0kZv2dueJP1/xUBPXyRX1mDpAUqv8GSMHQCnW
7URg343jfSutyHSR1fZ1xS9BO4yx55GKhmQEsxXNCV+R5XdYndHUFJWQ/1nOvTHe
Co5u5EzCwaAvnbcfnO/NU1m3amY3YHNPieqJlgdoywZxlexOjYkXu7qLtB50e1td
9iaH4/3zOid8RSQ4Mt1tJnlb4Kj16DLiZ6ud8O6TC+Nn311tcJUM9cQvcnwlGnof
4er6S977SN2OifuBV1R7dkcN2KlSfEC+CHI9fsMa1kLaj8vzUTB5DlTPo8PvViLH

Processed: Bug#881065 marked as pending

[Debian Bug Tracking System]

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

> tag 881065 pending
Bug #881065 [src:python-django-compressor] python-django-compressor: B-D on 
obsolete transitional package python3-appconf
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#881065: marked as pending

[Thomas Goirand]

tag 881065 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/openstack/python/python-django-compressor.git/commit/?id=7ac532f

---
commit 7ac532fe0f55376170a31032d1ee8e39ea8566b4
Author: Thomas Goirand 
Date:   Tue Nov 7 15:00:51 2017 +

Fixed python{3,}-django-appconf instead of just -appconf (Closes: #881065).

diff --git a/debian/changelog b/debian/changelog
index b9dd88a..0407cfe 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-django-compressor (2.2-3) unstable; urgency=medium
+
+  * Fixed python{3,}-django-appconf instead of just -appconf (Closes: #881065).
+
+ -- Thomas Goirand   Tue, 07 Nov 2017 15:00:06 +
+
 python-django-compressor (2.2-2) unstable; urgency=medium
 
   * Removed python-django-discover-runner as build-depends.

Bug#880234: Re%3A nibabel%3A FTBFS%3A Test failures

[Thiago Franco de Moraes]

Hi

I cloned the git repo from nibabel and did some tests. I saw the HEAD of 
upstream doesn't have this problem. The difference from the HEAD to the 2.1.0 
version in the file with the error is diff I've attached in this email. 
Applying this diff fix this problem. I think you can send this patch to the guy 
which packages nibabel.

Kind regards.diff --git a/nibabel/orientations.py b/nibabel/orientations.py
index 2567b41..bc85173 100644
--- a/nibabel/orientations.py
+++ b/nibabel/orientations.py
@@ -63,7 +63,7 @@ def io_orientation(affine, tol=None):
 RS = RZS / zooms
 # Transform below is polar decomposition, returning the closest
 # shearless matrix R to RS
-P, S, Qs = npl.svd(RS)
+P, S, Qs = npl.svd(RS, full_matrices=False)
 # Threshold the singular values to determine the rank.
 if tol is None:
 tol = S.max() * max(RS.shape) * np.finfo(S.dtype).eps

Bug#879637: Ping?

[Lisandro Damián Nicanor Pérez Meyer]

Hi! Would it be possible at least to ignore the tests on mips64el for the time 
being? This has been stopping the Qt transition for too long already.

Thanks!

-- 
 1: Una computadora sirve:
* Para tratar de dominar el mundo, un caso conocido de esto fue el de
  Skinet
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#881097: libnet-ping-external-perl: long-standing command injection via crafted arguments

[Simon McVittie]

Package: libnet-ping-external-perl
Version: 0.13-1
Severity: grave
Tags: security patch upstream
Justification: user security hole
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=33230

See forwarded message below. The reporter's proposed patch is also
attached.

The proposed patch seems to pretend to be a new upstream release, which
seems weird to me, but it isn't my patch.

For what it's worth, dak says nothing in unstable depends on this
package; so perhaps it's time to remove it from Debian.

smcv

- Forwarded message from Matthias Weckbecker  
-

Date: Tue, 7 Nov 2017 17:51:27 +0100
From: Matthias Weckbecker 
To: oss-secur...@lists.openwall.com
Subject: [oss-security] Net::Ping::External command injections
Message-ID: <20171107165127.ga1...@weckbecker.name>

Hi,

Net::Ping::External [0] is prone to command injection vulnerabilities.

The issues are roughly 10 (!) years old [1], but the code is still being
shipped these days (e.g. in ubuntu artful and debian stretch [2]).

I had contacted the author of the code a few days ago, but obviously did
not get any reaction.

A patch is available here:

  http://matthias.sdfeu.org/devel/net-ping-external-cmd-injection.patch

Maybe time to just patch it downstream? Or drop this pkg. altogether?

Thanks,
Matthias

--
[0] https://metacpan.org/pod/Net::Ping::External
[1] https://rt.cpan.org/Public/Dist/Display.html?Name=Net-Ping-External
(id #33230)
[2] https://packages.debian.org/stable/perl/libnet-ping-external-perl \
https://launchpad.net/ubuntu/+source/libnet-ping-external-perl

- End forwarded message -
>From b3dd4de6417f5f9d06710fc185ae6b4ee3661c45 Mon Sep 17 00:00:00 2001
From: Matthias Weckbecker 
Date: Fri, 27 Oct 2017 15:01:10 +0200
Subject: [PATCH 1/1] Fix 10 year old command injection vulnerability

---
 Changes |  3 +++
 External.pm | 24 
 test.pl | 53 +++--
 3 files changed, 74 insertions(+), 6 deletions(-)

diff --git a/Changes b/Changes
index 283ad4d..f36f0d0 100644
--- a/Changes
+++ b/Changes
@@ -8,6 +8,9 @@ newer versions of Net::Ping::External.
 - Support Debian GNU/kFreeBSD
 - ping location on Darwin
 
+0.16 2017-10-27
+- Fix 10 year old command injection vulnerability
+
 0.15 2014-04-12
 - Better detect Windows ping under Cygwin
 - Add ping output for test 2 if it fails
diff --git a/External.pm b/External.pm
index eb472bd..82bc0b8 100644
--- a/External.pm
+++ b/External.pm
@@ -15,11 +15,26 @@ use Carp;
 use Socket qw(inet_ntoa);
 require Exporter;
 
-$VERSION = "0.15";
+$VERSION = "0.16";
 @ISA = qw(Exporter);
 @EXPORT = qw();
 @EXPORT_OK = qw(ping);
 
+sub _clean_args {
+  my %args = @_;
+  for my $arg (qw(size count timeout)) {
+  if ($args{$arg} !~ /([0-9]+)/) {
+croak("$arg must be numeric");
+  }
+  $args{$arg} = $1;
+  }
+  if ($args{host} !~ /([A-Z0-9\.\-]+)/i) {
+croak("invalid host");
+  }
+  $args{host} = $1;
+  return %args;
+}
+
 sub ping {
   # Set up defaults & override defaults with parameters sent.
   my %args = (count => 1, size => 56, @_);
@@ -34,7 +49,7 @@ sub ping {
   croak("You must provide a hostname") unless defined $args{host};
   $args{timeout} = 5 unless defined $args{timeout} && $args{timeout} > 0;
 
-  my %dispatch = 
+  my %dispatch =
 (linux=> \&_ping_linux,
  gnukfreebsd => \&_ping_linux, #Debian GNU/kFreeBSD
  mswin32  => \&_ping_win32,
@@ -61,6 +76,7 @@ sub ping {
 
   croak("External ping not supported on your system") unless $subref;
 
+  %args = _clean_args(%args);
   return $subref->(%args);
 }
 
@@ -83,7 +99,7 @@ sub _ping_win32 {
 }
 
 # Mac OS X 10.2 ping does not handle -w timeout now does it return a
-# status code if it fails to ping (unless it cannot resolve the domain 
+# status code if it fails to ping (unless it cannot resolve the domain
 # name)
 # Thanks to Peter N. Lewis for this one.
 sub _ping_darwin {
@@ -201,7 +217,7 @@ sub _ping_netbsd {
 # -s size option supported -- superuser only... fixme
 sub _ping_bsd {
   my %args = @_;
-  my $command = "ping -c $args{count} -q $args{hostname}";
+  my $command = "ping -c $args{count} -q $args{host}";
   return _ping_system($command, 0);
 }
 
diff --git a/test.pl b/test.pl
index 591f6d4..29c5bc8 100644
--- a/test.pl
+++ b/test.pl
@@ -6,7 +6,7 @@
 # Change 1..1 below to 1..last_test_to_print .
 # (It may become useful if the test is moved to ./t subdirectory.)
 
-BEGIN { $| = 1; $num_tests = 6; print "1..$num_tests\n"; }
+BEGIN { $| = 1; $num_tests = 8; print "1..$num_tests\n"; }
 END {print "not ok 1\n" unless $loaded;}
 use Net::Ping::External qw(ping);
 $loaded = 1;
@@ -24,7 +24,12 @@ $Net::Ping::External::DEBUG_OUTPUT = 1;
 	   3 => "ping(host => '127.0.0.1', timeout => 5)",
 	   4 => "ping(host => 'some.non.existent.host.')",
 	   5 => "ping(host => '127.0.0.1', count => 10)",
-	   6 => "ping(host => '127.0.0.1', size => 32)"
+	   6 => "ping(host 

Processed: Re: Bug#879673: ffmpeg 3.4 API compat layer not 100% backwards compatible

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:kodi src:gst-libav1.0
Bug #879673 [ffmpeg] ffmpeg 3.4 API compat layer not 100% backwards compatible
Added indication that 879673 affects src:kodi and src:gst-libav1.0

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

Bug#879673: ffmpeg 3.4 API compat layer not 100% backwards compatible

[James Cowgill]

Control: affects -1 src:kodi src:gst-libav1.0


Control: tags -1 patch

Hi,

On 24/10/17 09:52, Sebastian Dröge wrote:
> Package: ffmpeg
> Version: 7:3.4-1
> Severity: serious
> 
> Hi,
> 
> ffmpeg 3.4 comes with a new decoding API (among other things), and
> provides a compatibility layer around that for the old API.
> Unfortunately this compatibility layer is apparently not 100% backwards
> compatible or buggy. It breaks at least h264 decoding with gst-
> libav1.0, but then probably also breaks other packages.
> 
> gst-libav upstream bug can be found here:
> https://bugzilla.gnome.org/show_bug.cgi?id=789193
> 
> We'll try to port over to the new API but it looks like some effort,
> and even independent of that the compatibility layer should either be
> fixed or the soname of the libraries has to be updated.

Unfortunately there doesn't seem to have been a lot of activity on the
upstream bug report from FFmpeg themselves. Based on what I can infer
from the source code, I think there is no API breakage here. The
documentation on draining packets in the old API is pretty poor and it
"worked" with ffmpeg < 3.4 so people started using it that way. However,
I think that even under the old API, drain packets can only be sent at
the end of a stream. This seems to make the most sense and aligns with
new the API (where the documentation does say that this is required).

I think the best solution is to apply the attached workaround for the
time being to the Debian package. The workaround will call
avcodec_flush_buffers automatically when it detects that a data packet
has been sent to avcodec_decode_* after the codec has been completely
drained. This allows gst-libav1.0 and kodi (which I also discovered does
this) to play video again.

I am wondering why gst-libav1.0 needs to drain the code at every
discontinuity in the stream? I would have thought there are two separate
cases here: seeking where you want to reset the codec, and dropped
packets where you allow the codec itself to fix the stream (as best it can).

Thanks,
James
diff --git a/debian/patches/0003-reset-codec-after-eof.patch b/debian/patches/0003-reset-codec-after-eof.patch
new file mode 100644
index ..a8bb7692
--- /dev/null
+++ b/debian/patches/0003-reset-codec-after-eof.patch
@@ -0,0 +1,34 @@
+Description: lavc: reset codec on receiving packet after EOF
+ In ffmpeg 3.4, the deprecated avcodec_decode_* APIs were reworked so that they
+ called into the new avcodec_send_packet / avcodec_receive_frame API. This had
+ the side effect of prohibiting sending new packets containing data after a
+ NULL packet. In the new API, it is documented that a NULL packet means EOF.
+ .
+ While the documentation is sparse in this area. It seems that a NULL packet
+ also meant EOF in the old API, but since it was unclear and worked, a few
+ applications assumed that it was ok to to continue sending data after an EOF,
+ and subsequently broke with ffmpeg 3.4.
+ .
+ This patch adds a workaround to the old API which will reset the codec
+ (allowing new data) if a packet is received after an EOF. Hopefully this
+ allow these applications to continue to work with newer ffmpeg.
+Author: James Cowgill 
+Bug: https://trac.ffmpeg.org/ticket/6775
+Bug-Debian: https://bugs.debian.org/879673
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/libavcodec/decode.c
 b/libavcodec/decode.c
+@@ -753,6 +753,12 @@ static int compat_decode(AVCodecContext
+ 
+ av_assert0(avci->compat_decode_consumed == 0);
+ 
++if (avci->draining_done && pkt && pkt->size != 0) {
++av_log(avctx, AV_LOG_WARNING,
++"Got unexpected packet after EOF. Resetting codec and continuing...\n");
++avcodec_flush_buffers(avctx);
++}
++
+ *got_frame = 0;
+ avci->compat_decode = 1;
+ 
diff --git a/debian/patches/series b/debian/patches/series
index bb700bb6..4fe4a0d2 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 0001-arm-thumb2-blx.patch
 0002-arm-Check-for-have_vfp_vm-instead-of-have_vfpv3.patch
+0003-reset-codec-after-eof.patch


signature.asc
Description: OpenPGP digital signature

Bug#880266: marked as done (eztrace FTBFS on big endian: test hang)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 17:49:10 +
with message-id 
and subject line Bug#880266: fixed in eztrace 1.1-7-3
has caused the Debian Bug report #880266,
regarding eztrace FTBFS on big endian: test hang
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.)


-- 
880266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eztrace
Version: 1.1-7-1
Severity: serious

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

...
make  check-TESTS
make[4]: Entering directory '/<>/build-mpich/test/automake'
make[5]: Entering directory '/<>/build-mpich/test/automake'
PASS: teststdio
PASS: testmemory
FAIL: teststatic
FAIL: testopenmpsimple
PASS: testopenmplock
PASS: testopenmpnestlock
FAIL: testmpiring
E: Build killed with signal TERM after 150 minutes of inactivity
--- End Message ---
--- Begin Message ---
Source: eztrace
Source-Version: 1.1-7-3

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated eztrace 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, 07 Nov 2017 18:42:45 +0100
Source: eztrace
Binary: eztrace libeztrace-dev libeztrace0
Architecture: source amd64
Version: 1.1-7-3
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 eztrace- Automatic execution trace generation for HPC - tools
 libeztrace-dev - Automatic execution trace generation for HPC - development 
files
 libeztrace0 - Automatic execution trace generation for HPC - development files
Closes: 880266
Changes:
 eztrace (1.1-7-3) unstable; urgency=medium
 .
   * patches/big-endian-fix: Complete fix for hang on big-endian archs (Closes: 
Bug#880266)
Checksums-Sha1:
 c0483c1c62f3092aad5e582a4da6244f3a2f5cc3 2300 eztrace_1.1-7-3.dsc
 9953c015c0f548db93ac19d759a2b86be1403a92 9464 eztrace_1.1-7-3.debian.tar.xz
 28e7168912fd567fa92bb8255db86be7da62062d 2079444 
eztrace-dbgsym_1.1-7-3_amd64.deb
 0ba1ae003c64b72b66d48306b189d8d6cfd96644 8351 eztrace_1.1-7-3_amd64.buildinfo
 1c192a2d36d82a1a8f34e455e6c389735c575df8 502512 eztrace_1.1-7-3_amd64.deb
 33fb5e34eff3b5b7ac9e3cf4c829b3daaa4c378a 20552 libeztrace-dev_1.1-7-3_amd64.deb
 ca7500a9f4f82b1d6c4b152adc7a91171d2b4e38 1553988 
libeztrace0-dbgsym_1.1-7-3_amd64.deb
 fdae589470c4a1e03f0c431e714253db2b9c40aa 235216 libeztrace0_1.1-7-3_amd64.deb
Checksums-Sha256:
 2a0bb43b53d937bb01e62a76daadb89f5ed96feded47163196f3b2bf212005cf 2300 
eztrace_1.1-7-3.dsc
 118fe9e0d4702ab4706afdf48241049bdcf18e7324df901ba05fb527d84a1806 9464 
eztrace_1.1-7-3.debian.tar.xz
 f8a6f765c2369ef94b27030c5bfea9acc2132a55f336e69ede2fda2047629510 2079444 
eztrace-dbgsym_1.1-7-3_amd64.deb
 548752fca55325597616b0a46b508e491fbf09f6822ffe9735acdbc9afaa5293 8351 
eztrace_1.1-7-3_amd64.buildinfo
 2c673a82f9922f6de15354f5ca18e003dee928cbac1e3331069f1b204d7665b5 502512 
eztrace_1.1-7-3_amd64.deb
 1bc9add5e823876120b361dc465de77edac52b5f0c8ea79847ed6076213b1663 20552 
libeztrace-dev_1.1-7-3_amd64.deb
 217ce68acb2fdb6cae9b25dec62849e869354d61780e3096dd38438d3081ac88 1553988 
libeztrace0-dbgsym_1.1-7-3_amd64.deb
 d0a4861340eb389a86fc4fcc42c4b82d040fe99611a787e2b3064b9ef9c8c49e 235216 
libeztrace0_1.1-7-3_amd64.deb
Files:
 e8faf6986444373151602e8131ac3b6c 2300 devel optional eztrace_1.1-7-3.dsc
 158dc5c47d6141ce4807fe7468fda5dd 9464 devel optional 
eztrace_1.1-7-3.debian.tar.xz
 2f7f4382ac512c8ca45b0d1b182bcbd3 2079444 debug optional 
eztrace-dbgsym_1.1-7-3_amd64.deb
 06bf43e77ef21e6f515fb010bccf2a28 8351 devel optional 
eztrace_1.1-7-3_amd64.buildinfo
 536bd69d1a84f45908e89d273a7879ad 502512 devel optional 
eztrace_1.1-7-3_amd64.deb
 9680d79aac6e16110278a8702b7ab241 20552 libdevel optional 
libeztrace-dev_1.1-7-3_amd64.deb
 0ca7154c202647722ea62b76ee4e3cab 1553988 debug optional 
libeztrace0-dbgsym_1.1-7-3_amd64.deb
 

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

[Jérémy Lal]

2017-10-25 16:04 GMT+02:00 Pirate Praveen :

> On ബുധന്‍ 25 ഒക്ടോബര്‍ 2017 07:08 വൈകു, Pirate Praveen wrote:
> > I can reach the segfaulting point faster by setting break point at
> > thread creation
> >
> > b pthread_create.c:333
> >
> > after 8 c, I reach the segfault point.
> >
> >
> >
>
> hopefully more useful bt
>
> (gdb) bt
> #0  node::fs_req_wrap::~fs_req_wrap (this=,
> __in_chrg=) at ../src/node_file.cc:334
> #1  node::Open (args=...) at ../src/node_file.cc:1063
> #2  0x3b905decccb8 in ?? ()
> #3  0x7fff8fc7a418 in ?? ()
> #4  0x7fff8fc7a468 in ?? ()
> #5  0x0003 in ?? ()
> #6  0x in ?? ()
> (gdb) s
> node::Open (args=...) at ../src/node_file.cc:1064
> 1064in ../src/node_file.cc
> (gdb) bt
> #0  node::Open (args=...) at ../src/node_file.cc:1064
> #1  0x3b905decccb8 in ?? ()
> #2  0x7fff8fc7a418 in ?? ()
> #3  0x7fff8fc7a468 in ?? ()
> #4  0x0003 in ?? ()
> #5  0x in ?? ()
> (gdb) s
> v8::ReturnValue::Set (i=, this=)
> at ../src/node_file.cc:1064
> 1064in ../src/node_file.cc
> (gdb) s
> v8::internal::Internals::IntToSmi (value=)
> at ../src/node_file.cc:1064
> 1064in ../src/node_file.cc
> (gdb) s
> v8::internal::SmiTagging<8ul>::IntToSmi (value=)
> at ../src/node_file.cc:1064
> 1064in ../src/node_file.cc
> (gdb) s
> v8::internal::IntToSmi<31> (value=)
> at ../deps/v8/include/v8.h:7274
> 7274../deps/v8/include/v8.h: No such file or directory.
> (gdb) s
> node::Open (args=...) at ../src/node_file.cc:1063
> 1063../src/node_file.cc: No such file or directory.
> (gdb) s
> node::fs_req_wrap::~fs_req_wrap (this=0x7fff8fc79db0,
> __in_chrg=) at ../src/node_file.cc:334
> 334 in ../src/node_file.cc
> (gdb) s
> uv_fs_req_cleanup (req=req@entry=0x7fff8fc79db0) at src/unix/fs.c:1351
> 1351src/unix/fs.c: No such file or directory.
> (gdb) s
> 1357in src/unix/fs.c
> (gdb) s
> 1363in src/unix/fs.c
> (gdb) s
> 1360in src/unix/fs.c
> (gdb) s
> 1361in src/unix/fs.c
> (gdb) s
> 1363in src/unix/fs.c
> (gdb) s
> 1366in src/unix/fs.c
> (gdb) s
> 1367in src/unix/fs.c
> (gdb)
> uv__free (ptr=0x0) at src/uv-common.c:78
> 78  src/uv-common.c: No such file or directory.
> (gdb)
> 84  in src/uv-common.c
> (gdb)
> __errno_location () at ../csu/errno-loc.c:26
> 26  ../csu/errno-loc.c: No such file or directory.
> (gdb)
> 27  in ../csu/errno-loc.c
> (gdb)
> uv__free (ptr=0x0) at src/uv-common.c:85
> 85  src/uv-common.c: No such file or directory.
> (gdb)
> __GI___libc_free (mem=0x0) at malloc.c:2954
>

This points a lot to a libuv bug.

Now that ilbuv 1.11 is in unstable, can you update and post results here ?

Jérémy

Bug#881091: marked as done (converseen FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 17:34:34 +
with message-id 
and subject line Bug#881091: fixed in converseen 0.9.6.2-2
has caused the Debian Bug report #881091,
regarding converseen FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev
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.)


-- 
881091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: converseen
Version: 0.9.6.2-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/converseen.html

...
CMake Error at CMakeLists.txt:94 (FIND_PACKAGE):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...
--- End Message ---
--- Begin Message ---
Source: converseen
Source-Version: 0.9.6.2-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated converseen 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 16:41:45 +
Source: converseen
Binary: converseen
Architecture: source amd64
Version: 0.9.6.2-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 converseen - batch image converter and resizer
Closes: 881091
Changes:
 converseen (0.9.6.2-2) unstable; urgency=medium
 .
   * Update build dependencies (closes: #881091).
   * Update Standards-Version to 4.1.1:
 - change package priority to optional.
Checksums-Sha1:
 9da1e6a1ca28c11d74fab950c9da9caa6aa6aaaf 1855 converseen_0.9.6.2-2.dsc
 7cc533cd80af426b4d12934384730cf8e64e3404 2988 
converseen_0.9.6.2-2.debian.tar.xz
 e6d67fd9111436189f8dfcd79ae45a7eb544af91 3839864 
converseen-dbgsym_0.9.6.2-2_amd64.deb
 6e5abb7720038309098f5ecbca29960c8ce73230 16258 
converseen_0.9.6.2-2_amd64.buildinfo
 b2c923af6938267ff78abbb98f1ed1a02a783de1 281128 converseen_0.9.6.2-2_amd64.deb
Checksums-Sha256:
 9af0b07313aefd9c441b0de84909cf2a24f66db43be6a86ba43a7549cd740ba0 1855 
converseen_0.9.6.2-2.dsc
 8e3c07ef28a432401b7d0879bb8e98439ed6930e03a517b4e264e22e40e7593f 2988 
converseen_0.9.6.2-2.debian.tar.xz
 917f5590dd7f2d1f4898039b0a3736dc98b45bdfbd63d1ece86028351eaf9591 3839864 
converseen-dbgsym_0.9.6.2-2_amd64.deb
 4a90efaa2efdf10783ced017f9045225bdccd5a683950e80dadb21e62ff69f45 16258 
converseen_0.9.6.2-2_amd64.buildinfo
 969bcc16c7ac8e2f7f150d22c9d94b99367ddacfb636082bbbd8ddb40a042c82 281128 
converseen_0.9.6.2-2_amd64.deb
Files:
 ce3ed4c13dad11c3865ec4c202a51fdd 1855 graphics optional 
converseen_0.9.6.2-2.dsc
 3e0b8983c78916a0a34c8b3816b38f74 2988 graphics optional 
converseen_0.9.6.2-2.debian.tar.xz
 ceeeb27df8fe5cacdb39439a6d931a9b 3839864 debug optional 
converseen-dbgsym_0.9.6.2-2_amd64.deb
 5cf958a7ed4f69311184a9430dd2d9d6 16258 graphics optional 
converseen_0.9.6.2-2_amd64.buildinfo
 21cb73df10bdebe72b5208e70e8bf09a 281128 graphics optional 
converseen_0.9.6.2-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAloB6PoACgkQ3OMQ54ZM
yL8zUQ//e3oJMrGQibVJnl7jtTYyLbgG7UqX5nvPBbt7D68oCE506GDBWfjgmMMK
wrXYramBVKGaH4p8UtGQAAlqIs5vqWz0SzVjj3lAkZyyCJZ/W81Zcv79R/AX/vKa

Bug#880304: marked as done (user-mode-linux: FTBFS: build-dependency not installable: linux-source-4.9)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 17:21:19 +
with message-id 
and subject line Bug#880304: fixed in user-mode-linux 4.13-1um-1
has caused the Debian Bug report #880304,
regarding user-mode-linux: FTBFS: build-dependency not installable: 
linux-source-4.9
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.)


-- 
880304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: user-mode-linux
Version: 4.9-1um-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>> 9.0.0), quilt, linux-source-4.9, 
> docbook-to-man, xz-utils, m4, kmod, libvdeplug2-dev, libpcap-dev, bc, dpkg 
> (>= 1.16.2), libssl-dev
> Filtered Build-Depends: debhelper (>> 9.0.0), quilt, linux-source-4.9, 
> docbook-to-man, xz-utils, m4, kmod, libvdeplug2-dev, libpcap-dev, bc, dpkg 
> (>= 1.16.2), libssl-dev
> dpkg-deb: building package 'sbuild-build-depends-user-mode-linux-dummy' in 
> '/<>/resolver-UyZ5I0/apt_archive/sbuild-build-depends-user-mode-linux-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-user-mode-linux-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-UyZ5I0/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-UyZ5I0/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-UyZ5I0/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-UyZ5I0/apt_archive ./ Sources [576 B]
> Get:5 copy:/<>/resolver-UyZ5I0/apt_archive ./ Packages [661 B]
> Fetched 2200 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install user-mode-linux build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-user-mode-linux-dummy : Depends: linux-source-4.9 but 
> it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/user-mode-linux_4.9-1um-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: user-mode-linux
Source-Version: 4.13-1um-1

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated user-mode-linux 
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, 07 Nov 2017 21:53:50 +0530
Source: user-mode-linux
Binary: user-mode-linux
Architecture: source amd64
Version: 4.13-1um-1
Distribution: unstable
Urgency: 

Bug#879231: security update: ruby2.3

[Antonio Terceiro]

On Sat, Nov 04, 2017 at 10:08:36PM +0100, Salvatore Bonaccorso wrote:
> Hi Antonio
> 
> Sorry for the late reply
> 
> On Mon, Oct 23, 2017 at 11:49:28AM -0200, Antonio Terceiro wrote:
> > Hi security team,
> > 
> > I have prepared a security update for ruby2.3.
> > 
> > It includes all the pending recent CVE's, plus a fix for a bug that
> > causes runaway child processes hogging the CPU, noticed at least in
> > puppet.
> 
> For the later one, not directly a security issue, strictly speaking we
> would need an ack from the SRM to see they would ack it to a point
> release and then we can pick it as well for a security update. The
> patch though looks confined enough that I would trust it's okay as
> well for SRM to see it included (Cc'ed explicity Adam).
> 
> > The test suite still passes both during build, and under autopkgtest. I
> > am running these packages on my workstation since yesterday. The patches
> > are targeted enough that I don't expect any regressions.
> > 
> > As I explained before, unfortunately the patch management for ruby2.3 is
> > not optimal, so I attach both the debdiff and the individual patches
> > that I applied to the git repository. The later will make your review
> > work easier.
> > 
> > You can also inspect the git repository:
> > https://anonscm.debian.org/cgit/collab-maint/ruby.git/log/?h=debian/stretch
> 
> Yes thank you. Please go ahead with the upload to security-master
> (unless you in meanwhile have found any regression caused by the
> update on your workstation).

Uploaded.


signature.asc
Description: PGP signature

Bug#881074: marked as done (qcomicbook FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 17:20:25 +
with message-id 
and subject line Bug#881074: fixed in qcomicbook 0.9.1-2
has caused the Debian Bug report #881074,
regarding qcomicbook FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev
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.)


-- 
881074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qcomicbook
Version: 0.9.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qcomicbook.html

...
CMake Error at CMakeLists.txt:23 (FIND_PACKAGE):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.



qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...
--- End Message ---
--- Begin Message ---
Source: qcomicbook
Source-Version: 0.9.1-2

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated qcomicbook 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, 07 Nov 2017 19:02:11 +0200
Source: qcomicbook
Binary: qcomicbook
Architecture: source
Version: 0.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 qcomicbook - qt viewer for comic book archives (cbr/cbz/cba/cbg/cbb)
Closes: 881074
Changes:
 qcomicbook (0.9.1-2) unstable; urgency=medium
 .
   * QA upload.
   * Build-depend on qttools5-dev. (Closes: #881074)
Checksums-Sha1:
 ad4f5a911d58f7f55c37d1c95fbe97c64b07276f 1880 qcomicbook_0.9.1-2.dsc
 e0cf799823242565239737becb8c49cc950a60dd 4468 qcomicbook_0.9.1-2.debian.tar.xz
Checksums-Sha256:
 2f45525153cc307b158a4b8e5fbec29f3902df218845a2c9a527dee4a5e3b155 1880 
qcomicbook_0.9.1-2.dsc
 684c0a82eb7e79f9c7fe1dcf7b1e2bb6162605cbfdb857100ff6bade8311d7db 4468 
qcomicbook_0.9.1-2.debian.tar.xz
Files:
 0a61356fac5d1529ba8d459ccf5c32dc 1880 graphics optional qcomicbook_0.9.1-2.dsc
 2ab7e24b4981ec8658a7401468a36e64 4468 graphics optional 
qcomicbook_0.9.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAloB58wACgkQiNJCh6LY
mLHfaRAApAQrQl6LqBWstK5R999eIcrMV+OVKjakptWnj11plicNuBDyXqmksGZ4
q8M+AqWjptrug4Za4bAms1I5iis55GNTBTxe1fE+6cFFMvnS1XykZWKqD9uOzq6d
AodwzFf6B2TSfmL0KBeWMd19shavIgRWEvhmsTw/7PIhYO2YXUg6I/DkLl1JWOtr
kugj5zW0NpftS/tyK71s98FhvjSszRgBXlgGxkMcHebQ23Ju9fvqBgskSlyx6YS/
R+EIgvzhYzRRyeiErbUzffxrX3taGO+gVrPthkmlgMlEXqFOczoVPk9CPc50oUr+
wa+ONRagb5JzEkqax8o3Xnz1ar0jpaAhLmGgSn5JK1Sf1EuX1KNLeeJJ66bNQNJH
XVRA4xm9+l5pvAvRLi30uXrX3W+XHI/K7EEd/alSr9+YXWWYAfMnKSjwFVLiG1EW
epnt4bu1LxRGlATpaPhednMmuwGZa4TEDA1AAgZ+gV9v94EYfvCQCZ/t4HzLQln0
yM8VLSFwulyB4e04EMA7cZsV2tMsgDvlIy257FcG4PohONS61OySjJZ8p0Jn9Ze4
IsuYrV35zXDQz48pQgjQxjhEjZUya5Mh2BWHhLhyJwGOGXQs6Glc0nrlnGLNiWOw
dvEqTktJbpoI9Nx4eCO9k09bg+dwM8PjzOrsqB13d8vCp75x0hA=
=9b24
-END PGP SIGNATURE End Message ---

Bug#880867: marked as done (gnome-recipes FTBFS with meson 0.43.0: Invalid kwargs for option "autoar": "default")

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 17:19:29 +
with message-id 
and subject line Bug#880867: fixed in gnome-recipes 2.0.0-1
has caused the Debian Bug report #880867,
regarding gnome-recipes FTBFS with meson 0.43.0: Invalid kwargs for option 
"autoar": "default"
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.)


-- 
880867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-recipes
Version: 1.6.2-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-recipes.html

...
The Meson build system
Version: 0.43.0
Source dir: /build/1st/gnome-recipes-1.6.2
Build dir: /build/1st/gnome-recipes-1.6.2/obj-x86_64-linux-gnu
Build type: native build

Meson encountered an error in file meson_options.txt, line 1, column 0:
Invalid kwargs for option "autoar": "default"
--- End Message ---
--- Begin Message ---
Source: gnome-recipes
Source-Version: 2.0.0-1

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gnome-recipes 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, 07 Nov 2017 11:28:50 -0500
Source: gnome-recipes
Binary: gnome-recipes gnome-recipes-data
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gnome-recipes - Recipe application for GNOME
 gnome-recipes-data - Recipe application for GNOME (data files)
Closes: 880867
Changes:
 gnome-recipes (2.0.0-1) unstable; urgency=medium
 .
   [ Paul van Tilburg ]
   * New upstream release (Closes: #880867)
   * debian/control.in:
 - Bump the standards version to 4.1.1; no changes required
 - Add (new) build-depends on libgoa-1.0-dev, libjson-glib-dev and
   librest-dev
 - Set multi-arch flag to foreign for gnome-recipes-data
   * debian/gnome-recipes.manpages, debian/gnome-recipes.1: add a man page
   * debian/recipes*: remove files used from old "recipes" package name
Checksums-Sha1:
 b74f170ebdd1876888cf0fb7578aad14b7403c46 2294 gnome-recipes_2.0.0-1.dsc
 39f6331965721f939a299b7c2487a764b911e34f 18050764 
gnome-recipes_2.0.0.orig.tar.xz
 a9698e84ccecd1b1e9f40a2e7f037c6f7867cf2f 7704 
gnome-recipes_2.0.0-1.debian.tar.xz
 eab658a3497a28ca2c89d946509e25e5e0608d85 17274 
gnome-recipes_2.0.0-1_source.buildinfo
Checksums-Sha256:
 6b1fb411672590d83b2db47d328b5c58452f4a80e3a4e39e5059002b0f3f71c0 2294 
gnome-recipes_2.0.0-1.dsc
 a853f46add4454b3bec984fbcff83c2f32b2b488eb817dc8249f7906b2d9af71 18050764 
gnome-recipes_2.0.0.orig.tar.xz
 2e02fe6b8e0bfddec6af305a5a1009709e2094c80280af0b8713ea1ea01722e9 7704 
gnome-recipes_2.0.0-1.debian.tar.xz
 255d02e1dec89422de0b8490a66ea9158f75db6b6c2ac3025360ccfc9c257de2 17274 
gnome-recipes_2.0.0-1_source.buildinfo
Files:
 819d96b5bc453964af0080041c9fa7d0 2294 gnome optional gnome-recipes_2.0.0-1.dsc
 86b3a82067314d53da9d2739a973dec9 18050764 gnome optional 
gnome-recipes_2.0.0.orig.tar.xz
 ac2029a55872e9f16d324b58cedc7c58 7704 gnome optional 
gnome-recipes_2.0.0-1.debian.tar.xz
 c714d6d3405aac6f331df355e68de6f2 17274 gnome optional 
gnome-recipes_2.0.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaAehrAAoJEOZsd1rr/mx9mHIQAImLdXAAfW48kyAUFILXAro+
q3T9BSdKeUtn01i2jw/yPeGoaCQz0YdCPuY4nWGAcLdqfrrHZFkH4+OIrC+1dBP2
Q9GoXiVUqkgofn0iEzTKQ/g4Im5NBiql7iFZc7/dYuKjcFv0kH8QYY379wwnKDXO
+5TzqoxBrPRza6B4taZvfhRfeEeA0BQFUJFi5EkpQlh8RKSACNd3tnBn0b2pgKyM
kh5lndWjR5VQrFv6GI8Von4vfDJBopD9fz3kBPtfYZUogBWAni3nNgUj3THx8xED
eyzZR4L3TfvMrKe3wGG5UW7GMc6TNfESCSf3lyz77JuGUFdlkhdqXbcGWhFyH+Gs
WjFSu8/KGXLj7xpyVrqIb9Dg7giNbylGdC0Xl5zcyjs+l5eKL/Z40xPUWMDwgCni
qQjdaARqTelpsXkaK4KhG5XozAO8VQfCOOIEm7QBxlu+TbUn+pd0Lh2XMJ0bnxFV
7d2YHCKqL9wRno3FBtteyZ6/JPyaizPJ1Qb3ngQ1h2FxNBzx0RBLT8WkSynHVcU5

Bug#881095: openstack-trove FTBFS: test failures

[Adrian Bunk]

Source: openstack-trove
Version: 1:6.0.0-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes openstack-trove FTBFS:

https://tests.reproducible-builds.org/debian/history/openstack-trove.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openstack-trove.html

...
==
FAIL: common.test_remote.TestCreateNovaClient.test_create_admin_client
common.test_remote.TestCreateNovaClient.test_create_admin_client
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/common/test_remote.py", 
line 423, in test_create_admin_client
self.assertEqual(admin_user, admin_client.client.user)
AttributeError: 'SessionClient' object has no attribute 'user'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_attach_public_ips
taskmanager.test_models.BuiltInstanceTasksTest.test_attach_public_ips
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_attach_replica
taskmanager.test_models.BuiltInstanceTasksTest.test_attach_replica
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: 
taskmanager.test_models.BuiltInstanceTasksTest.test_cleanup_source_on_replica_detach
taskmanager.test_models.BuiltInstanceTasksTest.test_cleanup_source_on_replica_detach
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: 
taskmanager.test_models.BuiltInstanceTasksTest.test_demote_replication_master
taskmanager.test_models.BuiltInstanceTasksTest.test_demote_replication_master
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_detach_public_ips
taskmanager.test_models.BuiltInstanceTasksTest.test_detach_public_ips
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_detach_replica
taskmanager.test_models.BuiltInstanceTasksTest.test_detach_replica
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'


==
FAIL: taskmanager.test_models.BuiltInstanceTasksTest.test_enable_as_master
taskmanager.test_models.BuiltInstanceTasksTest.test_enable_as_master
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-6.0.0/trove/tests/unittests/taskmanager/test_models.py",
 line 741, in setUp
spec=novaclient.v2.floating_ips.FloatingIPManager)
AttributeError: 'module' object has no attribute 'floating_ips'

Bug#881096: python-asyncssh FTBFS: test falures

[Adrian Bunk]

Source: python-asyncssh
Version: 1.11.0-1
Severity: serious

Some recent change in unstable makes python-asyncssh FTBFS:

https://tests.reproducible-builds.org/debian/history/python-asyncssh.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-asyncssh.html

...
==
ERROR: tearDownClass (tests.test_agent._TestAPI)
--
Traceback (most recent call last):
  File "/build/1st/python-asyncssh-1.11.0/tests/util.py", line 319, in 
tearDownClass
cls.loop.run_until_complete(cls.asyncTearDownClass())
  File "/usr/lib/python3.6/asyncio/base_events.py", line 467, in 
run_until_complete
return future.result()
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 210, in coro
res = func(*args, **kw)
  File "/build/1st/python-asyncssh-1.11.0/tests/test_agent.py", line 124, in 
asyncTearDownClass
os.kill(cls._agent_pid, signal.SIGTERM)
ProcessLookupError: [Errno 3] No such process

==
ERROR: test_keys (tests.test_public_key.TestDSA) [Import OpenSSH private 
(arcfour)] (alg_name='ssh-dss')
Check keys and certificates
--
Traceback (most recent call last):
  File "/build/1st/python-asyncssh-1.11.0/tests/test_public_key.py", line 1344, 
in check_openssh_private
self.import_openssh_private(use_openssh, cipher)
  File "/build/1st/python-asyncssh-1.11.0/tests/test_public_key.py", line 519, 
in import_openssh_private
cipher)
  File "/build/1st/python-asyncssh-1.11.0/tests/util.py", line 173, in run
stderr=subprocess.STDOUT)
  File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
**kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'ssh-keygen -p -a 128 -N passphrase -Z 
arcfour -o -f new' returned non-zero exit status 1.

==
ERROR: test_keys (tests.test_public_key.TestDSA) [Export OpenSSH private 
(arcfour)] (alg_name='ssh-dss')
Check keys and certificates
--
Traceback (most recent call last):
  File "/build/1st/python-asyncssh-1.11.0/tests/test_public_key.py", line 1347, 
in check_openssh_private
self.export_openssh_private(use_openssh, cipher)
  File "/build/1st/python-asyncssh-1.11.0/tests/test_public_key.py", line 538, 
in export_openssh_private
run('ssh-keygen -p -P passphrase -N "" -o -f new')
  File "/build/1st/python-asyncssh-1.11.0/tests/util.py", line 173, in run
stderr=subprocess.STDOUT)
  File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
**kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'ssh-keygen -p -P passphrase -N "" -o -f 
new' returned non-zero exit status 255.

==
ERROR: test_keys (tests.test_public_key.TestDSA) [Import OpenSSH private 
(arcfour128)] (alg_name='ssh-dss')
Check keys and certificates
--
Traceback (most recent call last):
  File "/build/1st/python-asyncssh-1.11.0/tests/test_public_key.py", line 1344, 
in check_openssh_private
self.import_openssh_private(use_openssh, cipher)
  File "/build/1st/python-asyncssh-1.11.0/tests/test_public_key.py", line 519, 
in import_openssh_private
cipher)
  File "/build/1st/python-asyncssh-1.11.0/tests/util.py", line 173, in run
stderr=subprocess.STDOUT)
  File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
**kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'ssh-keygen -p -a 128 -N passphrase -Z 
arcfour128 -o -f new' returned non-zero exit status 1.
...

Bug#879231: security update: ruby2.3

[Antonio Terceiro]

On Sat, Nov 04, 2017 at 10:45:06PM +, Adam D. Barratt wrote:
> On Sat, 2017-11-04 at 22:08 +0100, Salvatore Bonaccorso wrote:
> > Hi Antonio
> > 
> > Sorry for the late reply
> > 
> > On Mon, Oct 23, 2017 at 11:49:28AM -0200, Antonio Terceiro wrote:
> > > Hi security team,
> > > 
> > > I have prepared a security update for ruby2.3.
> > > 
> > > It includes all the pending recent CVE's, plus a fix for a bug that
> > > causes runaway child processes hogging the CPU, noticed at least in
> > > puppet.
> > 
> > For the later one, not directly a security issue, strictly speaking
> > we
> > would need an ack from the SRM to see they would ack it to a point
> > release and then we can pick it as well for a security update. The
> > patch though looks confined enough that I would trust it's okay as
> > well for SRM to see it included (Cc'ed explicity Adam).
> 
> Assuming that's "0005-thread_pthread.c-do-not-wakeup-inside-child-
> processe.patch", it looks okay to me.

Thanks.

> As I've previously mentioned to Salvatore in another discussion, the
> fact that the patch hasn't been applied in unstable, afaict, doesn't
> fit our usual requirements for accepting patches in stable. I
> understand there are reasons for that, and the upload going via the
> security archive does make things slightly easier from that
> perspective, but as thinks stand I imagine we'll end up pushing +deb9u2
> into unstable during the next point release, as we did with +deb9u1
> recently.

If I upload these changes to unstable myself (with a properly adjusted
version number), does that make it easier for you? I have not been doing
that because ruby2.3 won't be shipped in buster anyway, but I would
rather consume my time as maintainer than yours as stable release
manager.


signature.asc
Description: PGP signature

Bug#843926: jemalloc hard codes page size during build

[James Cowgill]

On 07/11/17 17:02, James Cowgill wrote:
> Hi,
> 
> Is there a plan to start a transition to get this version of jemalloc in
> unstable? I don't see a transition bug against release.d.o. Is there
> anything blocking it?

Ah nevermind - I see it FTBFS in experimental on lots of arches.

James



signature.asc
Description: OpenPGP digital signature

Bug#843926: jemalloc hard codes page size during build

[James Cowgill]

Hi,

Is there a plan to start a transition to get this version of jemalloc in
unstable? I don't see a transition bug against release.d.o. Is there
anything blocking it?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#881061: python-lz4 FTBFS on big endian: FAIL: test_get_frame_info (test_frame.TestLZ4Frame)

[James Cowgill]

Control: tags -1 patch

Hi,

On 07/11/17 14:39, Adrian Bunk wrote:
> Source: python-lz4
> Version: 0.10.1+dfsg1-0.1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=python-lz4=sid
> 
> ...
>dh_auto_test -a -O--parallel -O--buildsystem=pybuild
> I: pybuild base:184: cd 
> /<>/python-lz4-0.10.1+dfsg1/.pybuild/pythonX.Y_2.7/build; python2.7 
> -m nose tests
> ..F.
> ==
> FAIL: test_get_frame_info (test_frame.TestLZ4Frame)
> --
> Traceback (most recent call last):
>   File 
> "/<>/python-lz4-0.10.1+dfsg1/.pybuild/pythonX.Y_2.7/build/tests/test_frame.py",
>  line 200, in test_get_frame_info
> "contentSize":len(input_data)
> AssertionError: {'blockMode': 1, 'blockSizeID': 4, 'contentSize': 0, 
> 'frameType': 0, 'contentChe [truncated]... != {'blockMode': 1, 'blockSizeID': 
> 4, 'contentSize': 112, 'frameType': 0, 'contentC [truncated]...
>   {'blockMode': 1,
>'blockSizeID': 4,
>'contentChecksumFlag': 0,
> -  'contentSize': 0,
> ? ^
> 
> +  'contentSize': 112,
> ? ^^^
> 
>'frameType': 0}

The attached patch should fix this. contentSize is an "unsigned long
long", but was passing the "int" format to Py_BuildValue so it chopped
off the lower/upper (depending on endianness) part of the number.

James
--- a/lz4/frame/_frame.c
+++ b/lz4/frame/_frame.c
@@ -630,7 +630,7 @@ get_frame_info (PyObject * Py_UNUSED (se
   return NULL;
 }
 
-  return Py_BuildValue ("{s:i,s:i,s:i,s:i,s:i}",
+  return Py_BuildValue ("{s:i,s:i,s:i,s:i,s:K}",
 "blockSizeID", frame_info.blockSizeID,
 "blockMode", frame_info.blockMode,
 "contentChecksumFlag", frame_info.contentChecksumFlag,


signature.asc
Description: OpenPGP digital signature

Processed: Bug#881061: python-lz4 FTBFS on big endian: FAIL: test_get_frame_info (test_frame.TestLZ4Frame)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #881061 [src:python-lz4] python-lz4 FTBFS on big endian: FAIL: 
test_get_frame_info (test_frame.TestLZ4Frame)
Added tag(s) patch.

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

Bug#881093: marked as done (lvm depend on unneeded libraries)

[Debian Bug Tracking System]

Your message dated Tue, 7 Nov 2017 17:36:28 +0100
with message-id <20171107163627.33cxwdncuf4nd...@shell.thinkmo.de>
and subject line Re: Bug#881093: lvm depend on unneeded libraries
has caused the Debian Bug report #881093,
regarding lvm depend on unneeded libraries
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.)


-- 
881093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: lvm2
Version: 2.02.175-1
Severity: serious

Debian Policy says that no package should depend on libraries that they
don't need.

With 2.02.175-1 lvm2 start to depend on libsystemd. That dependency is
not needed. (And by the way break some systems and leave them
unbootable.)

- -- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloB3vYACgkQpnwKsYAZ
9qzOYgv/fvSbdmZvizJLbMAkwnVA16BlSTbnz6AiYThfI+wr2XHYSL2n5KJBT6uw
o+si46V+CsHDraAt/2Xxk+kz2laqKfVLdUtnAy5NkYH1eoAcSWB/s5bb/fvVPGKg
LWQ3oB+xWwMYO213OqpBhgtmMsiLuYpDVzk9t8SwndVxdfD4qhG6E9YeCtgJe6Gt
JWbIYXO0LvdWRydIFW/29WTPEhqjozKuwIigPpIkfamNESi+3/5Vp+ksGOpw0uIV
CAiUh6SsyOhwU94nH6s67ocqmDFh6OF/vkwGyY4qhVGtsqs34W6nP3J9NNi/10Hf
lnK5Gdzl41PEUC05+oGZlP+QzNdhVxz1FbID30pp8HHIMGEY9j80iekDJr+OYHi2
G0Fyu1VbQ+jdmM8OoleGyJPU9e1i3JJyAHENZsudgp4SU6So2+896/05F/azyq1F
aNaR+J8mby8w3gUIPPKrc8D/GqpDHm+IZau88+yxW+5BhiiZIt9LGXUpsZRPqw5A
NkAqoMbt
=wEKG
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On Tue, Nov 07, 2017 at 05:27:41PM +0100, Klaus Ethgen wrote:
> Debian Policy says that no package should depend on libraries that they
> don't need.
> With 2.02.175-1 lvm2 start to depend on libsystemd. That dependency is
> not needed. (And by the way break some systems and leave them
> unbootable.)

It needs this library to do notifications for lvm2dbusd.

Bastian

-- 
Emotions are alien to me.  I'm a scientist.
-- Spock, "This Side of Paradise", stardate 3417.3--- End Message ---

Bug#881093: lvm depend on unneeded libraries

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: lvm2
Version: 2.02.175-1
Severity: serious

Debian Policy says that no package should depend on libraries that they
don't need.

With 2.02.175-1 lvm2 start to depend on libsystemd. That dependency is
not needed. (And by the way break some systems and leave them
unbootable.)

- -- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloB3vYACgkQpnwKsYAZ
9qzOYgv/fvSbdmZvizJLbMAkwnVA16BlSTbnz6AiYThfI+wr2XHYSL2n5KJBT6uw
o+si46V+CsHDraAt/2Xxk+kz2laqKfVLdUtnAy5NkYH1eoAcSWB/s5bb/fvVPGKg
LWQ3oB+xWwMYO213OqpBhgtmMsiLuYpDVzk9t8SwndVxdfD4qhG6E9YeCtgJe6Gt
JWbIYXO0LvdWRydIFW/29WTPEhqjozKuwIigPpIkfamNESi+3/5Vp+ksGOpw0uIV
CAiUh6SsyOhwU94nH6s67ocqmDFh6OF/vkwGyY4qhVGtsqs34W6nP3J9NNi/10Hf
lnK5Gdzl41PEUC05+oGZlP+QzNdhVxz1FbID30pp8HHIMGEY9j80iekDJr+OYHi2
G0Fyu1VbQ+jdmM8OoleGyJPU9e1i3JJyAHENZsudgp4SU6So2+896/05F/azyq1F
aNaR+J8mby8w3gUIPPKrc8D/GqpDHm+IZau88+yxW+5BhiiZIt9LGXUpsZRPqw5A
NkAqoMbt
=wEKG
-END PGP SIGNATURE-

Bug#880960: marked as done (python3-stem picks up a dependency on a versioned python3.x package)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 16:19:35 +
with message-id 
and subject line Bug#880960: fixed in python-stem 1.6.0-1
has caused the Debian Bug report #880960,
regarding python3-stem picks up a dependency on a versioned python3.x package
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.)


-- 
880960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-stem
Version: 1.5.3-1
Severity: serious
Tags: sid buster

python3-stem picks up a dependency on a versioned python3.x package, using a
hand-coded packaging.  It looks like this can be fixed by using pybuild and
dh-python.

python3.5 is going to be removed in buster.
--- End Message ---
--- Begin Message ---
Source: python-stem
Source-Version: 1.6.0-1

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

Debian distribution maintenance software
pp.
Ulises Vitulli  (supplier of updated python-stem 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,  7 Nov 2017 12:54:12 -03
Source: python-stem
Binary: python-stem python3-stem
Architecture: all source
Version: 1.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli 
Changed-By: Ulises Vitulli 
Description: 
 python-stem - Tor control library for Python
 python3-stem - Tor control library for Python 3 series
Closes: 880960
Changes:
 python-stem (1.6.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fix versioned py3.x dependency, thanks MatthiasKlose! (Closes: #880960).
   * Updated Standard-version to 4.1.1.1 (no changes needed).
   * Updated upstream changelog note on large file.
   * Update Vcs-Browser field to https one.
Checksums-Sha256: 
 3f6492690db795fbd01dfccb00e8062ca4b777fa64e3d5149d916601e8757a87 256828 
python-stem_1.6.0-1_all.deb
 f64f20922b1006670f5d27d2e5e2516b5fe7281eef17d5615bd4c3f19abe1790 256988 
python3-stem_1.6.0-1_all.deb
 d7fe1fb13ed5a94d610b5ad77e9f1b3404db0ca0586ded7a34afd323e3b849ed 204 
python-stem_1.6.0.orig.tar.gz
 838bdf84b971a76384223280652969f3f78c034f2015f61dc8f1e30b2072de72 1989 
python-stem_1.6.0-1.dsc
 32e6ce93d47c562b40edd4403ad5fe01edac1a5b058e3a576ee9af5c9f6467d6 3916 
python-stem_1.6.0-1.debian.tar.xz
Checksums-Sha1: 
 05fcfa4bffce9345ad9e91403417eb14797707cc 256828 python-stem_1.6.0-1_all.deb
 681508dcb80ba29b61938f19c79bd407e8dec51b 256988 python3-stem_1.6.0-1_all.deb
 1590ee340a3b321d8e51cfd6e9fb2c6637b93fee 204 python-stem_1.6.0.orig.tar.gz
 500aa0efb12cd325e75218aa0795c32d960486dc 1989 python-stem_1.6.0-1.dsc
 a4b4089cf36d7d6f284addb14eb0a59e7b2a3b40 3916 python-stem_1.6.0-1.debian.tar.xz
Files: 
 802bbfb1fbe03705c00e640bb368c08a 256828 python optional 
python-stem_1.6.0-1_all.deb
 c1c415c71b8a9bec00f00d7c6c0b8b95 256988 python optional 
python3-stem_1.6.0-1_all.deb
 fbf900e5c53441f7297b55154e3f34ea 204 - - python-stem_1.6.0.orig.tar.gz
 7e516b89ba535686249544666b221ccb 1989 python optional python-stem_1.6.0-1.dsc
 07b698921250ec04ac8189b0898eed6f 3916 - - python-stem_1.6.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvQqKQ/VtTywBCMYlg8MHkAqShqAFAloB10gACgkQg8MHkAqS
hqAbgA/+Pdsk3Pyqdp0E6AqBxaoCpvplVsYXaYTj5FjCXdOKTsS/+D4AkCmDn/qj
33qu2C3ks6JjEUqrpXHr9XyXzNE4bMS3q3GnTlzO3pfsZ3QQ9hV45omdPvGUHcIC
3JuH7iZqLBnFHK42p4ZjNA7nsLjyfEZElOsS2v9HjcaeAqlDJb0AHrpRoLCAbTcI
ys406DTbs+lFEt9FbKfrZUjIE1qMQd7I57NUG/ywEQ0tCEuWN8fsYHQBa+eRL2dQ
avu/ZTAl3izoGcT8qqgqw6/J4OZMF+AfQFnIUY6TbAeje/d09cp1ozGW8E+Gx9LD
2BEJFT5GdmfhizF/AtYfdh1OBgKYvH1ieYZlezCHqTZKVza20MtdpG2sF0p/UKF4
iEEVrA4RoDYYKjsr6bqDh1NIJSTYnzFRJWwzDkP7xhHJJ9yRitjLWVdd2Ql3fJV8
VfLzSOZQ0DS/mIUIZNeI8gP+/hHUsSKj7+AWS8UyAb+8QFjt7C1aYjgM4usLH/Mj
lbMGideZOuGJ1t7Cm0RS3SaEHH3kUWmliZLlnXjwyXZOO5gbqQEq1gEUQm2m00ka
MkTn6vsV2z1XeKFX3f3e4og93dCnKFv7Ns3rbxmGYoW5gUJFpn3Z+uf4UmlCtP3X
5TzJY1JNo1HkjLGtwHGgFm5zJhUM8s2qmF4fj8N06AGKn5RZCGk=
=smVq
-END PGP SIGNATURE End Message ---

Bug#881092: brewtarget FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: brewtarget
Version: 2.3.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/brewtarget.html

...
CMake Error at CMakeLists.txt:151 (FIND_PACKAGE):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881091: converseen FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: converseen
Version: 0.9.6.2-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/converseen.html

...
CMake Error at CMakeLists.txt:94 (FIND_PACKAGE):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881090: italc FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: italc
Version: 1:3.0.3+dfsg1-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/italc.html

...
CMake Error at CMakeLists.txt:129 (FIND_PACKAGE):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 881064 buster sid
Bug #881064 [src:drf-fsm-transitions] drf-fsm-transitions: B-D on obsolete 
transitional package python3-appconf
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#881057: marked as done (System does not boot due to dependency to /usr)

[Debian Bug Tracking System]

Your message dated Tue, 7 Nov 2017 16:41:43 +0100
with message-id <20171107154143.wgpxfbnmounxx...@shell.thinkmo.de>
and subject line Re: Bug#881057: System does not boot due to dependency to /usr
has caused the Debian Bug report #881057,
regarding System does not boot due to dependency to /usr
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.)


-- 
881057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: lvm2
Version: 2.02.176-1
Severity: critical

lvm2 starting with 2.02.175-1 depends on library in /usr. With that, it
is not possible to boot the system anymore when /usr is on a LVM.
(initrd-less setup)

The last working version is 2.02.173-1.

- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (400, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.12 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE=de_DE:en 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lvm2 depends on:
ii  dmeventd  2:1.02.145-1
ii  dmsetup   2:1.02.145-1
ii  init-system-helpers   1.51
ii  libblkid1 2.30.2-0.1
ii  libc6 2.24-17
ii  libdevmapper-event1.02.1  2:1.02.145-1
ii  libdevmapper1.02.12:1.02.145-1
ii  liblvm2app2.2 2.02.173-1
ii  libreadline5  5.2+dfsg-3+b1
pn  libudev1  
ii  lsb-base  9.20170808

lvm2 recommends no packages.

Versions of packages lvm2 suggests:
pn  thin-provisioning-tools  

- -- Configuration Files:
/etc/lvm/lvm.conf changed:
config {
# Configuration option config/checks.
# If enabled, any LVM configuration mismatch is reported.
# This implies checking that the configuration key is understood by
# LVM and that the value of the key is the proper type. If disabled,
# any configuration mismatch is ignored and the default value is used
# without any warning (a message about the configuration key not being
# found is issued in verbose mode only).
checks = 1
# Configuration option config/abort_on_errors.
# Abort the LVM process if a configuration mismatch is found.
abort_on_errors = 0
# Configuration option config/profile_dir.
# Directory where LVM looks for configuration profiles.
profile_dir = "/etc/lvm/profile"
}
devices {
# Configuration option devices/dir.
# Directory in which to create volume group device nodes.
# Commands also accept this as a prefix on volume group names.
# This configuration option is advanced.
dir = "/dev"
# Configuration option devices/scan.
# Directories containing device nodes to use with LVM.
# This configuration option is advanced.
scan = [ "/dev" ]
# Configuration option devices/obtain_device_list_from_udev.
# Obtain the list of available devices from udev.
# This avoids opening or using any inapplicable non-block devices or
# subdirectories found in the udev directory. Any device node or
# symlink not managed by udev in the udev directory is ignored. This
# setting applies only to the udev-managed device directory; other
# directories will be scanned fully. LVM needs to be compiled with
# udev support for this setting to apply.
obtain_device_list_from_udev = 1
# Configuration option devices/external_device_info_source.
# Select an external device information source.
# Some information may already be available in the system and LVM can
# use this information to determine the exact type or use of devices it
# processes. Using an existing external device information source can
# speed up device processing as LVM does not need to run its own native
# routines to acquire this information. For example, this information
# is used to drive LVM filtering like MD component detection, multipath
# component detection, partition detection and others.
# 
# Accepted values:
#   none
# No external device information source is used.
#   udev
# Reuse existing udev database records. Applicable only if LVM is
# compiled 

Bug#880768: marked as done (embassy-domalign build depends on removed libgd2*-dev provides)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 15:49:44 +
with message-id 
and subject line Bug#880768: fixed in embassy-domalign 0.1.660-2
has caused the Debian Bug report #880768,
regarding embassy-domalign build depends on removed libgd2*-dev provides
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.)


-- 
880768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: embassy-domalign
Version: 0.1.660-1
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:embassy-domalign : Depends: libgd2-xpm-dev but it is not installable


Please change the build dependency to libgd-dev.
--- End Message ---
--- Begin Message ---
Source: embassy-domalign
Source-Version: 0.1.660-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated embassy-domalign package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 15:24:46 +0100
Source: embassy-domalign
Binary: embassy-domalign
Architecture: source
Version: 0.1.660-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 embassy-domalign - Extra EMBOSS commands for protein domain alignment
Closes: 880768
Changes:
 embassy-domalign (0.1.660-2) unstable; urgency=medium
 .
   * Moved packaging from SVN to Git
   * Standards-Version: 4.1.1
   * Fix Build-Depends: libgd2-xpm-dev -> libgd-dev
 Closes: #880768
   * Lintian-override to accept RPATH definition
Checksums-Sha1:
 f1d9bd86e80402cbc2e5dd7ddb3ea6f0fbf97689 2233 embassy-domalign_0.1.660-2.dsc
 2e4631e8d6117e59a57cb0b0c51bedbf9cf1fad3 6308 
embassy-domalign_0.1.660-2.debian.tar.xz
 97e5382fbb56d454cf7f7588a14176866cb54f5b 7870 
embassy-domalign_0.1.660-2_amd64.buildinfo
Checksums-Sha256:
 3ed590e4ce3d0a531c5df9dbffa46aca267b152730bb547bb7f9e0ea2f852456 2233 
embassy-domalign_0.1.660-2.dsc
 632a7d3a39137570cea9566263ef6f96a6060f40e384c45fadafad4beeb5a7f6 6308 
embassy-domalign_0.1.660-2.debian.tar.xz
 378448c9cadb7c49905cd860ee2da5658eee69f432837fd67def1546a3f65266 7870 
embassy-domalign_0.1.660-2_amd64.buildinfo
Files:
 c64eb61ad7ade70a7d3c6777149e19e1 2233 science optional 
embassy-domalign_0.1.660-2.dsc
 9f7460ee54ad44b1c68c8c0bdd34d36b 6308 science optional 
embassy-domalign_0.1.660-2.debian.tar.xz
 e715fce210ec5306cb255ec5c0d4eb14 7870 science optional 
embassy-domalign_0.1.660-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAloB78gRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEWOg/9Hqj9edxJRsaX+z9rtY3jS3psiWiT9jQU
R7a4nluAlNQgf8QBqFMqTq8wgPY194f/T9joMj+YLfDoVDaPF1KZ54GTf7FbEpmo
gLIt2GeTcRyuyEiQCA4UtxH89j9jbfGTQCP19wiKzSFE0N8LFXmuLvlRy0MUyNlk
RBbnNABTS/QjKHNVVRGKqlHB2CapBbFp0TjTKfrv51WVtf4JMlWetnGednUC1zHn
PaURvT77pSLCbc/OwUSHQJr8Wj4QgDqSWJQ5uybKTCjOVSXl0ecRu3LuVPvzzJvH
yYtmBfuZduc+dAOde65YyXqcERz6BZN9zni+MibitzX5532Ppy7Xl4/JAaucaXme
bT4nYqF1CrBkQT6gcX1cOous53ml9S+U/38xQ98pbEi81wMjuGzVSuvKK2VHTe6e
lE7BFC70rFVVCcHlyYMVLUDYakjPnwFs6tz1r1ZgQGBFXAdn8cd33wBPoiXnK6un
3kZGWfHDfzb5rXyGhrxIkbClzcDP6KFbN3hDW8M5Xs2UZc0sRMOlx3ww+5Px6Ywj
2IOkY+oshiPdgcXFZ1bAKKWp3ya5JPWqyYJQ9IVfiUhiEUbOMmOxMnYiYGwVTsMk
xwXazUhvs9/eHa8nOioNdoOHYE0a89400Aw3mBIZljxtnMHJBn28X1Wq2TrDKgfv
UDw63pCO5qY=
=Ix/w
-END PGP SIGNATURE End Message ---

Bug#881086: qastools FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: qastools
Version: 0.21.0-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qastools.html

...
CMake Warning at i18n/CMakeLists.txt:5 (FIND_PACKAGE):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#880354: marked as done (embassy-phylip: switch B-D from libgd2-xpm-dev to libgd-dev)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 15:34:28 +
with message-id 
and subject line Bug#880354: fixed in embassy-phylip 3.69.660-2
has caused the Debian Bug report #880354,
regarding embassy-phylip: switch B-D from libgd2-xpm-dev to libgd-dev
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.)


-- 
880354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: embassy-phylip
Version: 3.69.660-1
Severity: serious
Tags: buster sid
Justification: fails to build from source

Hi,

the transitional libgd2*-dev packages are finally gone, please switch
the Build-Depends to libgd-dev.


Andreas
--- End Message ---
--- Begin Message ---
Source: embassy-phylip
Source-Version: 3.69.660-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated embassy-phylip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 15:58:51 +0100
Source: embassy-phylip
Binary: embassy-phylip
Architecture: source amd64
Version: 3.69.660-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 embassy-phylip - EMBOSS conversions of the programs in the phylip package
Closes: 880354
Changes:
 embassy-phylip (3.69.660-2) unstable; urgency=medium
 .
   * Moved packaging from SVN to Git
   * debhelper 10
   * Standards-Version: 4.1.1
   * Fix Build-Depends: libgd2-xpm-dev -> libgd-dev
 Closes: #880354
Checksums-Sha1:
 601a1998fc75ae5a4598cb5f4d6136e436968dd7 2250 embassy-phylip_3.69.660-2.dsc
 b08ffbca1a5de48c113d5b9ba4618d40e03468b5 10864 
embassy-phylip_3.69.660-2.debian.tar.xz
 504de3767d9738ed10f91ed5faf4f0916de3ccaf 3937604 
embassy-phylip-dbgsym_3.69.660-2_amd64.deb
 db12d49eb84b9570294e2d3e1088b13d5267a19a 8099 
embassy-phylip_3.69.660-2_amd64.buildinfo
 a09657fa86e6dcc199819fbc5d7bcf0b0b78a91d 838424 
embassy-phylip_3.69.660-2_amd64.deb
Checksums-Sha256:
 ee7aedb8514195cbd868ba70436229e5529a1f46344f22dc0d9ee4eec0395b00 2250 
embassy-phylip_3.69.660-2.dsc
 c41595c51ec231d8ad0155009ed2300eea8f37de616d1e50570fa992ebe5dd60 10864 
embassy-phylip_3.69.660-2.debian.tar.xz
 0605e143a8309b6c8c2f9483f21acab21a7c2a6ba585966cf75b14a1125d4a36 3937604 
embassy-phylip-dbgsym_3.69.660-2_amd64.deb
 59ac955324e291b7d0cb2aa7ba528f951182b407edcc282b2644cad4bfdd5494 8099 
embassy-phylip_3.69.660-2_amd64.buildinfo
 4931e857450838e6c239c8b658bc52eb3effaef691cfda3a6c2e34c26caad87f 838424 
embassy-phylip_3.69.660-2_amd64.deb
Files:
 df5ed8ce508d8da58c1f1ddff7dfb34d 2250 non-free/science optional 
embassy-phylip_3.69.660-2.dsc
 78f59e6483b9756809cc1314c61521de 10864 non-free/science optional 
embassy-phylip_3.69.660-2.debian.tar.xz
 42d869733397eae5a9dd077e7650811c 3937604 non-free/debug optional 
embassy-phylip-dbgsym_3.69.660-2_amd64.deb
 30dc51af07726c46877d0616c3b884df 8099 non-free/science optional 
embassy-phylip_3.69.660-2_amd64.buildinfo
 47e5d61f0258581df9c755d914d83d04 838424 non-free/science optional 
embassy-phylip_3.69.660-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAloB5rkRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEtwRAAmPy55hWEZTQUHFUKpWvEYYYtkO5Nzm18
go5/nfxff948eAKBJhri0/u2OAf5bWEErUXawe4WuDAgy9BlpRPScRg3ov0ZgJM2
yYi0+HkrcDE4kvq3+aCXq41YcJ/cVDzl7DVah6yslUzTjyc+3BCQf86U/R4Fgt+T
LTmIssdPST1qSleG0JjrDAwkPIbxs91xt3yU/IDyabhZPhrpdoPsMnTeyjrsQIgD
90Odq9j/oej+LgMT1RhwdT36xB9OK58wcWFir/TnNK1eJ36zM9myBYp/HMF2NTuL
gd+Q9763rrrw1aDRNgNx8rZ3cPlQfVB+Z+v8zYVPe8ixTbq3zT8S6uugPlEQmTQP
8zjtNrJB2NJGlMbcvmiWHsZ7y/n4ptM7e/Zbhhc0Tyxxwxw+RoYQ5jX64911lfDV
jffk6nCzwgSk7z/Xl6FL1VdtwfXWk7PhPOsoQ2++5xu54NWePn1u2w+xXFnYeXBI
FSAfBk/j0jDzGeEgtn+NWpAsqb6ldJIiSMrlrj5As6Dwkj8sZnPXPO0JJom7UOmX
xivypO/ZPIVqShQt8ULPyrmqPeaHrfriGYcMnqMgokuDCSSByx0ryG3fCgq0tEkP

Bug#881087: nlkt FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: nlkt
Version: 0.3.2.6-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nlkt.html

...
CMake Warning at share/CMakeLists.txt:1 (find_package):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881082: nitroshare FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: nitroshare
Version: 0.3.3-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nitroshare.html

...
CMake Error at CMakeLists.txt:22 (find_package):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  (requested version 5.1) with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881083: rosegarden FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: rosegarden
Version: 1:17.04-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rosegarden.html

...
-- Not building unit tests, using a static library for rosegarden
CMake Error at src/CMakeLists.txt:742 (find_package):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  (requested version 5.1.0) with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.



qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881084: qmmp FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: qmmp
Version: 1.1.10-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qmmp.html

...
CMake Error at CMakeLists.txt:47 (find_package):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  (requested version 5.4.0) with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881085: q4wine FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: q4wine
Version: 1.3.6-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/q4wine.html

...
CMake Error at src/CMakeLists.txt:39 (find_package):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.



qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881080: kirigami FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: kirigami
Version: 1.1.0-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kirigami.html

...
CMake Error at /usr/share/ECM/modules/ECMPoQmTools.cmake:144 (find_package):
  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881081: ksyntax-highlighting FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: ksyntax-highlighting
Version: 5.37.0-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ksyntax-highlighting.html

...
CMake Error at /usr/share/ECM/modules/ECMPoQmTools.cmake:144 (find_package):
  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 881079 buster sid
Bug #881079 [src:kdiagram] kdiagram FTBFS: Qt5LinguistTools*.cmake moved to 
qttools5-dev
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#881078: kdb FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: kdb
Version: 3.0.2-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kdb.html

...
CMake Error at /usr/share/ECM/modules/ECMPoQmTools.cmake:144 (find_package):
  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881079: kdiagram FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: kdiagram
Version: 2.6.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kdiagram.html

...
CMake Error at /usr/share/ECM/modules/ECMPoQmTools.cmake:144 (find_package):
  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881076: kirigami2 FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: kirigami2
Version: 5.37.0-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kirigami2.html

...
CMake Error at /usr/share/ECM/modules/ECMPoQmTools.cmake:144 (find_package):
  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#881074: qcomicbook FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev

[Adrian Bunk]

Source: qcomicbook
Version: 0.9.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qcomicbook.html

...
CMake Error at CMakeLists.txt:23 (FIND_PACKAGE):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.



qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...

Bug#880788: marked as done (w3c-markup-validator build depends on removed transitional package lynx-cur)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 15:12:44 +
with message-id 
and subject line Bug#880788: fixed in w3c-markup-validator 1.3+dfsg-4
has caused the Debian Bug report #880788,
regarding w3c-markup-validator build depends on removed transitional package 
lynx-cur
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.)


-- 
880788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: w3c-markup-validator
Version: 1.3+dfsg-3
Severity: serious
Tags: buster sid 

The following packages have unmet dependencies:
 builddeps:w3c-markup-validator : Depends: lynx-cur but it is not installable


Please update the build dependency to lynx.
--- End Message ---
--- Begin Message ---
Source: w3c-markup-validator
Source-Version: 1.3+dfsg-4

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated w3c-markup-validator 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 14:41:21 +0100
Source: w3c-markup-validator
Binary: w3c-markup-validator
Architecture: source
Version: 1.3+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 w3c-markup-validator - W3C Markup Validator
Closes: 880788
Changes:
 w3c-markup-validator (1.3+dfsg-4) unstable; urgency=medium
 .
   * QA upload.
   * Switch Build-Depends back to lynx.  (Closes: #880788)
   * Use https:// URLs where possible.
Checksums-Sha1:
 563722ba9e22d4d5c641099ca07ecd9a835b6686 2163 
w3c-markup-validator_1.3+dfsg-4.dsc
 223f4e43fd64050cf333f87253ab5e067a720c9a 24112 
w3c-markup-validator_1.3+dfsg-4.debian.tar.xz
 155fcbb92fab4eb2aebb1aae36494bd11e1f154f 5263 
w3c-markup-validator_1.3+dfsg-4_source.buildinfo
Checksums-Sha256:
 34a72775db0602fbd317393470dfe4991e5036420a31775070aa64ec9ed8457b 2163 
w3c-markup-validator_1.3+dfsg-4.dsc
 80418e442a09a3f101f77e9d1aa73eaf22ef39e6dfa43168894593bbcd474a19 24112 
w3c-markup-validator_1.3+dfsg-4.debian.tar.xz
 74bab313de8f3c5c6cc089c22e4b7f40ade1fb04f1dc862fdd85cd55c50eaa1b 5263 
w3c-markup-validator_1.3+dfsg-4_source.buildinfo
Files:
 dc629ce4dcbdc0a2d6d9286a3747b51b 2163 web optional 
w3c-markup-validator_1.3+dfsg-4.dsc
 1425b8d45eafb7bca7a41cf6d3ca0551 24112 web optional 
w3c-markup-validator_1.3+dfsg-4.debian.tar.xz
 1bd44dc45218b055d2249013a9c62e2c 5263 web optional 
w3c-markup-validator_1.3+dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAloBuXUQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCDd1D/0Swy3M8yuBK9dPEG5CrF44qB7l+JTq3rss
OVN1bubauA9EkU62l1SCZ93YtAjrn7na+Vf7+cvua9fAbNUiWqXLL4/J3MTHhN06
3FsLgCOkZSKlzjw+BdzOw4P6Uu0hE5lOWCtWazAmFFO38IZfCC/GHVG0pYxZYhSG
cAYCFpMTKdm9XeMq+J4oMmmsvr3XhJFA0UVSi1m5pbRTlmkvu6dijNLT7mGXHLvn
mDCnX7bZ7+EjQe/SxOeVV7FDLPI9PT1d0rroKBJq7brxQJMC/jdCIJFphdK95W64
unTc2POLCKKgjE94f4/fZjFhr1syzdTnNk5Ro3KQ0ekQSAkarsoilycirujBAXmb
AorkOY7ZbnExpdH0m3UgFZUMPKL/TIgzvWzfjTN2wO6NhVgfInNAWJZwQb8szumM
cero3t/nj88RKtX8bRN8QgE35Y7AC0iJfu+091NOCjY2aFEL71E9SzDYeQI634EY
ozL8XZTL9sQzyWX11zFtZtl+KBnFYL7H4W0bOHHEF2R/joMFosVNdO9fsN/WDJ5e
BERsFjb5Bmz38reECuYIL7eSWCWADXRgUgSL+jWxK/reJvbzpDSf9P2MZAdv/3vt
OG1bbguMV0AALYQ3rxrBm4Me626zlIU0/nCiDduM5SbE04+uqJ8w7Av56c8yEKqs
77nIy/JLDg==
=4vgo
-END PGP SIGNATURE End Message ---

Bug#877250: marked as done (conffile /etc/default/kdump-tools changed by maintainer scripts)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 15:09:31 +
with message-id 
and subject line Bug#877250: fixed in makedumpfile 1:1.6.2-1
has caused the Debian Bug report #877250,
regarding conffile /etc/default/kdump-tools changed by maintainer scripts
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.)


-- 
877250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdump-tools
Version: 1:1.6.2-0.1
Severity: serious

Per Debian Policy, a conffile must not be modified by a maintainer
script. We should make /etc/default/kdump-tools not be a conffile
anymore, and create it during the installation.

We will probably need to do something with dpkg-maintscript-helper in
some upgrade/removal cases, have a template/base file in
/usr/share/kdump-tools/ that we use.

As an additional requirement, as kdump-tools is usually tested by
crashing the system after it's installed, the maintainer scripts should
sync/fsync the files it touches.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages kdump-tools depends on:
ii  bsdmainutils 9.0.12+nmu1
ii  debconf  1.5.63
ii  file 1:5.32-1
ii  init-system-helpers  1.49
ii  kexec-tools  1:2.0.15-1
ii  lsb-base 9.20170808
ii  makedumpfile 1:1.6.2-0.1

kdump-tools recommends no packages.

kdump-tools suggests no packages.

-- debconf information:
* kdump-tools/use_kdump: true
--- End Message ---
--- Begin Message ---
Source: makedumpfile
Source-Version: 1:1.6.2-1

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

Debian distribution maintenance software
pp.
Louis Bouchard  (supplier of updated makedumpfile 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: Wed, 01 Nov 2017 14:50:26 +0100
Source: makedumpfile
Binary: makedumpfile kdump-tools
Architecture: source
Version: 1:1.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Louis Bouchard 
Changed-By: Louis Bouchard 
Description:
 kdump-tools - scripts and tools for automating kdump (Linux crash dumps)
 makedumpfile - VMcore extraction tool
Closes: 877250
Changes:
 makedumpfile (1:1.6.2-1) unstable; urgency=medium
 .
   [ Thadeu Lima de Souza Cascardo ]
   * Add ucf support
 .
 /etc/default/kdump-tools was already changed by the maintainer script,
 so it should not be a conffile. ucf allows the maintainer scripts to ask
 the user about changes done by the user to the config file.
 .
 Invoking debconf first in the script is desired, because the frontend
 might exec and invoke the script itself again. Also, we install the
 generated file instead of the original file, as we will replace some of
 the settings.  (Closes: 877250)
Checksums-Sha1:
 72afb540131a620a44ad21f0e5ac1c38b7ed234e 2218 makedumpfile_1.6.2-1.dsc
 c08493f9cc6b775f901c9a20229c5a83f9c0b938 32352 
makedumpfile_1.6.2-1.debian.tar.xz
Checksums-Sha256:
 fdbe0d62c96746cb95b333cf6eafb8a6fde621a222eedffe01518dbe9e3aedd7 2218 
makedumpfile_1.6.2-1.dsc
 261ca282deb5945d015cc8fa87e3daef7e24cb094cc49fa0da73c1587754628b 32352 
makedumpfile_1.6.2-1.debian.tar.xz
Files:
 5b4228175605798b50cf6f7588f422ea 2218 devel optional makedumpfile_1.6.2-1.dsc
 446de127a64712c2c08afbba6d4024d0 32352 devel optional 
makedumpfile_1.6.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE34E7Im3TmixTD299CrplA3L9lXEFAloBt5gUHGNhc2NhcmRv
QGRlYmlhbi5vcmcACgkQCrplA3L9lXGM4BAAobDBJBhmLQRkws8cwCqR0X5yhvY+

Bug#880769: marked as done (embassy-domsearch build depends on removed libgd2*-dev provides)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 15:07:48 +
with message-id 
and subject line Bug#880769: fixed in embassy-domsearch 1:0.1.660-2
has caused the Debian Bug report #880769,
regarding embassy-domsearch build depends on removed libgd2*-dev provides
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.)


-- 
880769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: embassy-domsearch
Version: 1:0.1.660-1
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:embassy-domsearch : Depends: libgd2-xpm-dev but it is not installable


Please change the build dependency to libgd-dev.
--- End Message ---
--- Begin Message ---
Source: embassy-domsearch
Source-Version: 1:0.1.660-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated embassy-domsearch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 15:46:08 +0100
Source: embassy-domsearch
Binary: embassy-domsearch
Architecture: source
Version: 1:0.1.660-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 embassy-domsearch - Extra EMBOSS commands to search for protein domains
Closes: 880769
Changes:
 embassy-domsearch (1:0.1.660-2) unstable; urgency=medium
 .
   * Moved packaging from SVN to Git
   * Standards-Version: 4.1.1
   * Fix Build-Depends: libgd2-xpm-dev -> libgd-dev
 Closes: #880769
Checksums-Sha1:
 8d7faca04bee86c87646e7292c5033b0a9a5d650 2247 embassy-domsearch_0.1.660-2.dsc
 c9c8e4890093d33ba6d38e48023c87769f4eff5b 6808 
embassy-domsearch_0.1.660-2.debian.tar.xz
 de6cf8743e15abf9742c7d79567e3e7bad5f836c 7884 
embassy-domsearch_0.1.660-2_amd64.buildinfo
Checksums-Sha256:
 eb088f94148d01ca760f09f864bd3f26a1c0444144e127ccbab37718dc670f8c 2247 
embassy-domsearch_0.1.660-2.dsc
 a6388cffcf15d1e54a367661b969f5f6d76622b362844f146ba23944cc3a1d25 6808 
embassy-domsearch_0.1.660-2.debian.tar.xz
 7360c8ebbdafea28b13509596c7867d0e86dc646739b47ff79f420efa4150290 7884 
embassy-domsearch_0.1.660-2_amd64.buildinfo
Files:
 c5444f27d50e615bdab6c2c32116a3af 2247 science optional 
embassy-domsearch_0.1.660-2.dsc
 5f373e818f79d5eb276638c8cbaedda1 6808 science optional 
embassy-domsearch_0.1.660-2.debian.tar.xz
 ca0185a57ab0c0a37511036a00e73a89 7884 science optional 
embassy-domsearch_0.1.660-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAloB5DMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGePQ//ZKF0mC0gO5usiG1o1JQrz8CMoI58mch8
sT+7yrdZW+h/jTjAvbbIfRF5qL/cYMvGt2G/V6VtoNhFXUOOUUoQuRZmRlaaH+s/
++mr+UGbVAZ90X0Uk4tPtbs2RZm36mCMiAi/p0zq6KLGLxwcXmyuDoBkCK75Mfyn
dCJtPQA9BDDN2mv6wBnIIKyCjhjuLzjBa4OtV2SwmQrm2eop8maY/2Yc3LGxLbXN
xdBqDx2Lw+CHLDc5IQFSOKL+et4voNoJkZH4Ui9wIoCP6zL/K7ONy//rrPMwoHod
M1GOENF4yd4AvjNMf+e6uIOGRuq+3Yq9jX2Bf1hjPKElXukqwMUoJKqSWqZ3gjDt
Qz/MCiuzQAS5KFGvdACSIIVKo4DDqqZsenp/8b2XEJOpe2MPa/V+IRETNXPl8zBb
ZoiRMPMdOqklONvbugydyBYLWMfIDb7p6CLzsDLFiA1C6+K8kdZ29wnkMI09yJFT
XNWgLyPUZRH2B3nE4iituEFtLlQOaEz7cJ3cSTCCqseWp4yz6iD7YecbJdF+Z35R
zWaHUkTrI0dP7gTiIC/m7H3lSuTcQnzpOKfJW+LavLhcAQubvcGV3XaL5pm7OPAm
Uoc7yK3i0hZTwmEj98JayFT+aS1WXtDGB1t1nBIykmk7z+09AwwdsHOrBb6Jjton
ztdtefz41v4=
=1Xrp
-END PGP SIGNATURE End Message ---

Bug#880767: marked as done (embassy-domainatrix build depends on removed libgd2*-dev provides)

[Debian Bug Tracking System]

Your message dated Tue, 07 Nov 2017 15:07:36 +
with message-id 
and subject line Bug#880767: fixed in embassy-domainatrix 0.1.660-2
has caused the Debian Bug report #880767,
regarding embassy-domainatrix build depends on removed libgd2*-dev provides
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.)


-- 
880767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: embassy-domainatrix
Version: 0.1.660-1
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:embassy-domainatrix : Depends: libgd2-xpm-dev but it is not 
installable


Please change the build dependency to libgd-dev.
--- End Message ---
--- Begin Message ---
Source: embassy-domainatrix
Source-Version: 0.1.660-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated embassy-domainatrix 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 07 Nov 2017 15:05:05 +0100
Source: embassy-domainatrix
Binary: embassy-domainatrix
Architecture: source amd64
Version: 0.1.660-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 embassy-domainatrix - Extra EMBOSS commands to handle domain classification 
file
Closes: 880767
Changes:
 embassy-domainatrix (0.1.660-2) unstable; urgency=medium
 .
   * Moved packaging from SVN to Git
   * Standards-Version: 4.1.1
   * Fix Build-Depends: libgd2-xpm-dev -> libgd-dev
 Closes: #880767
Checksums-Sha1:
 27269242b9539b7943f0a3cfb75ad8c4fadc877e 2269 embassy-domainatrix_0.1.660-2.dsc
 77ede992831388f4528dc14bd0d9f2df6b5eb4af 8252 
embassy-domainatrix_0.1.660-2.debian.tar.xz
 fe0c4800c7f169dca5cf0c6b5db0bab949bde8e4 66644 
embassy-domainatrix-dbgsym_0.1.660-2_amd64.deb
 9ffa2cc3aa8224471acfb3f08fae63ee10429e80 7906 
embassy-domainatrix_0.1.660-2_amd64.buildinfo
 dca1c67b06e1d1f6cea073c0e830aeb8571d9202 62808 
embassy-domainatrix_0.1.660-2_amd64.deb
Checksums-Sha256:
 a0281ed5bd96283f46bb16800f685d68942f86a70c1d5d1fa93ea568f3ff20bf 2269 
embassy-domainatrix_0.1.660-2.dsc
 daae2f25585bfd4bb6f29f1cda827ce6897c004b912270207837588fef322524 8252 
embassy-domainatrix_0.1.660-2.debian.tar.xz
 a25c1d4e9ba1209003c6c0a03cc1ed990857c6f5eca23677f99dd491c64bf48d 66644 
embassy-domainatrix-dbgsym_0.1.660-2_amd64.deb
 f3ddc066e9ad1916f30e2ca50e67e45dd3a6ad5bb20aeebf823bf2c11bd7c570 7906 
embassy-domainatrix_0.1.660-2_amd64.buildinfo
 28c2e3a7b88efa9fbe33d56648244c3be39f049b15ec3dce8515849e5599a25d 62808 
embassy-domainatrix_0.1.660-2_amd64.deb
Files:
 134f3ca0c2b6cbaa48b9bad7780bb240 2269 science optional 
embassy-domainatrix_0.1.660-2.dsc
 c097d0263af06f5d5b511f48f14b041a 8252 science optional 
embassy-domainatrix_0.1.660-2.debian.tar.xz
 3d215f8731ad22543e54df26e88eb433 66644 debug optional 
embassy-domainatrix-dbgsym_0.1.660-2_amd64.deb
 d45374134c108d44490dc3258b35071e 7906 science optional 
embassy-domainatrix_0.1.660-2_amd64.buildinfo
 8c549d34d2e56fc66ba237e9911a5fb5 62808 science optional 
embassy-domainatrix_0.1.660-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAloB2hURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFWEw/8DhF8RszsfD8OqnjgmNhugI4Ow4bmG6ao
aavLGSrjOkaXN4syIMKsfyVIut+l79g3XLYEiBv+pI4dhnO2cZsZlOVXYuwlatE1
2SgKaoktYtd3pQhYZ3WpW9ngQ6lQn9Uyz15rPOMOHt4JHZwfe6/W4qqcdBZqr6mC
d+nJnHuJmqPxou/Pl5u3uRzZAu3O7ZP3H+4WHjYFoaRRzKLtS9i4SoM32YJoKR0K
cx4NFdgFOsWMxllT3A3GLiEkEOPzbU4FKNVopUcHc6Su0svY2I/ejYZeuvdBVeGo
hcjQX/bOGOoTfx8LTlKvtbDBBy4CjcIaYkVwt/ihNw/Zr/JIbwqLKDX5cwNDtw/u
HWus8QXb49zHEQ6HOOYPIj5u4U9TpT92IUCQIgK7M8L9ZGDTAoHYTYmDV/9/Mk/N
OP7nwz+vMwB0+5tlJ4IMWsIuZaFahYb0U3dnQIZg/AReUFM/yZyjQh8IIMsEggXb
QrxTqgs8qlyXTfC6f/9e/gfqc5wLx0MhBeIYAkeWarqWq+peLa510npUMTbptb5h
FMDCDV2+W+ebexpMo8Pb+gyrGG0/WQQxV280R8/f+l/8IKKwXB0zdspG79JfRGz7

Processed: libmariadb-dev: mariadb_config always returns the help text

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:rmysql
Bug #881073 [libmariadb-dev] libmariadb-dev: mariadb_config always returns the 
help text
Added indication that 881073 affects src:rmysql

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

Bug#881073: libmariadb-dev: mariadb_config always returns the help text

[Adrian Bunk]

Package: libmariadb-dev
Version: 10.2.7-1
Severity: serious
Control: affects -1 src:rmysql

$ mariadb_config --cflags
Copyright 2011-2015 MariaDB Corporation AB
Get compiler flags for using the MariaDB Connector/C.
Usage: /usr/lib/x86_64-linux-gnu/mariadb_config [OPTIONS]
  --cflags[-I/usr/include/mysql -I/usr/include/mysql/mysql]
  --include   [-I/usr/include/mysql -I/usr/include/mysql/mysql]
  --libs  [-L/usr/lib/x86_64-linux-gnu/ -lmariadb -lpthread -ldl -lm 
-lgnutls]
  --libs_r[-L/usr/lib/x86_64-linux-gnu/ -lmariadb -lpthread -ldl -lm 
-lgnutls]
  --libs_sys  [-lpthread -ldl -lm -lgnutls]
  --version   [10.2.7]
  --socket[/var/run/mysqld/mysqld.sock]
  --port  [3306]
  --plugindir [/usr/lib/x86_64-linux-gnu/mariadb3/plugin]
  --tlsinfo   [GnuTLS ]
$ 

Processed: Also affects dolphin-emu

[Debian Bug Tracking System]

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

> affects 881071 src:dolphin-emu
Bug #881071 [libsoil-dev] libsoil-dev: missing Depends: libsoil1 (= 
${binary:Version})
Added indication that 881071 affects src:dolphin-emu
> thanks
Stopping processing here.

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

Processed: libsoil-dev: missing Depends: libsoil1 (= ${binary:Version})

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:miceamaze
Bug #881071 [libsoil-dev] libsoil-dev: missing Depends: libsoil1 (= 
${binary:Version})
Added indication that 881071 affects src:miceamaze

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

Bug#881071: libsoil-dev: missing Depends: libsoil1 (= ${binary:Version})

[Adrian Bunk]

Package: libsoil-dev
Version: 1.07~20080707.dfsg-3
Severity: serious
Control: affects -1 src:miceamaze

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/miceamaze.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-DDATAPATH=\"/usr/share/games/miceamaze\" -I/usr/include/SDL -D_GNU_SOURCE=1 
-D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro src/AI.o 
src/AIVertexHeap.o src/Animal.o src/Arrow.o src/Button.o src/Config.o 
src/Cursor.o src/FPS.o src/Functions.o src/Game.o src/House.o src/HowToPlay.o 
src/Images.o src/Maze.o src/MenuAbout.o src/MenuMain.o src/MenuOptions.o 
src/MenuPlayers.o src/MenuSelectMaze.o src/Mouse.o src/Program.o 
src/RenderFlatText.o src/Snake.o src/Sound.o src/Spawner.o src/main.o -Wall 
-lGLC -lSOIL -L/usr/lib/x86_64-linux-gnu -lSDL -lSDL_mixer -lGL -lm -o miceamaze
/usr/bin/ld: cannot find -lSOIL
collect2: error: ld returned 1 exit status
Makefile:26: recipe for target 'miceamaze' failed
make[2]: *** [miceamaze] Error 1


Without libsoil1 /usr/lib/libSOIL.so is a dangling symlink.

Bug#881070: python3-django-celery-haystack: depends on obsolete transitional package python3-appconf

[Andreas Beckmann]

Package: python3-django-celery-haystack
Version: 0.10-1
Severity: serious
Tags: sid buster

Hi,

python3-appconf is now gone from sid.
Please switch to python3-django-appconf.

Andreas

Bug#881053: ppp: fails to compile because of mistake in rules file

[Adrian Bunk]

On Tue, Nov 07, 2017 at 02:46:59PM +0100, Christian Blum wrote:
> Package: ppp
> Version: 2.4.7-1+4
> Severity: serious
> Tags: patch
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear Maintainer,
> 
> the rules file contains a problem that keeps ppp from compiling. This patch 
> fixes the problem.
> 
> 
> --- debian/rules.ORIG 2017-11-07 14:43:08.026945955 +0100
> +++ debian/rules  2017-11-07 14:43:20.174879455 +0100
> @@ -156,7 +156,7 @@
>  # the build fails if there are any discrepancies in the symbols file in order
>  # to catch ABI changes.
>  override_dh_makeshlibs:
> - dh_makeshlibs --package=ppp -- -c2 -edebian/ppp/usr/sbin/pppd -V
> + dh_makeshlibs --package=ppp -- -c2 -edebian/ppp/usr/sbin/pppd --version
>   dh_makeshlibs --no-package=ppp
>...

-V looks correct, and it works everywhere else:
  https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppp.html

What is the exact error message you get?

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#881065: python-django-compressor: B-D on obsolete transitional package python3-appconf

[Andreas Beckmann]

Source: python-django-compressor
Version: 2.2-1
Severity: serious
Justification: fails to build from source

python3-appconf is now gone from sid.
Please switch to python3-django-appconf.

Andreas

Bug#874708: anthy (EUCJP->UTF-8) and *-anthy packages

[Osamu Aoki]

Hi,

On Mon, Nov 06, 2017 at 05:28:13AM -0500, Jeremy Bicha wrote:
> Control: tags -1 +moreinfo
>
> What exactly is the problem the missing library causes? This sounds
> like a normal library transition that Debian does all the time. The
> old library (libanthy0) is removed because everything in Debian will
> build against the new library (libanthy1).

No ABI change is involved.  Data passed from library call is now encoded
in UTF-8 instead of EUCJP by the new library (or I should say the new
library use new data in anthy-common in UTF-8)

> Osamu, can we lower the severity of this bug so that this package can
> migrate to testing?

See below.

On Tue, Nov 07, 2017 at 07:04:54PM +0900, d...@debian.org wrote:
> Control: tags -1 + moreinfo
> 
> 1:0.3-6 has been uploaded. Can we close this bug?

Actually, we may need to upload few manually updated packages.

One package just uploaded with such manual patch by NOKUBI Takatsugu.

  ibus-anthy_1.5.9-2.1_amd64.changes ACCEPTED unstable

So at least anthy is usable with ibus now in unstable.

Are *-anthy packages uploaded to cope with this new anthy just like ibus-anthy?
 fcitx-anthy
 hime-anthy
 scim-anthy
 uim-anthy

Otherwise, they are broken in unstable now. (I did not have time to test
them yet)

Even these are updated with manual patches, all these updated package
needs to move together from unstable to testing.  I am not very familiar
with this ABI breaking library update.  We may need to add BREAKS: to
anthy to ensure this.  (I am not sure)  That may reqire to upload -7 for
anthy.

Anyway, these need to be properly coordinated.

Jeremy, your guidance is highly appreciated.

Osamu