date:20171218

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

> reassign 884513 python-xhtml2pdf 0.2b-1
Bug #884513 {Done: Drew Parsons } 
[python-pisa,python-xhtml2pdf] python-pisa,python-xhtml2pdf: error when trying 
to install together
Bug reassigned from package 'python-pisa,python-xhtml2pdf' to 
'python-xhtml2pdf'.
No longer marked as found in versions pisa/3.0.32-4 and xhtml2pdf/0.2b-1.
No longer marked as fixed in versions xhtml2pdf/0.2b-2.
Bug #884513 {Done: Drew Parsons } [python-xhtml2pdf] 
python-pisa,python-xhtml2pdf: error when trying to install together
Marked as found in versions xhtml2pdf/0.2b-1.
> fixed 884513 0.2b-2
Bug #884513 {Done: Drew Parsons } [python-xhtml2pdf] 
python-pisa,python-xhtml2pdf: error when trying to install together
Marked as fixed in versions xhtml2pdf/0.2b-2.
> affects 884513 + python-pisa
Bug #884513 {Done: Drew Parsons } [python-xhtml2pdf] 
python-pisa,python-xhtml2pdf: error when trying to install together
Added indication that 884513 affects python-pisa
> thanks
Stopping processing here.

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

Processed: Re: Bug#884654: glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed

Processing control commands:

> found -1 2.54.1-1
Bug #884654 [src:glib2.0] glib2.0: FTBFS on amd64 buildd: gdbus-peer test: 
assertion 'source->ref_count > 0' failed
Marked as found in versions glib2.0/2.54.1-1.

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

Bug#884654: glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed

Control: found -1 2.54.1-1

On Mon, 18 Dec 2017 at 18:18:41 +, Simon McVittie wrote:
> On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote:
> > The failure on the buildd is new, although I think I might have seen it
> > before in local testing (but never reproducibly). It's probably some
> > rarely-hit race condition?
> 
> I can reproduce this by running the gdbus-peer test in a loop (this is
> with GLib git master, not Debian's GLib, but that's close enough).

I can also reproduce it by building 2.54.1-1 or 2.54.2-2 and re-running
that test in a loop, but not easily (running 100 times in a loop often
succeeds). Having looked at the history of the code involved, I think
this is a long-standing race condition; so this isn't a regression,
and shouldn't block testing migration.

smcv

Processed: unarchiving 876414, found 876414 in 343.22-1, found 876414 in 378.13-1, found 876414 in 381.22-1

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

> # the 375.xx series before 375.88 is buggy, too; 340.xx/304.xx are not buggy
> unarchive 876414
Bug #876414 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272
Unarchived Bug 876414
> found 876414 343.22-1
Bug #876414 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272
Marked as found in versions nvidia-graphics-drivers/343.22-1.
> found 876414 378.13-1
Bug #876414 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272
Marked as found in versions nvidia-graphics-drivers/378.13-1.
> found 876414 381.22-1
Bug #876414 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272
Marked as found in versions nvidia-graphics-drivers/381.22-1.
> thanks
Stopping processing here.

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

Bug#884687: marked as done (python-backports-shutil-get-terminal-size: missing depepdency on the python interpreter)

Your message dated Mon, 18 Dec 2017 23:49:47 +
with message-id 
and subject line Bug#884687: fixed in python-backports-shutil-get-terminal-size 
1.0.0-4
has caused the Debian Bug report #884687,
regarding python-backports-shutil-get-terminal-size: missing depepdency on the 
python interpreter
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.)


-- 
884687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-backports-shutil-get-terminal-size
Version: 1.0.0-3
Severity: serious

Dear maintainer,

python-backports-shutil-get-terminal-size is a Python package but lacks any 
dependency, including
one on the Python interpreter itself.

Most of the times this is due to using the wrong substvar, for instance
using ${python3:Depends} on a python2 package (or the reverse,
${python:Depends on a python3 package).
--- End Message ---
--- Begin Message ---
Source: python-backports-shutil-get-terminal-size
Source-Version: 1.0.0-4

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated 
python-backports-shutil-get-terminal-size 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, 19 Dec 2017 00:30:44 +0100
Source: python-backports-shutil-get-terminal-size
Binary: python-backports-shutil-get-terminal-size
Architecture: source all
Version: 1.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Julien Puydt 
Description:
 python-backports-shutil-get-terminal-size - Backport of the 
"shutil.get_terminal_size" function (Python 2)
Closes: 884687
Changes:
 python-backports-shutil-get-terminal-size (1.0.0-4) unstable; urgency=medium
 .
   * Fix a typo in the substvar depends (Closes: #884687)
   * Refresh packaging:
 - Use https in d/copyright's Format.
 - Bump dh compat to 10.
 - Bump d/watch to version 4.
 - Bump std-ver to 4.1.2.0.
 - Add lintian override for a silly warning.
Checksums-Sha1:
 82f711ff1636dac866678addaf4f65971dd735f1 2418 
python-backports-shutil-get-terminal-size_1.0.0-4.dsc
 dec29c9ef40a8a468bf8ef15e146e3299a2feee8 2256 
python-backports-shutil-get-terminal-size_1.0.0-4.debian.tar.xz
 d978e849460c86b0fdc24d325f10e142f837afec 4972 
python-backports-shutil-get-terminal-size_1.0.0-4_all.deb
 ededb37439ba53e0934a8b68509881ac0ed997bc 6580 
python-backports-shutil-get-terminal-size_1.0.0-4_amd64.buildinfo
Checksums-Sha256:
 02afa46089fe66e7801b963730d2bc3e78885ddb504ddd712fff56ded8ef107f 2418 
python-backports-shutil-get-terminal-size_1.0.0-4.dsc
 1886f2f7c338feb05230567916a247f5e0769a385af8f47f193bf60cebcbc3b9 2256 
python-backports-shutil-get-terminal-size_1.0.0-4.debian.tar.xz
 f12714adaf09666f74d03c3cc62edb0137bcdfdb078951de7973226653de9c01 4972 
python-backports-shutil-get-terminal-size_1.0.0-4_all.deb
 22070452f127f168504eb1e1203a22a97d581c029e32c5af7c3fe8f58aeab092 6580 
python-backports-shutil-get-terminal-size_1.0.0-4_amd64.buildinfo
Files:
 4f851e8047c5875a9765ef1d2b4e8d1f 2418 python optional 
python-backports-shutil-get-terminal-size_1.0.0-4.dsc
 1e9ae7f0f968fb9c7020bd5227ca84a8 2256 python optional 
python-backports-shutil-get-terminal-size_1.0.0-4.debian.tar.xz
 01ade914f956bb5f588690b053c743ec 4972 python optional 
python-backports-shutil-get-terminal-size_1.0.0-4_all.deb
 442b5b2eb7793739e3b3141f0d5789cc 6580 python optional 
python-backports-shutil-get-terminal-size_1.0.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAlo4T9UZHGp1bGllbi5w
dXlkdEBsYXBvc3RlLm5ldAAKCRAExTvX/gMFUcAiD/9PA3Nh3q2SKNUiXwry14Xf
Yvy3uN62nalMM9DMksT8MXn7REBdDtrdwkRmFz7uVhhx8guqcPqFL6zmGhvjCvAr
m8nak1QOD87FMZRiitkIXDDNsVLkW9EgZ+WfzPJSFQGjwFZcKNF7gh3imrHOJzVT

Bug#880883: FTBFS on arm64: test suite times out (on arm-arm-04)

On Fri, 17 Nov 2017 at 18:37:42 +0100, Emilio Pozuelo Monfort wrote:
> I gave it back again, and it again got picked by arm-arm-04. With the help 
> from
> jcristau (as I don't have access to that machine) I determined that the build
> gets killed while running the closures test, which gets executed by is way too
> slow on that machine (it'd take around 200 minutes to complete it).

In 2.54.2-3 I've cut that test down to 1% of the usual repetitions on
arm64, which seems like enough to prove that this functionality does
basically work. The fact that it's far slower than on other CPUs is
still a bug, but hopefully one that can be downgraded to important.

smcv

Bug#884659: glib2.0: sometimes FTBFS on reproducible-builds: gwakeup, gwakeup-fallback tests terminated by SIGALRM

On Mon, 18 Dec 2017 at 10:17:54 +, Simon McVittie wrote:
> The thread count, number of tokens and token TTL are probably also completely
> arbitrary, and could be reduced, at the cost of being less likely to
> detect bugs (unfortunately this sort of threading stress-test is usually
> probabilistic).

In 2.54.2-3 I've reduced the number of threads and the TTL, both by a
factor of 10. I don't think this is really a correct solution (it's now
less likely to find bugs), but it'll let us see what happens. If the
builds succeed I'll drop this bug down to a non-RC severity.

smcv

Bug#884660: marked as done (glib2.0: sometimes FTBFS on reproducible-builds: gdbus-threading test: assertion failed (elapsed_msec < 8000): (8220 < 8000))

Your message dated Mon, 18 Dec 2017 23:34:09 +
with message-id 
and subject line Bug#884660: fixed in glib2.0 2.54.2-3
has caused the Debian Bug report #884660,
regarding glib2.0: sometimes FTBFS on reproducible-builds: gdbus-threading 
test: assertion failed (elapsed_msec < 8000): (8220 < 8000)
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.)


-- 
884660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.54.2-2
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

glib2.0 fails to build from source on amd64. This happens both on the
buildd
https://buildd.debian.org/status/fetch.php?pkg=glib2.0=amd64=2.54.2-2=1513222982=0
and on the reproducible infrastructure
https://tests.reproducible-builds.org/debian/logs/unstable/amd64/glib2.0_2.54.2-2.build2.log.gz.
Though reproducible experiences more failures (including gwakeup and
gmenumodel). It seems unlikely that this fixes itself somehow.

Helmut
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.54.2-3

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Dec 2017 21:30:18 +
Source: glib2.0
Binary: libglib2.0-0 libglib2.0-tests libglib2.0-udeb libglib2.0-bin 
libglib2.0-dev libglib2.0-dev-bin libglib2.0-data libglib2.0-doc libgio-fam
Architecture: source
Version: 2.54.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Description:
 libgio-fam - GLib Input, Output and Streaming Library (fam module)
 libglib2.0-0 - GLib library of C routines
 libglib2.0-bin - Programs for the GLib library
 libglib2.0-data - Common files for GLib library
 libglib2.0-dev - Development files for the GLib library
 libglib2.0-dev-bin - Development utilities for the GLib library
 libglib2.0-doc - Documentation files for the GLib library
 libglib2.0-tests - GLib library of C routines - installed tests
 libglib2.0-udeb - GLib library of C routines - minimal runtime (udeb)
Closes: 884660 884661
Changes:
 glib2.0 (2.54.2-3) unstable; urgency=medium
 .
   * Team upload
   * d/patches: Re-export with gbp pq
   * d/patches: Use `gbp pq export`-style metadata, retrieving authors
 and dates from d/changelog where needed
   * d/p/closures-test-Run-fewer-iterations-on-ARM64.patch: New patch.
 tests/refcount/closures: Run fewer iterations on ARM64
 (mitigates: #880883)
   * d/p/gdbus-threading-test-Allow-even-longer-for-test_method_ca.patch:
 New patch. Allow even longer for the gdbus-threading test, and
 re-enable it on 32-bit ARM now that the timeout is longer
 (Closes: #884660)
   * d/p/gmenumodel-test-If-something-goes-wrong-don-t-wait-foreve.patch,
 d/p/gmenumodel-test-Wait-for-the-expected-events-to-happen.patch:
 Add patches to make the GMenuModel test more patient (Closes: #884661)
   * d/p/gwakeuptest-Be-less-parallel-unless-invoked-with-m-slow.patch:
 Reduce number of threads and number of operations in response to
 timeout on reproducible-builds infrastructure (mitigates: #884659)
Checksums-Sha1:
 d009c94701762926c4d7117f13076feaea7cd2a6 3268 glib2.0_2.54.2-3.dsc
 3ff74eaf3678d118f84006c554cd2a7ecdc7e902 74776 glib2.0_2.54.2-3.debian.tar.xz
 98071842c827ef7df9a5f3e37193096b91866889 8093 glib2.0_2.54.2-3_source.buildinfo
Checksums-Sha256:
 7e3b46d66a5ab76c709551c0e48110a37bca72632934653acb539a967df23e3c 3268 
glib2.0_2.54.2-3.dsc
 ff89f8ca531662f29da49a4c3959759bb6d8a60d09d9ec177a58c482cac2e9ed 74776 
glib2.0_2.54.2-3.debian.tar.xz
 652c85fc1dcd14e2ad5901a2cce7e6aee068c5d0bd60b5b6b4714e6845dcb4b5 8093 
glib2.0_2.54.2-3_source.buildinfo
Files:
 9d555135ac22e8197f1370b34c2bcc0f 3268 libs optional

Bug#884661: marked as done (glib2.0: sometimes FTBFS on reproducible-builds: gmenumodel test: assertion failed (items_changed_count == 1): (0 == 1))

Your message dated Mon, 18 Dec 2017 23:34:09 +
with message-id 
and subject line Bug#884661: fixed in glib2.0 2.54.2-3
has caused the Debian Bug report #884661,
regarding glib2.0: sometimes FTBFS on reproducible-builds: gmenumodel test: 
assertion failed (items_changed_count == 1): (0 == 1)
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.)


-- 
884661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.54.2-2
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

glib2.0 fails to build from source on amd64. This happens both on the
buildd
https://buildd.debian.org/status/fetch.php?pkg=glib2.0=amd64=2.54.2-2=1513222982=0
and on the reproducible infrastructure
https://tests.reproducible-builds.org/debian/logs/unstable/amd64/glib2.0_2.54.2-2.build2.log.gz.
Though reproducible experiences more failures (including gwakeup and
gmenumodel). It seems unlikely that this fixes itself somehow.

Helmut
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.54.2-3

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Dec 2017 21:30:18 +
Source: glib2.0
Binary: libglib2.0-0 libglib2.0-tests libglib2.0-udeb libglib2.0-bin 
libglib2.0-dev libglib2.0-dev-bin libglib2.0-data libglib2.0-doc libgio-fam
Architecture: source
Version: 2.54.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Description:
 libgio-fam - GLib Input, Output and Streaming Library (fam module)
 libglib2.0-0 - GLib library of C routines
 libglib2.0-bin - Programs for the GLib library
 libglib2.0-data - Common files for GLib library
 libglib2.0-dev - Development files for the GLib library
 libglib2.0-dev-bin - Development utilities for the GLib library
 libglib2.0-doc - Documentation files for the GLib library
 libglib2.0-tests - GLib library of C routines - installed tests
 libglib2.0-udeb - GLib library of C routines - minimal runtime (udeb)
Closes: 884660 884661
Changes:
 glib2.0 (2.54.2-3) unstable; urgency=medium
 .
   * Team upload
   * d/patches: Re-export with gbp pq
   * d/patches: Use `gbp pq export`-style metadata, retrieving authors
 and dates from d/changelog where needed
   * d/p/closures-test-Run-fewer-iterations-on-ARM64.patch: New patch.
 tests/refcount/closures: Run fewer iterations on ARM64
 (mitigates: #880883)
   * d/p/gdbus-threading-test-Allow-even-longer-for-test_method_ca.patch:
 New patch. Allow even longer for the gdbus-threading test, and
 re-enable it on 32-bit ARM now that the timeout is longer
 (Closes: #884660)
   * d/p/gmenumodel-test-If-something-goes-wrong-don-t-wait-foreve.patch,
 d/p/gmenumodel-test-Wait-for-the-expected-events-to-happen.patch:
 Add patches to make the GMenuModel test more patient (Closes: #884661)
   * d/p/gwakeuptest-Be-less-parallel-unless-invoked-with-m-slow.patch:
 Reduce number of threads and number of operations in response to
 timeout on reproducible-builds infrastructure (mitigates: #884659)
Checksums-Sha1:
 d009c94701762926c4d7117f13076feaea7cd2a6 3268 glib2.0_2.54.2-3.dsc
 3ff74eaf3678d118f84006c554cd2a7ecdc7e902 74776 glib2.0_2.54.2-3.debian.tar.xz
 98071842c827ef7df9a5f3e37193096b91866889 8093 glib2.0_2.54.2-3_source.buildinfo
Checksums-Sha256:
 7e3b46d66a5ab76c709551c0e48110a37bca72632934653acb539a967df23e3c 3268 
glib2.0_2.54.2-3.dsc
 ff89f8ca531662f29da49a4c3959759bb6d8a60d09d9ec177a58c482cac2e9ed 74776 
glib2.0_2.54.2-3.debian.tar.xz
 652c85fc1dcd14e2ad5901a2cce7e6aee068c5d0bd60b5b6b4714e6845dcb4b5 8093 
glib2.0_2.54.2-3_source.buildinfo
Files:
 9d555135ac22e8197f1370b34c2bcc0f 3268 libs optional glib2.0_2.54.2-3.dsc

Bug#884687: marked as pending

2017-12-18 Thread Julien Puydt

tag 884687 pending
thanks

Hello,

Bug #884687 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/python-modules/packages/python-backports-shutil-get-terminal-size.git/commit/?id=2c27e43

---
commit 2c27e43625342531739cf54e34582462060bfeff
Author: Julien Puydt 
Date:   Mon Dec 18 18:50:27 2017 +0100

Fix typo in the substvar deps (Closes: #884687)

diff --git a/debian/changelog b/debian/changelog
index 13beca8..54fa404 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-backports-shutil-get-terminal-size (1.0.0-4) UNRELEASED; urgency=medium
+
+  * Fix a typo in the substvar depends (Closes: #884687)
+
+ -- Julien Puydt   Mon, 18 Dec 2017 18:45:55 +0100
+
 python-backports-shutil-get-terminal-size (1.0.0-3) unstable; urgency=medium
 
   * Declare Breaks with old python-backports.ssl-match-hostname so

Processed: Bug#884687 marked as pending

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

> tag 884687 pending
Bug #884687 [python-backports-shutil-get-terminal-size] 
python-backports-shutil-get-terminal-size: missing depepdency on the python 
interpreter
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#884662: glib2.0: sometimes FTBFS on reproducible-builds: tar: ./usr/share/locale/en_??/LC_MESSAGES/glib20.mo/: Cannot savedir: Not a directory

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote:
> [#884662] (a build failure inside dpkg-builddeb, not a test failure)
> I don't know what is going on, and it doesn't seem particularly likely
> to be a GLib bug - GLib just puts files in a tree like any other package,
> so I'm not sure how it would trigger this particular failure. It can be
> seen in these logs:
> https://tests.reproducible-builds.org/debian/rbuild/buster/i386/glib2.0_2.54.1-1.rbuild.log
> https://tests.reproducible-builds.org/debian/rbuild/unstable/armhf/glib2.0_2.54.2-2.rbuild.log
> (not build2, so we presumably can't blame disorderfs either).

tar and dpkg maintainers: does this look at all familiar to you, or
can you think of anything that GLib might be doing strangely with its
translations that would somehow make tar think it needed to treat the
regular file glib20.mo as a directory? It's an ordinary GNU gettext .gmo
file, with nothing GLib-specific that I'm aware of, and in particular
File::StripNondeterminism was able to open and rewrite it like a
regular file.

This is on the reproducible-builds infrastructure, so if there are any
oddities implied by that, they apply here (for example I think it's a
tmpfs - although I've been able to build GLib in a large tmpfs on my
laptop without problems).

I don't know whether it's significant or just coincidence that the two
languages affected in the failing builds that I've seen are the only two
of the form en_??.

Unfortunately this is pbuilder, not sbuild, so the log doesn't list the
versions of tar and dpkg used.

The most relevant bits of the (armhf + all) build log (the i386 + all
failure is similar, but en_GB is the one that fails there):

make[4]: Entering directory '/build/1st/glib2.0-2.54.2/debian/build/deb/po'
mkdir -p /build/1st/glib2.0-2.54.2/debian/tmp/usr/share; \
catalogs='af.gmo am.gmo an.gmo ar.gmo as.gmo ast.gmo az.gmo be.gmo 
b...@latin.gmo bg.gmo bn.gmo bn_IN.gmo bs.gmo ca.gmo c...@valencia.gmo cs.gmo 
cy.gmo da.gmo de.gmo dz.gmo el.gmo en_CA.gmo en_GB.gmo e...@shaw.gmo eo.gmo 
es.gmo et.gmo eu.gmo fa.gmo fi.gmo fr.gmo fur.gmo ga.gmo gd.gmo gl.gmo gu.gmo 
he.gmo hi.gmo hr.gmo hu.gmo hy.gmo id.gmo is.gmo it.gmo ja.gmo ka.gmo kk.gmo 
kn.gmo ko.gmo ku.gmo lt.gmo lv.gmo mai.gmo mg.gmo mk.gmo ml.gmo mn.gmo mr.gmo 
ms.gmo nb.gmo nds.gmo ne.gmo nl.gmo nn.gmo oc.gmo or.gmo pa.gmo pl.gmo ps.gmo 
pt.gmo pt_BR.gmo ro.gmo ru.gmo rw.gmo si.gmo sk.gmo sl.gmo sq.gmo sr.gmo 
s...@latin.gmo s...@ije.gmo sv.gmo ta.gmo te.gmo tg.gmo th.gmo tl.gmo tr.gmo 
ug.gmo tt.gmo uk.gmo vi.gmo wa.gmo xh.gmo yi.gmo zh_CN.gmo zh_HK.gmo 
zh_TW.gmo'; \
for cat in $catalogs; do \
  cat=`basename $cat`; \
  case "$cat" in \
*.gmo) destdir=/usr/share/locale;; \
*) destdir=/usr/lib/arm-linux-gnueabihf/locale;; \
  esac; \
  lang=`echo $cat | sed 's/\.gmo$//'`; \
  dir=/build/1st/glib2.0-2.54.2/debian/tmp$destdir/$lang/LC_MESSAGES; \
  mkdir -p $dir; \
  if test -r $cat; then \
/usr/bin/install -c -m 644 $cat $dir/glib20.mo; \
echo "installing $cat as $dir/glib20.mo"; \
  else \
/usr/bin/install -c -m 644 ../../../../po/$cat $dir/glib20.mo; \
echo "installing ../../../../po/$cat as" \
 "$dir/glib20.mo"; \
  fi; \
...
installing ../../../../po/af.gmo as 
/build/1st/glib2.0-2.54.2/debian/tmp/usr/share/locale/af/LC_MESSAGES/glib20.mo
... and the same for many more languages ...
   dh_strip_nondeterminism
...
Normalized 
debian/libglib2.0-data/usr/share/locale/dz/LC_MESSAGES/glib20.mo
... and the same for many more languages ...
...
   dh_builddeb
...
dpkg-deb: building package 'libglib2.0-data' in 
'../libglib2.0-data_2.54.2-2_all.deb'.
tar: ./usr/share/locale/en_CA/LC_MESSAGES/glib20.mo/: Cannot savedir: Not a 
directory
tar: Exiting with failure status due to previous errors
...
dpkg-deb: error: tar -cf subprocess returned error exit status 2
dh_builddeb: dpkg-deb --build debian/libglib2.0-data .. returned exit code 2

Thanks,
smcv

Bug#847611: Patch

2017-12-18 Thread Ian Beckwith

Hi,

On Mon, Dec 18, 2017 at 09:42:17PM +0100, Sebastian Andrzej Siewior wrote:
> On 2017-12-17 18:35:17 [+0100], Hilko Bengen wrote:
> > Control: tag -1 patch -fixed-upstream
> > 
> > I don't see where the direct struct access issues have been fixed
> > upstream, the source code snapshot available from
> > http://www.kermitproject.org/ckdaily.html still has lots of those.

I'm shamefully MIA at the moment but upstream is active and worth contacting:

f...@columbia.edu

thanks for your help!

Ian.

-- 
Ian Beckwith - i...@debian.org - i...@erislabs.net - http://erislabs.net/ianb/
New key: 4096R/A796 3918 B66A A6DD CFC5  EFF2 17D7 13AD 62E8 8618

Bug#828557: Patch for sslsniff, request for review

2017-12-18 Thread Hilko Bengen

* Sebastian Andrzej Siewior:

> It is not back compatible with openssl 1.0.2

Aware of that. Chose to ignore backwards compatibility for now.

I took care of the const issue and eliminated the leaks using a
stack-allocated buffer. New patch attached.

Cheers,
-Hilko
Index: sslsniff/SessionCache.cpp
===
--- sslsniff.orig/SessionCache.cpp
+++ sslsniff/SessionCache.cpp
@@ -47,7 +47,9 @@ void SessionCache::removeSessionId(unsig
 }
 
 int SessionCache::setNewSessionId(SSL *s, SSL_SESSION *session) {
-  return setNewSessionId(s, session, session->session_id, session->session_id_length);
+  unsigned int id_length;
+  const unsigned char *id = SSL_SESSION_get_id(session, _length);
+  return setNewSessionId(s, session, (unsigned char*)id, id_length);
 }
 
 int SessionCache::setNewSessionId(SSL *s, SSL_SESSION *session, 
@@ -94,7 +96,7 @@ int SessionCache::setNewSessionId(SSL *s
   return 1;  
 }
 
-SSL_SESSION * SessionCache::getSessionId(SSL *s, unsigned char *id, int idLength, int *ref) {
+SSL_SESSION * SessionCache::getSessionId(SSL *s, const unsigned char *id, int idLength, int *ref) {
   int i;
   unsigned char *b;
 
@@ -117,7 +119,7 @@ SSL_SESSION * SessionCache::getSessionId
 
 // Trampoline Functions.  Yay C.
 
-SSL_SESSION * SessionCache::getSessionIdTramp(SSL *s, unsigned char *id, int idLength, int *ref) {
+SSL_SESSION * SessionCache::getSessionIdTramp(SSL *s, const unsigned char *id, int idLength, int *ref) {
   return SessionCache::getInstance()->getSessionId(s, id, idLength, ref);
 }
 
Index: sslsniff/certificate/Certificate.hpp
===
--- sslsniff.orig/certificate/Certificate.hpp
+++ sslsniff/certificate/Certificate.hpp
@@ -92,7 +92,8 @@ private:
   }
 
   void parseCommonName(X509 *cert) {
-std::string distinguishedName(cert->name);
+char buf[4096];
+std::string distinguishedName(X509_NAME_oneline(X509_get_subject_name(cert), buf, sizeof(buf)));
 std::string::size_type cnIndex = distinguishedName.find("CN=");
 
 if (cnIndex == std::string::npos) throw BadCertificateException();
Index: sslsniff/certificate/TargetedCertificateManager.cpp
===
--- sslsniff.orig/certificate/TargetedCertificateManager.cpp
+++ sslsniff/certificate/TargetedCertificateManager.cpp
@@ -115,8 +115,9 @@ void TargetedCertificateManager::getCert
 
 void TargetedCertificateManager::dump() {
   std::list::iterator i;
+  char buf[4096];
 
   for(i=certificates.begin(); i != certificates.end(); ++i) 
-std::cout << "Certificate: " << (*i)->getCert()->name << std::endl;
+std::cout << "Certificate: " << X509_NAME_oneline(X509_get_subject_name((*i)->getCert()), buf, sizeof(buf)) << std::endl;
 
 }
Index: sslsniff/SessionCache.hpp
===
--- sslsniff.orig/SessionCache.hpp
+++ sslsniff/SessionCache.hpp
@@ -49,12 +49,12 @@ class SessionCache {
 
 public:
   static SessionCache* getInstance();
-  static SSL_SESSION * getSessionIdTramp(SSL *s, unsigned char *id, int idLength, int *ref);
+  static SSL_SESSION * getSessionIdTramp(SSL *s, const unsigned char *id, int idLength, int *ref);
   static int setNewSessionIdTramp(SSL *s, SSL_SESSION *session);
 
   int setNewSessionId(SSL *s, SSL_SESSION *session);
   int setNewSessionId(SSL *s, SSL_SESSION *session, unsigned char *id, int idLength);
-  SSL_SESSION * getSessionId(SSL *s, unsigned char *id, int idLength, int *ref);
+  SSL_SESSION * getSessionId(SSL *s, const unsigned char *id, int idLength, int *ref);
 
 private:
   static SessionCache *sessionCache;

Bug#884738: openjpeg2: CVE-2017-17480: stack-based buffer overflow in pgxtovolume function in jp3d/convert.c

2017-12-18 Thread Salvatore Bonaccorso

Source: openjpeg2
Version: 2.1.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/uclouvain/openjpeg/issues/1044

Hi,

the following vulnerability was published for openjpeg2.

CVE-2017-17480[0]:
| In OpenJPEG 2.3.0, a stack-based buffer overflow was discovered in the
| pgxtovolume function in jp3d/convert.c. The vulnerability causes an
| out-of-bounds write, which may lead to remote denial of service or
| possibly remote code execution.

Note there is as well the CVE-2017-17479 assignment, for the
jpwl/convert.c part. But AFAICS the Debian packagagins has overall
BUILD_JPWL:BOOL=OFF, so that one can be considered unimportant since
only present as in the source, but not in the resulting binary
packages. Though if upstream fixes the both issues, then fixes could
be applied.

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-17480
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17480
[1] https://github.com/uclouvain/openjpeg/issues/1044

Regards,
Salvatore

Processed: Bug#884661 marked as pending

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

> tag 884661 pending
Bug #884661 [src:glib2.0] glib2.0: sometimes FTBFS on reproducible-builds: 
gmenumodel test: assertion failed (items_changed_count == 1): (0 == 1)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#884661: marked as pending

tag 884661 pending
thanks

Hello,

Bug #884661 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-gnome/glib.git/commit/?id=889b168

---
commit 889b1685dcddbb25213be112e5f3b4f6895f4b51
Author: Simon McVittie 
Date:   Mon Dec 18 17:53:06 2017 +

Add patches to make the GMenuModel test more patient (Closes: #884661)

diff --git a/debian/changelog b/debian/changelog
index 1640b08..3b165ca 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,6 +10,9 @@ glib2.0 (2.54.2-3) UNRELEASED; urgency=medium
 New patch. Allow even longer for the gdbus-threading test, and
 re-enable it on 32-bit ARM now that the timeout is longer
 (Closes: #884660)
+  * d/p/gmenumodel-test-If-something-goes-wrong-don-t-wait-foreve.patch,
+d/p/gmenumodel-test-Wait-for-the-expected-events-to-happen.patch:
+Add patches to make the GMenuModel test more patient (Closes: #884661)
 
  -- Simon McVittie   Mon, 18 Dec 2017 10:47:35 +

Processed: fixed 874115 in 2.1.0-2+deb8u3, fixed 874115 in 2.1.2-1.1+deb9u2

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

> fixed 874115 2.1.0-2+deb8u3
Bug #874115 {Done: Mathieu Malaterre } [src:openjpeg2] 
openjpeg2: CVE-2017-14041: Stack-based buffer over-write in pgxtoimage function 
in bin/jp2/convert.c
Marked as fixed in versions openjpeg2/2.1.0-2+deb8u3.
> fixed 874115 2.1.2-1.1+deb9u2
Bug #874115 {Done: Mathieu Malaterre } [src:openjpeg2] 
openjpeg2: CVE-2017-14041: Stack-based buffer over-write in pgxtoimage function 
in bin/jp2/convert.c
Marked as fixed in versions openjpeg2/2.1.2-1.1+deb9u2.
> thanks
Stopping processing here.

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

Processed: bug 884654 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=791754

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

> forwarded 884654 https://bugzilla.gnome.org/show_bug.cgi?id=791754
Bug #884654 [src:glib2.0] glib2.0: FTBFS on amd64 buildd: gdbus-peer test: 
assertion 'source->ref_count > 0' failed
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=791754'.
> thanks
Stopping processing here.

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

Bug#847611: Patch

2017-12-18 Thread Sebastian Andrzej Siewior

On 2017-12-17 18:35:17 [+0100], Hilko Bengen wrote:
> Control: tag -1 patch -fixed-upstream
> 
> I don't see where the direct struct access issues have been fixed
> upstream, the source code snapshot available from
> http://www.kermitproject.org/ckdaily.html still has lots of those.
> 
> I have prepared a patch that fixes building with OpenSSL 1.1 and would
> appreciate a review.

>Index: ckermit-302/ck_ssl.c
>===
>--- ckermit-302.orig/ck_ssl.c
>+++ ckermit-302/ck_ssl.c
>@@ -975,13 +981,15 @@ static DH *
> get_dh1536()
> {
> DH *dh=NULL;
>+BIGNUM *p, *g;
> 
> if ((dh=DH_new()) == NULL)
> return(NULL);
>-dh->p=BN_bin2bn(dh1536_p,sizeof(dh1536_p),NULL);
>-dh->g=BN_bin2bn(dh1536_g,sizeof(dh1536_g),NULL);
>-if ((dh->p == NULL) || (dh->g == NULL))
>+p=BN_bin2bn(dh1536_p,sizeof(dh1536_p),NULL);
>+g=BN_bin2bn(dh1536_g,sizeof(dh1536_g),NULL);
>+if ((p == NULL) || (g == NULL))
> return(NULL);
>+DH_set0_pqg(dh, p, NULL, g);
> return(dh);

Those DH values should not be static / compiled in (e.g. the same on
every server) but not the scope of the patch…

> }
> 
>@@ -1457,13 +1468,15 @@ the build.\r\n\r\n");
> 
> #ifdef ZLIB
> cm = COMP_zlib();
>-if (cm != NULL && cm->type != NID_undef) {
>+if (cm != NULL && SSL_COMP_get_id(cm) != NID_undef) {
> SSL_COMP_add_compression_method(0xe0, cm); /* EAY's ZLIB ID */
> }
> #endif /* ZLIB */
>+#if 0 /* COMP_rle has apparently been removed in OpenSSL 1.1 */
> cm = COMP_rle();
> if (cm != NULL && cm->type != NID_undef)
> SSL_COMP_add_compression_method(0xe1, cm); /* EAY's RLE ID */
>+#endif
yes, but that ZLIB in the above shouldn't work since it should not be
compiled in :) Anyway, a check for OpenSSL version instead that if0
would be better.

>@@ -2583,7 +2598,7 @@ ssl_anonymous_cipher(ssl) SSL * ssl;
> int
> ssl_verify_crl(int ok, X509_STORE_CTX *ctx)
> {
>-X509_OBJECT obj;
>+X509_OBJECT *obj = X509_OBJECT_new();
this may be NULL

> X509_NAME *subject = NULL;
> X509_NAME *issuer = NULL;
> X509 *xs = NULL;
>@@ -2649,11 +2664,10 @@ ssl_verify_crl(int ok, X509_STORE_CTX *c
>  * Try to retrieve a CRL corresponding to the _subject_ of
>  * the current certificate in order to verify it's integrity.
>  */

and before that where were two return statemens where you would leak
`obj'.

>-memset((char *), 0, sizeof(obj));
> X509_STORE_CTX_init(store_ctx, crl_store, NULL, NULL);
>-rc = X509_STORE_get_by_subject(store_ctx, X509_LU_CRL, subject, );
>+rc = X509_STORE_get_by_subject(store_ctx, X509_LU_CRL, subject, obj);
> X509_STORE_CTX_cleanup(store_ctx);
>-crl = obj.data.crl;
>+crl = X509_OBJECT_get0_X509_CRL(obj);
> if (rc > 0 && crl != NULL) {
> /*
>  * Verify the signature on this CRL
>@@ -2661,7 +2675,7 @@ ssl_verify_crl(int ok, X509_STORE_CTX *c
> if (X509_CRL_verify(crl, X509_get_pubkey(xs)) <= 0) {
> fprintf(stderr, "Invalid signature on CRL!\n");
> X509_STORE_CTX_set_error(ctx, X509_V_ERR_CRL_SIGNATURE_FAILURE);
>-X509_OBJECT_free_contents();
>+X509_OBJECT_free(obj);
> X509_STORE_CTX_free(store_ctx);
> return 0;
> }
>@@ -2674,7 +2688,7 @@ ssl_verify_crl(int ok, X509_STORE_CTX *c
> fprintf(stderr, "Found CRL has invalid nextUpdate field.\n");
> X509_STORE_CTX_set_error(ctx,
> 
> X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD);
>-X509_OBJECT_free_contents();
>+X509_OBJECT_free();
> X509_STORE_CTX_free(store_ctx);
> return 0;
> }
>@@ -2683,11 +2697,11 @@ ssl_verify_crl(int ok, X509_STORE_CTX *c
> "Found CRL is expired - revoking all certificates until you get updated 
> CRL.\n"
> );
> X509_STORE_CTX_set_error(ctx, X509_V_ERR_CRL_HAS_EXPIRED);
>-X509_OBJECT_free_contents();
>+X509_OBJECT_free();
> X509_STORE_CTX_free(store_ctx);
> return 0;
> }
>-X509_OBJECT_free_contents();
>+X509_OBJECT_free();

I *think* that this won't work. You free `obj' here and in the next hunk
you use it again.

> }
> 
> /*
>@@ -2698,7 +2712,7 @@ ssl_verify_crl(int ok, X509_STORE_CTX *c
> X509_STORE_CTX_init(store_ctx, crl_store, NULL, NULL);
> rc = X509_STORE_get_by_subject(store_ctx, X509_LU_CRL, issuer, );
> X509_STORE_CTX_free(store_ctx);   /* calls 
> X509_STORE_CTX_cleanup() */
>-crl = obj.data.crl;
>+crl = X509_OBJECT_get0_X509_CRL(obj);
> if (rc > 0 && crl != NULL) {
> /*
>  * Check if the current certificate is revoked by this CRL
>@@ -2706,19 +2720,19 @@ ssl_verify_crl(int ok, X509_STORE_CTX *c
> n = sk_X509_REVOKED_num(X509_CRL_get_REVOKED(crl));
> for (i = 0; i < n; i++) {
> revoked

Bug#828557: Patch for sslsniff, request for review

2017-12-18 Thread Sebastian Andrzej Siewior

On 2017-12-17 19:32:52 [+0100], Hilko Bengen wrote:
> Control: tag -1 patch
> 
> Hi,
> 
> here's a patch that fixes the OpenSSL-1.1-related FTBFS for sslsniff.
> 
> I'd appreciate a review of the patch.

It is not back compatible with openssl 1.0.2

>Index: sslsniff/SessionCache.cpp
>===
>--- sslsniff.orig/SessionCache.cpp
>+++ sslsniff/SessionCache.cpp
>@@ -47,7 +47,9 @@ void SessionCache::removeSessionId(unsig
> }
> 
> int SessionCache::setNewSessionId(SSL *s, SSL_SESSION *session) {
>-  return setNewSessionId(s, session, session->session_id, 
>session->session_id_length);
>+  unsigned int id_length;
>+  const unsigned char *id = SSL_SESSION_get_id(session, _length);
>+  return setNewSessionId(s, session, (unsigned char*)id, id_length);
> }
> 
> int SessionCache::setNewSessionId(SSL *s, SSL_SESSION *session, 
>@@ -117,8 +119,8 @@ SSL_SESSION * SessionCache::getSessionId
> 
> // Trampoline Functions.  Yay C.
> 
>-SSL_SESSION * SessionCache::getSessionIdTramp(SSL *s, unsigned char *id, int 
>idLength, int *ref) {
>-  return SessionCache::getInstance()->getSessionId(s, id, idLength, ref);
>+SSL_SESSION * SessionCache::getSessionIdTramp(SSL *s, const unsigned char 
>*id, int idLength, int *ref) {
>+  return SessionCache::getInstance()->getSessionId(s, (unsigned char*)id, 
>idLength, ref);

since you propage that `const' to getSessionIdTramp(), you could propage it
further and drop that cast.

> }
> 
> int SessionCache::setNewSessionIdTramp(SSL *s, SSL_SESSION *session) {
>Index: sslsniff/SessionCache.hpp
>===
>--- sslsniff.orig/SessionCache.hpp
>+++ sslsniff/SessionCache.hpp
>@@ -49,7 +49,7 @@ class SessionCache {
> 
> public:
>   static SessionCache* getInstance();
>-  static SSL_SESSION * getSessionIdTramp(SSL *s, unsigned char *id, int 
>idLength, int *ref);
>+  static SSL_SESSION * getSessionIdTramp(SSL *s, const unsigned char *id, int 
>idLength, int *ref);
>   static int setNewSessionIdTramp(SSL *s, SSL_SESSION *session);
> 
>   int setNewSessionId(SSL *s, SSL_SESSION *session);
>Index: sslsniff/certificate/Certificate.hpp
>===
>--- sslsniff.orig/certificate/Certificate.hpp
>+++ sslsniff/certificate/Certificate.hpp
>@@ -92,7 +92,7 @@ private:
>   }
> 
>   void parseCommonName(X509 *cert) {
>-std::string distinguishedName(cert->name);
>+std::string 
>distinguishedName(X509_NAME_oneline(X509_get_subject_name(cert), NULL, 0));

X509_NAME_oneline() allocates memory which you leak.

> std::string::size_type cnIndex = distinguishedName.find("CN=");

That part grabs the hostname from the CN= part of the subject. I haven't
look *why* this is done but usually one wants to check the "subject
alternative name" extension and the content may conttain an asterisk.

> if (cnIndex == std::string::npos) throw BadCertificateException();
>Index: sslsniff/certificate/TargetedCertificateManager.cpp
>===
>--- sslsniff.orig/certificate/TargetedCertificateManager.cpp
>+++ sslsniff/certificate/TargetedCertificateManager.cpp
>@@ -117,6 +117,6 @@ void TargetedCertificateManager::dump()
>   std::list::iterator i;
> 
>   for(i=certificates.begin(); i != certificates.end(); ++i) 
>-std::cout << "Certificate: " << (*i)->getCert()->name << std::endl;
>+std::cout << "Certificate: " << 
>X509_NAME_oneline(X509_get_subject_name((*i)->getCert()), NULL, 0) << 
>std::endl;

also a leak.

> 
> }

> Cheers,
> -Hilko

Sebastian

Bug#884645: marked as done (qupzilla-plugin-{gnome-keyring,kwallet}: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/qupzilla/lib{GnomeKeyring,KWallet}Passwords.so)

Your message dated Mon, 18 Dec 2017 19:06:23 +
with message-id 
and subject line Bug#884645: fixed in qupzilla 2.2.2~dfsg1-2
has caused the Debian Bug report #884645,
regarding qupzilla-plugin-{gnome-keyring,kwallet}: fails to upgrade from 
'testing' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/qupzilla/lib{GnomeKeyring,KWallet}Passwords.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.)


-- 
884645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qupzilla-plugin-gnome-keyring,qupzilla-plugin-kwallet
Version: 2.2.2~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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package qupzilla-plugin-gnome-keyring.
  Preparing to unpack 
.../193-qupzilla-plugin-gnome-keyring_2.2.2~dfsg1-1_amd64.deb ...
  Unpacking qupzilla-plugin-gnome-keyring (2.2.2~dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-jSbyKA/193-qupzilla-plugin-gnome-keyring_2.2.2~dfsg1-1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qupzilla/libGnomeKeyringPasswords.so', which is also 
in package libqupzilla1 2.2.0~dfsg1-2
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-jSbyKA/193-qupzilla-plugin-gnome-keyring_2.2.2~dfsg1-1_amd64.deb

  Selecting previously unselected package qupzilla-plugin-kwallet.
  Preparing to unpack .../193-qupzilla-plugin-kwallet_2.2.2~dfsg1-1_amd64.deb 
...
  Unpacking qupzilla-plugin-kwallet (2.2.2~dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Azhy0x/193-qupzilla-plugin-kwallet_2.2.2~dfsg1-1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qupzilla/libKWalletPasswords.so', which is also in 
package libqupzilla1 2.2.0~dfsg1-2
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-Azhy0x/193-qupzilla-plugin-kwallet_2.2.2~dfsg1-1_amd64.deb


cheers,

Andreas


libqupzilla1=2.2.0~dfsg1-2_qupzilla-plugin-gnome-keyring=2.2.2~dfsg1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qupzilla
Source-Version: 2.2.2~dfsg1-2

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated qupzilla package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Dec 2017 15:52:27 +0100
Source: qupzilla
Binary: qupzilla libqupzilla1 libqupzilla-dev qupzilla-plugin-kwallet 
qupzilla-plugin-gnome-keyring
Architecture: source amd64
Version: 2.2.2~dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 libqupzilla-dev - development files for qupzilla's shared library
 libqupzilla1 - shared library and header files for qupzilla
 qupzilla   - lightweight web browser based on libqtwebkit
 qupzilla-plugin-gnome-keyring - plugin to store passwords for Qupzilla with 
the Gnome
 qupzilla-plugin-kwallet - plugin to store passwords for Qupzilla with the KDE 
Wallet.
Closes: 834996 863458 870059 873283 884645
Changes:
 qupzilla (2.2.2~dfsg1-2) unstable; urgency=medium
 .
   * added a Breaks+Replace clause. Closes: #884645
   * tried on "some websites", ... when pressing the "Back"- button,
 qupzilla crashes no longer. So ... this Closes: #870059. If someone
 wants to reopen this bug report, please make a precise list of
 "some websites" which trigger this bug, in order to let the maintainer
 reproduce it.
   *

Bug#884720: marked as done (borgbackup: do not run borg 1.1.x check --repair)

Your message dated Mon, 18 Dec 2017 19:04:10 +
with message-id 
and subject line Bug#884720: fixed in borgbackup 1.1.3-3
has caused the Debian Bug report #884720,
regarding borgbackup: do not run borg 1.1.x check --repair
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.)


-- 
884720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: borgbackup
Version: 1.1.3-2
Severity: critical
Tags: upstream
Justification: causes serious data loss

Dear Maintainer,

just in case you missed it, there is a upstream warning about data
loss when using "check --repair" on 1.1.x series:

https://mail.python.org/pipermail/borgbackup/2017q4/000949.html

A suggested fix is pointed as well in the linked mail.

Regards,

Alberto
--- End Message ---
--- Begin Message ---
Source: borgbackup
Source-Version: 1.1.3-3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Dec 2017 19:50:46 +0100
Source: borgbackup
Binary: borgbackup borgbackup-doc
Architecture: source
Version: 1.1.3-3
Distribution: unstable
Urgency: critical
Maintainer: Danny Edel 
Changed-By: Gianfranco Costamagna 
Description:
 borgbackup - deduplicating and compressing backup program
 borgbackup-doc - deduplicating and compressing backup program (documentation)
Closes: 884720
Changes:
 borgbackup (1.1.3-3) unstable; urgency=critical
 .
   * debian/patches/3445.patch:
 - fix data loss with check --repair (Closes: #884720)
   * Bump std-version to 4.1.2, no changes required.
Checksums-Sha1:
 a7be23746aefcbb8d27fe90131c869c8859e14a8 2343 borgbackup_1.1.3-3.dsc
 2f593c73df2ef0bd316780c0c976a34f7adaaf8e 23516 borgbackup_1.1.3-3.debian.tar.xz
 fde80248766ce5ee66086d506aafc673a2f18fb9 9050 
borgbackup_1.1.3-3_source.buildinfo
Checksums-Sha256:
 9f01acb412fc998d386ebfa5f60cbc89ba1b5c73aafa95e4fdcc15cfe375e729 2343 
borgbackup_1.1.3-3.dsc
 416c596565084e0c2d65d930e859a78a9270a401c9c60c26e177dfb2476f3811 23516 
borgbackup_1.1.3-3.debian.tar.xz
 44ceb8f62b12f114fc34d112819a82d5991f832922ab3b745d7650be0d90f5fd 9050 
borgbackup_1.1.3-3_source.buildinfo
Files:
 f069946a685447e77fc2f63372a74cdb 2343 admin optional borgbackup_1.1.3-3.dsc
 469ab190a5aa86a72f7d42d440533feb 23516 admin optional 
borgbackup_1.1.3-3.debian.tar.xz
 d1a94123106de83d8e8be0ad8917237b 9050 admin optional 
borgbackup_1.1.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaOA5lAAoJEPNPCXROn13ZAT4QAKUtWitaUiFNWGxl0bF0482o
5NQqlr+bliPwOZDZqskjGr4ih1OAMkULbUV+EZoauGx1fepcM0gkqczrIgimwYmF
A7qEU7BLrCfRM1J4UdIp8YpMWu9KeGfvdMUTDQlZboWHm+d6fhKHGnfo3GP7sDgq
opPZwO+zTrPE9p0X7898066Xj4j0KSON7SA5d54NQkA8M1DnMxIXwr/g6Ii/vv1K
gQt5yqj4wrlnOglNDoQvu+UY/0V2IKbPT40V/ccS2wqglYKrheDmTaIx/ajbRrPR
SATHJ32eaEmwvHjHd1/aDAFiaXFvwBfSPBXBVaPTuH3AYNawVzX1RneRgsSHdVnl
QtxsQ2sRkQx4GKiKVK00AFHCZZerCf43WU33EVOQu3VamM9SQvpVn9ThVNU8Q0FO
hSFivJyhgWQwZmnkx4QPEDvU0sV8C9SwfhsipWR1UT3VZ9BRyH2RQqgB16xspHwY
AlrVS8MDWPTFMtXhM0aQ5QCnpxNexSzcrIoLg6R63sj4mxVtCLYBQdj7Qfh+eI7K
8ZZsXx9jW9S7hKZ3IvQfNocWlulLV55W46P3KolYuujNxD7kcEvQ2BqYJut/3UFQ
R2GFGl2Nh8y/THRxnTLU6fNaNIj9RukDc8TDAGOd/OfWYD3OoNeuhnHeuBoPQBHX
/hN2BnTYV5DzlEZNR0vz
=3hf1
-END PGP SIGNATURE End Message ---

Bug#884686: marked as done (python-cloudpickle: missing depepdency on the python interpreter)

Your message dated Mon, 18 Dec 2017 19:04:16 +
with message-id 
and subject line Bug#884686: fixed in cloudpickle 0.5.2-2
has caused the Debian Bug report #884686,
regarding python-cloudpickle: missing depepdency on the python interpreter
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.)


-- 
884686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-cloudpickle
Version: 0.5.2-1
Severity: serious

Dear maintainer,

python-cloudpickle is a Python package but lacks any dependency, including
one on the Python interpreter itself.

Most of the times this is due to using the wrong substvar, for instance
using ${python3:Depends} on a python2 package (or the reverse,
${python:Depends on a python3 package).
--- End Message ---
--- Begin Message ---
Source: cloudpickle
Source-Version: 0.5.2-2

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated cloudpickle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Dec 2017 10:32:39 -0800
Source: cloudpickle
Binary: python3-cloudpickle python-cloudpickle
Architecture: source
Version: 0.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Diane Trout 
Description:
 python-cloudpickle - Extended pickling support for Python 2 objects
 python3-cloudpickle - Extended pickling support for Python 3 objects
Closes: 884686
Changes:
 cloudpickle (0.5.2-2) unstable; urgency=medium
 .
   * Forgot to update substvar for the Python 2 package (Closes: #884686)
 - Thanks: Mattia Rizzolo
Checksums-Sha1:
 66ca22a5b64bad8b95396a703e04a5d2d7205525 2306 cloudpickle_0.5.2-2.dsc
 954dc9f52d82ebda5c3fa9979bd08a0eaea3 3292 cloudpickle_0.5.2-2.debian.tar.xz
 486b22e7f67f9074145e7081152c0518d567a6a3 7225 
cloudpickle_0.5.2-2_source.buildinfo
Checksums-Sha256:
 da243beca22a5f55269f9ee7f1f089fc602dcf8e98537fab9b88ab203f864946 2306 
cloudpickle_0.5.2-2.dsc
 ab70aa79646bcb11774bde9a737b489716d14e175028dcb8a53907dcc66fca82 3292 
cloudpickle_0.5.2-2.debian.tar.xz
 aa418e481ee8dc3c46fcdf690cf64043e5e47d88fbeca057103ff290f57188df 7225 
cloudpickle_0.5.2-2_source.buildinfo
Files:
 ede56afdefa7c68030459712876b48ab 2306 python optional cloudpickle_0.5.2-2.dsc
 11caad4952141ef6b28c03541efc1aa3 3292 python optional 
cloudpickle_0.5.2-2.debian.tar.xz
 ebb189a723a8f52e765576bdd87944e8 7225 python optional 
cloudpickle_0.5.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQVcMeSBIEX5AQ11mQ04NnM013AFAlo4DQYACgkQmQ04NnM0
13ADCw/9Hqju8UOZKNh8zhx62qxXR6Hfh24ajDYbVk0VT0ntAuo+3KFEsbiDMBWb
6QVlLdo20hxF7tu0ouJVDPykulU+JOIJo+CqTW4b0fPLrSTCmviNr3iQm8VAXR8g
cWmzDxGmwuSFzYzUbgt2wNlOCItz8qQREMv74VGEGMEbz2H74jva7h52W2sqxlvn
+ZGkdeMiax0eMnbEdmn96TJ2XKvHhyc9rTQyuvqChFrp43QKOySouTPKHua+0NZk
UxiE99ghhWBxH7g4OUwZMHAYlLbdYRC+zGaqPvaAVzcsD3SS6lWcbOUKh1Z7ElwV
ed9gvrQDPkKndslm5di2B9tLnF/4pLkisou0+K8QbGWgJeVmo2FN+4Te2R1loJ8x
G6ywUQVR0RiK4yfLqdPM8Cgd3w1/PvTP7+tgfvEDRkRxqEleLFX5EUJ0Oh7pxMgJ
gSYXzSIIo3TO+DTD4J9RUowQO5suklq9jfkS1mxkNZin4/Pv6+3no3zZDnCRY3xI
NKjBkr6ceAZJvmR0ClIDH+Gk8ym6k+nu8nF9lWXnPvI22MpU2s3HyUPDfcfiqO1S
zogq6xd1N2pCiQp3ybiA/X6+0LIDDIf3sJqWwYABr/S5jZN6cfYznj6a3rOv22XJ
joSz0A2QUoJW0jJG7k9cpGh9W9/LgNmflVkNlH9f31IjQ2x9kHw=
=9iCt
-END PGP SIGNATURE End Message ---

Bug#884686: marked as pending

2017-12-18 Thread Diane Trout

tag 884686 pending
thanks

Hello,

Bug #884686 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/python-modules/packages/cloudpickle.git/commit/?id=89d7adc

---
commit 89d7adca099b5f4599ba6e3f6e713eee4a154426
Author: Diane Trout 
Date:   Mon Dec 18 10:44:23 2017 -0800

Forgot to update substvar for the Python 2 package (Closes: #884686)

  - Thanks: Mattia Rizzolo

diff --git a/debian/changelog b/debian/changelog
index 2581f06..d015f62 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+cloudpickle (0.5.2-2) unstable; urgency=medium
+
+  * Forgot to update substvar for the Python 2 package (Closes: #884686)
+- Thanks: Mattia Rizzolo
+
+ -- Diane Trout   Mon, 18 Dec 2017 10:32:39 -0800
+
 cloudpickle (0.5.2-1) unstable; urgency=medium
 
   * New upstream version. (Closes: #883782)

Processed: Bug#884686 marked as pending

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

> tag 884686 pending
Bug #884686 [python-cloudpickle] python-cloudpickle: missing depepdency on the 
python interpreter
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

2017-12-18 Thread Thomas Patrick Downes

Is there going to be any kind of post-mortem analysis of how this happened? The 
changelogs indicate that this entered oldstable-proposed-updates around 4 
December. I’m not quite sure when it entered oldstable-updates or if it ever 
formally entered oldstable-updates prior to being incorporated into the 8.10 
release on 9 December.

I would not call 5 days an “extended testing period” as promised by the 
proposed-updates mechanism.

https://www.debian.org/releases/proposed-updates.html

It would also be helpful if you clearly stated whether this (a) affects all 
multi-socket systems and (b) whether it affected any single-socket systems. 
Between the sample bias of bug reports themselves and the “fog of war” neither 
conclusion is clear.

Yours,

--
Tom Downes
Senior Scientist
Center for Gravitation, Cosmology and Astrophysics
414.229.2678

Bug#884721: rsyncrypto: Segmentation fault with --delete

2017-12-18 Thread Chris Boot

Package: rsyncrypto
Version: 1.13-1
Severity: serious
Tags: patch upstream
Justification: crash on basic functionality

Dear maintainer,

I have recently been exposed to rsyncrypto through a client of my
work's, and have encountered a crash when using rsyncrypto to refresh an
encrypted directory tree with --delete enabled.

This happens because of an infinite recursion in autofd::unlink():

https://sources.debian.org/src/rsyncrypto/1.13-1/autofd.h/#L217

static int unlink(const char *pathname)
{
bool success=unlink( pathname )==0;
[...]
}

I came up with the following patch which simply calls unlink() in the
top scope. This seems to fix the problem for me:

--- rsyncrypto-1.14.orig/autofd.h
+++ rsyncrypto-1.14/autofd.h
@@ -216,7 +216,7 @@ public:
 // unless it failed with ENOENT - the file already doesn't exist
 static int unlink(const char *pathname)
 {
-bool success=unlink( pathname )==0;
+bool success=::unlink( pathname )==0;
 if( !success && errno!=ENOENT )
 throw rscerror("Erasing file", errno, pathname );
 

This affects 1.13-1 and 1.14-1 in Debian in the same way. Please let me
know if you would like any further information.

Best regards,
Chris

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

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

Versions of packages rsyncrypto depends on:
ii  gzip1.6-5+b1
pn  libargtable2-0  
ii  libc6   2.25-3
ii  libgcc1 1:7.2.0-17
ii  libssl1.1   1.1.0g-2
ii  libstdc++6  7.2.0-17

Versions of packages rsyncrypto recommends:
ii  rsync  3.1.2-2

rsyncrypto suggests no packages.

Processed: Re: Bug#884654: glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed

Processing control commands:

> tags -1 + confirmed
Bug #884654 [src:glib2.0] glib2.0: FTBFS on amd64 buildd: gdbus-peer test: 
assertion 'source->ref_count > 0' failed
Added tag(s) confirmed.

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

Bug#884654: glib2.0: FTBFS on amd64 buildd: gdbus-peer test: assertion 'source->ref_count > 0' failed

Control: tags -1 + confirmed

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote:
> The failure on the buildd is new, although I think I might have seen it
> before in local testing (but never reproducibly). It's probably some
> rarely-hit race condition?

I can reproduce this by running the gdbus-peer test in a loop (this is
with GLib git master, not Debian's GLib, but that's close enough). I'm
not convinced it's RC, but I'll leave it at serious severity for now.

(gdb) thread apply all bt

Thread 7 (Thread 0x7f4576854700 (LWP 19643)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f457aa3cadd in g_cond_wait_until (cond=cond@entry=0x5617ef3f0be8, 
mutex=mutex@entry=0x5617ef3f0be0, end_time=end_time@entry=280830465587) at 
/home/smcv/src/glib/glib/gthread-posix.c:1449
#2  0x7f457a9c9a8e in g_async_queue_pop_intern_unlocked 
(queue=queue@entry=0x5617ef3f0be0, wait=wait@entry=1, end_time=280830465587) at 
/home/smcv/src/glib/glib/gasyncqueue.c:422
#3  0x7f457a9ca119 in g_async_queue_timeout_pop_unlocked 
(queue=0x5617ef3f0be0, timeout=timeout@entry=50) at 
/home/smcv/src/glib/glib/gasyncqueue.c:570
#4  0x7f457aa1ef01 in g_thread_pool_wait_for_new_task 
(pool=pool@entry=0x5617ef4072a0) at /home/smcv/src/glib/glib/gthreadpool.c:262
#5  0x7f457aa1f10b in g_thread_pool_thread_proxy (data=) at 
/home/smcv/src/glib/glib/gthreadpool.c:296
#6  0x7f457aa1e5fd in g_thread_proxy (data=0x5617ef3f8d40) at 
/home/smcv/src/glib/glib/gthread.c:784
#7  0x7f457a51a519 in start_thread (arg=0x7f4576854700) at 
pthread_create.c:456
#8  0x7f45799afa4f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f4578a6a700 (LWP 19641)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f457aa3c9ce in g_cond_wait (cond=cond@entry=0x7f457b8dd2b0 
, mutex=mutex@entry=0x7f457b8dd2c0 ) at 
/home/smcv/src/glib/glib/gthread-posix.c:1402
#2  0x7f457b574975 in g_cancellable_disconnect (cancellable=0x5617ef3fca80, 
handler_id=59) at /home/smcv/src/glib/gio/gcancellable.c:632
#3  0x7f457b5749ae in cancellable_source_finalize (source=0x5617ef407e00) 
at /home/smcv/src/glib/gio/gcancellable.c:675
#4  0x7f457a9f3af9 in g_source_unref_internal 
(source=source@entry=0x5617ef407e00, context=context@entry=0x5617ef3f2000, 
have_lock=have_lock@entry=1) at /home/smcv/src/glib/glib/gmain.c:2119
#5  0x7f457a9f3ef3 in g_child_source_remove_internal 
(child_source=0x5617ef407e00, context=context@entry=0x5617ef3f2000) at 
/home/smcv/src/glib/glib/gmain.c:1510
#6  0x7f457a9f3e5b in g_source_destroy_internal (source=0x5617ef4082f0, 
context=0x5617ef3f2000, have_lock=have_lock@entry=0) at 
/home/smcv/src/glib/glib/gmain.c:1273
#7  0x7f457a9f4e79 in g_source_destroy (source=source@entry=0x5617ef4082f0) 
at /home/smcv/src/glib/glib/gmain.c:1304
#8  0x7f457b5bf1b7 in free_sources (sources=0x0) at 
/home/smcv/src/glib/gio/gsocketlistener.c:616
#9  0x7f457b5c6003 in g_task_finalize (object=0x5617ef3e80e0) at 
/home/smcv/src/glib/gio/gtask.c:641
#10 0x7f457b2ea752 in g_object_unref (_object=_object@entry=0x5617ef3e80e0) 
at /home/smcv/src/glib/gobject/gobject.c:3338
#11 0x7f457b5bf308 in accept_ready (accept_socket=, 
condition=, user_data=0x5617ef3e80e0) at 
/home/smcv/src/glib/gio/gsocketlistener.c:786
#12 0x7f457b5b6bd5 in socket_source_dispatch 
(source=source@entry=0x5617ef4082f0, callback=0x7f457b5bf259 , 
user_data=0x5617ef3e80e0) at /home/smcv/src/glib/gio/gsocket.c:3818
#13 0x7f457a9f459c in g_main_dispatch 
(context=context@entry=0x5617ef3f2000) at /home/smcv/src/glib/glib/gmain.c:3183
#14 0x7f457a9f6de0 in g_main_context_dispatch 
(context=context@entry=0x5617ef3f2000) at /home/smcv/src/glib/glib/gmain.c:3848
#15 0x7f457a9f6f39 in g_main_context_iterate (context=0x5617ef3f2000, 
block=block@entry=1, dispatch=dispatch@entry=1, self=self@entry=0x5617ef3f8b70) 
at /home/smcv/src/glib/glib/gmain.c:3921
#16 0x7f457a9f72d8 in g_main_loop_run (loop=0x5617ef3f0b40) at 
/home/smcv/src/glib/glib/gmain.c:4117
#17 0x5617edf15430 in run_service_loop (service_context=0x5617ef3f2000) at 
/home/smcv/src/glib/gio/tests/gdbus-peer.c:365
#18 0x5617edf16b72 in nonce_tcp_service_thread_func 
(user_data=0x7fff9d4ed060) at /home/smcv/src/glib/gio/tests/gdbus-peer.c:1235
#19 0x7f457aa1e5fd in g_thread_proxy (data=0x5617ef3f8b70) at 
/home/smcv/src/glib/glib/gthread.c:784
#20 0x7f457a51a519 in start_thread (arg=0x7f4578a6a700) at 
pthread_create.c:456
#21 0x7f45799afa4f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 5 (Thread 0x7f4577267700 (LWP 19642)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f457aa3cadd in g_cond_wait_until (cond=cond@entry=0x5617ef3ce578, 
mutex=mutex@entry=0x5617ef3ce570, end_time=end_time@entry=280830465124) at 
/home/smcv/src/glib/glib/gthread-posix.c:1449
#2  0x7f457a9c9a8e in

Processed: bug 884661 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=791744

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

> forwarded 884661 https://bugzilla.gnome.org/show_bug.cgi?id=791744
Bug #884661 [src:glib2.0] glib2.0: sometimes FTBFS on reproducible-builds: 
gmenumodel test: assertion failed (items_changed_count == 1): (0 == 1)
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=791744'.
> thanks
Stopping processing here.

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

Processed: Re: [git] 2.15.x fails to fetch remote repository

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

> # regression but not reproducible
> severity 884038 important
Bug #884038 [git] [git] 2.15.x fails to fetch remote repository
Severity set to 'important' from 'grave'
> tags 884038 + upstream unreproducible
Bug #884038 [git] [git] 2.15.x fails to fetch remote repository
Added tag(s) unreproducible and upstream.
> quit
Stopping processing here.

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

Bug#884038: [git] 2.15.x fails to fetch remote repository

2017-12-18 Thread Jonathan Nieder

# regression but not reproducible
severity 884038 important
tags 884038 + upstream unreproducible
quit

Hi,

mirq-debo...@rere.qmqm.pl wrote:

> git 2.15.x from testing can't properly fetch from remote repository:
>
> $ git fetch --all
> Fetching origin
> remote: Counting objects: 752, done.
> remote: Total 752 (delta 578), reused 578 (delta 578), pack-reused 174
> Receiving objects: 100% (752/752), 244.37 KiB | 1.89 MiB/s, done.
> Resolving deltas: 100% (619/619), completed with 214 local objects.
> fatal: bad object HEAD
> error: https://github.com/torvalds/linux.git did not send all necessary 
> objects
>
> error: Could not fetch origin 
>
> Downgrading to 2.14.2-1~bpo9+1 from stretch-backports fixes the issue.
> Both current 2.15.1-1 and previous 2.15.0-1 in testing are affected.

Very strange.  I can't reproduce this --- any hints about what I am
doing differently from you?

Can you give commands starting with the initial "git clone" I can use to
reproduce this?

If there's no way to reproduce it from scratch, can you tar up your
.git directory and send it to me somehow to allow me to reproduce it?

Thanks,
Jonathan

Bug#859718: Please review patches for ssldump

2017-12-18 Thread Hilko Bengen

* Sebastian Andrzej Siewior:

> [...]
> from the remaining part, nothing stands out.

Thank you for reviewing, After uploading the fixed package, I have also
sent upstream the patches.

Cheers,
-Hilko

Bug#884720: borgbackup: do not run borg 1.1.x check --repair

2017-12-18 Thread Alberto Luaces

Package: borgbackup
Version: 1.1.3-2
Severity: critical
Tags: upstream
Justification: causes serious data loss

Dear Maintainer,

just in case you missed it, there is a upstream warning about data
loss when using "check --repair" on 1.1.x series:

https://mail.python.org/pipermail/borgbackup/2017q4/000949.html

A suggested fix is pointed as well in the linked mail.

Regards,

Alberto

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

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

> #
> # bts-link upstream status pull for source package src:wolfssl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #884235 (http://bugs.debian.org/884235)
> # Bug title: wolfssl: CVE-2017-13099
> #  * https://github.com/wolfSSL/wolfssl/pull/1229
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 884235 + fixed-upstream
Bug #884235 [src:wolfssl] wolfssl: CVE-2017-13099
Added tag(s) fixed-upstream.
> usertags 884235 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

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

> #
> # bts-link upstream status pull for source package src:oolite
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #863788 (http://bugs.debian.org/863788)
> # Bug title: oolite: Please drop dependency against mozjs 1.8.5
> #  * https://github.com/OoliteProject/oolite/issues/271
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 863788 + fixed-upstream
Bug #863788 [src:oolite] oolite: Please drop dependency against mozjs 1.8.5
Added tag(s) fixed-upstream.
> usertags 863788 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 863788 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#883503: prerex: depends on libpoppler-qt4 which is about to be removed

2017-12-18 Thread Ryan Kavanagh

Hi Emilio,

On Mon, Dec 04, 2017 at 06:41:34PM +0100, po...@debian.org wrote:
> prerex should switch to the Qt5 bindings, or disable Poppler support
> if the former is not possible.

I have a patch from upstream porting prerex to Qt5. I'll test it out and upload
it in the next couple of days.

Best wishes,
Ryan

-- 
|_)|_/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
| \| \  https://ryanak.ca/ |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#884031: marked as done (golang-github-hashicorp-serf: FTBFS on most architectures)

Your message dated Mon, 18 Dec 2017 16:19:34 +
with message-id 
and subject line Bug#884031: fixed in golang-github-hashicorp-serf 
0.8.1+git20171021.c20a0b1~ds1-4
has caused the Debian Bug report #884031,
regarding golang-github-hashicorp-serf: FTBFS on most architectures
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.)


-- 
884031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-hashicorp-serf
Version: 0.8.1+git20171021.c20a0b1~ds1-3
Severity: serious

Hi,

the last golang-github-hashicorp-serf upload FTBFS on most
architectures:

https://buildd.debian.org/status/package.php?p=golang-github-hashicorp-serf=unstable

with something that is probably a test failure.


Andreas
--- End Message ---
--- Begin Message ---
Source: golang-github-hashicorp-serf
Source-Version: 0.8.1+git20171021.c20a0b1~ds1-4

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated 
golang-github-hashicorp-serf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Dec 2017 15:58:42 +
Source: golang-github-hashicorp-serf
Binary: serf golang-github-hashicorp-serf-dev
Architecture: source
Version: 0.8.1+git20171021.c20a0b1~ds1-4
Distribution: unstable
Urgency: high
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 golang-github-hashicorp-serf-dev - Service orchestration and management tool 
(source)
 serf   - Service orchestration and management tool
Closes: 884031
Changes:
 golang-github-hashicorp-serf (0.8.1+git20171021.c20a0b1~ds1-4) unstable; 
urgency=high
 .
   * Ignore test failures again, as they are too flakey (upstream bug #496).
 Closes: 884031.
   * Stop using prisine-tar.
Checksums-Sha1:
 b7fc1eddf8e5d7354b4f8987e4662a53bc7d1138 2918 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4.dsc
 170fbb7da91ba3d7205079cb50d4c27e2bdfb316 47912 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4.debian.tar.xz
 8db892f9b856ed91a829ae5e4ae600f5f847a8dc 10440 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4_amd64.buildinfo
Checksums-Sha256:
 68d690aebc7f4277cae3fee982055fda4596a9a41400986867e95e3bf79831c4 2918 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4.dsc
 6969135928941cd4aa1f57f35156d9725eddfd5fd429557c0432bfcb1df8f017 47912 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4.debian.tar.xz
 7f5e58fc5dfd7e273ab4aaca7ac544db8d16519379e9f8b4128973e75ad1afe7 10440 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4_amd64.buildinfo
Files:
 f68be7c55ef090d5087a0025228f9aca 2918 devel optional 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4.dsc
 8f67306e42435afae594d008fa0ea8b1 47912 devel optional 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4.debian.tar.xz
 456ac15cce01ba06e37fd94f91695cb1 10440 devel optional 
golang-github-hashicorp-serf_0.8.1+git20171021.c20a0b1~ds1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlo35hUACgkQXdjgv5Gj
09rkVRAAwjIWwLMprqqdH6eqWXHJAQYtuA2xgl0J6HQw1gNoOU+GRxiU+j5Pt0xm
7dWK43qEd51yHCLT0e17YrBPuQP0A9LnjiXat1GgL3uvWRXKl06CztdwoqOTQoKD
DnQqvXM7H59pdxP8Cr+cz+d96eNASGTaR+x/Sq/1T0RHGYx27fdy4H4HTmPxbgAC
T9dVmUr6z1yyHvWyzW/VLCrbaZNcifcL1qodSve2qYzZDYYnSFrlyE9nC2Y0pick
H4hcL+UKrylWBgTLabwKWM0I/40EgCaPCS/pKAdzJYyJH0ZBcFgKkHY8npQd9ktJ
rSYFyOykEvtlikrRsZfUMsPGmdx4Vmz1rK/QlboEfcsslEXr/Jbje6cr0pWs/aIC
r+yY9QnKl3N9v96Qff+7/BtPFdBqcABX+JQZfRvf7CNWJPQEuSFfjLYjP6lM91yv
AI0g5YjinZTaPnmuP95BYqYP0PN4R4OYFq4Xm8/gzWpjfMCx2rpWNMafAREbNoua
5xMR5e9RZcw0Ue/xR8It9qPrUGT9pf5tXBH3xx/hTIFun/w42i7JLEu1ulEv573l
h0NxmeP3igr+fSmU1c0RTQvXcJLzjYDdbNROVS2rLxVXzdQ/uwoAOy9+cXwUWCIh
bR58rH52j07wOANFu02XlY4Y/AtTVoCqcl+7YIK8hPQ+eLGg4Nw=
=SRWy
-END PGP SIGNATURE

Bug#884706: marked as done (zfs-linux: make distclean deletes commands.cfg, which is not regenerated)

Your message dated Mon, 18 Dec 2017 15:25:26 +
with message-id 
and subject line Bug#884706: fixed in zfs-linux 0.7.4-1
has caused the Debian Bug report #884706,
regarding zfs-linux: make distclean deletes commands.cfg, which is not 
regenerated
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.)


-- 
884706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zfs-linux
Version: 0.7.3-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

zfs-linux fails to build twice in a row. The first build succeeds, the
subsequent 'debian/rules clean' runs 'make distclean' which deletes
tests/zfs-tests/include/commands.cfg, but that file is not regenerated
during the second build:

Making all in include
make[5]: Entering directory '/build/zfs-linux-0.7.3/tests/zfs-tests/include'
make[5]: *** No rule to make target 'commands.cfg', needed by 'all-am'.  Stop.
make[5]: Leaving directory '/build/zfs-linux-0.7.3/tests/zfs-tests/include'
Makefile:544: recipe for target 'all-recursive' failed

The full buildlog from pbuilder --twice is attached.


Andreas


zfs-linux_0.7.3-3_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 0.7.4-1

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated zfs-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: SHA256

Format: 1.8
Date: Mon, 18 Dec 2017 22:48:59 +0800
Source: zfs-linux
Binary: libnvpair1linux libuutil1linux libzfslinux-dev libzfs2linux 
libzpool2linux zfs-dkms zfs-initramfs zfs-dracut zfsutils-linux zfs-zed 
zfs-test zfs-dbg
Architecture: source amd64 all
Version: 0.7.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers 

Changed-By: Aron Xu 
Description:
 libnvpair1linux - Solaris name-value library for Linux
 libuutil1linux - Solaris userland utility library for Linux
 libzfs2linux - OpenZFS filesystem library for Linux
 libzfslinux-dev - OpenZFS filesystem development files for Linux
 libzpool2linux - OpenZFS pool library for Linux
 zfs-dbg- Debugging symbols for OpenZFS userland libraries and tools
 zfs-dkms   - OpenZFS filesystem kernel modules for Linux
 zfs-dracut - OpenZFS root filesystem capabilities for Linux - dracut
 zfs-initramfs - OpenZFS root filesystem capabilities for Linux - initramfs
 zfs-test   - OpenZFS test infrastructure an support scripts
 zfs-zed- OpenZFS Event Daemon
 zfsutils-linux - command-line tools to manage OpenZFS filesystems
Closes: 883832 884287 884706
Changes:
 zfs-linux (0.7.4-1) unstable; urgency=medium
 .
   * New upstream version 0.7.4 (Closes: #884287, #883832)
   * Require debhelper >= 10.2
   * cherry-pick: fix distclean which removes needed files (Closes: #884706)
   * Refresh patches
   * Update stdver to 4.1.2, no change required
   * Install zfs-import.target
Checksums-Sha1:
 67b6d62fc5bbc7c2b1377f57931e9d7b58578fb8 2632 zfs-linux_0.7.4-1.dsc
 f5651949efc4b55e8d34ae3bac8cf95c66aff0f2 6402864 zfs-linux_0.7.4.orig.tar.gz
 29c719c6dcd02d2ae60d69112ab689e361b34f0f 42068 zfs-linux_0.7.4-1.debian.tar.xz
 4042a5949d7966998546014618c9a489eccf898a 45852 
libnvpair1linux_0.7.4-1_amd64.deb
 4e376af877daff643adde3621fb69253951d72f7 48256 libuutil1linux_0.7.4-1_amd64.deb
 107ddbdd0c49d71cdf5a822478ce836324843314 137792 libzfs2linux_0.7.4-1_amd64.deb
 d2970cac6ea27f080dc801121f5e783e3f1dda44 1026032 
libzfslinux-dev_0.7.4-1_amd64.deb
 d81d92ffec56ad8816539293be27ef168b8e28a4 562312 
libzpool2linux_0.7.4-1_amd64.deb
 9416402fc5c5843e8522651046dc3f0362b912be 3723996 zfs-dbg_0.7.4-1_amd64.deb
 08e1690aa005dd643bced7f5560e15a8b571f6a2 1382628 zfs-dkms_0.7.4-1_all.deb
 45f8d3496647d5b1cd66ea108a407f2fba9438b8 21024 zfs-dracut_0.7.4-1_all.deb

Bug#870779: marked as done (pev: Please migrate to openssl1.1 in Buster)

Your message dated Mon, 18 Dec 2017 15:22:43 +
with message-id 
and subject line Bug#870779: fixed in pev 0.80-4
has caused the Debian Bug report #870779,
regarding pev: Please migrate to openssl1.1 in Buster
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.)


-- 
870779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pev
Version: 0.80-3
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian
--- End Message ---
--- Begin Message ---
Source: pev
Source-Version: 0.80-4

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated pev package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Dec 2017 16:02:05 +0100
Source: pev
Binary: pev
Architecture: source
Version: 0.80-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 pev- text-based tool to analyze PE files
Closes: 870779
Changes:
 pev (0.80-4) unstable; urgency=medium
 .
   * QA upload.
   * Migrate to openssl 1.1. (Closes: #870779)
   * Priority optional.
   * R³.
Checksums-Sha1:
 07ae40e894b8cc0cb7f243aee0ebf78a80fd9554 1880 pev_0.80-4.dsc
 ee62107cbd6fdee81c754d3639a4e0a9d34c5f20 4536 pev_0.80-4.debian.tar.xz
 9e7994271b15cf5375b3881db603a95e2fd00202 5345 pev_0.80-4_source.buildinfo
Checksums-Sha256:
 fa4f40a14567b1beebb919eea628f8e9cb538dca321d6ec2316cf54c89fb9dfc 1880 
pev_0.80-4.dsc
 266f23f23b613ddeb312c04fbee2c5142347678a10c0b2ea8e7112b72e394c39 4536 
pev_0.80-4.debian.tar.xz
 7f114a95170356392ca57c1fa05f0ea96b17ffddba6143efddd4e9496eb5a6a3 5345 
pev_0.80-4_source.buildinfo
Files:
 abe848c944b3da358ae0ddc20c56f0b4 1880 utils optional pev_0.80-4.dsc
 482f5cb4d9714f2ff9a6a2d17cb776a2 4536 utils optional pev_0.80-4.debian.tar.xz
 df1fafa9858e8ff1ca3749b096b959c1 5345 utils optional 
pev_0.80-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlo32JoUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH5RsRAAjAVrvE39rs21kCf/ioil/U9tQc+q
i+Fd8XR4P/qAWo0Si5ICpxGtVKnljGhHeGXtrRE5IlJSE8xBe63kaHML1QEQ+AuE
scNMBjRpkCbO0qv4rxOk5F/43ktNJfs2TwwvZACa9NRPScalS6BTHtLNmP6X1SGl
mrbSkKBEQ1NRBkomtyteIJ71CDY6tlFx+5p2GsWcM0q7Zew2sDicFTAtYrdgxRIi
mzMt6MVLP68Xccyp0K9FFddtHjM2uoncJie1NOnzv1xbojX8jgToWGue6vSVd4+7
FQ8ab1VsKc8kJUtwy0qud6hX2Crk/5+44ntrwwoy7Y3gAkUgdYfez6HTh1kt9V+w
kXEsIvp869/NF0TADwgp09kl7dhcsNPQ1BkweeXMibYSrjnrF3CgGbls+lfqK+q/
/+KZU0TFcnI1SyUj9i+sF6TdGEPeQvpfWDtbup5RwutaQbSq0zftNDernW5Yht+R
BLld2lLVrBVRdR/HB/nY+z420FYZ8/fEICLwybo5H5SvkgbtGFi5X4NWxlvB6TUO
PwmQWWgvF3mapBmWF39lc8xALT4B5YHZoK98xRK8npnlvqCi/t1F8ckkLU6K+IS9
sPLbTMwGte80A9QYIq1QiqsbMpJUmNfSMvDTxlbONzWXpyMUMLaBEy+wtIraXOKE
SXfHgWHATCDQqeY=
=6biZ
-END PGP SIGNATURE End Message ---

Bug#880783: webalizer build depends on removed libgd2*-dev provides

2017-12-18 Thread Gianfranco Costamagna

On Sat, 04 Nov 2017 21:52:10 +0200 Adrian Bunk  wrote:
> Source: webalizer
> Version: 2.23.08-2
> Severity: serious
> 
> The following packages have unmet dependencies:
>  builddeps:webalizer : Depends: libgd2-dev but it is not installable
> 
> 
> Please update the build dependency to libgd-dev.
> 
> 

Hello, can you please have a look?

G.



signature.asc
Description: OpenPGP digital signature

Processed: reassign 876499 to src:netbeans,src:libnb-platform18-java, found 876499 in 8.2+dfsg1-1

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

> reassign 876499 src:netbeans,src:libnb-platform18-java
Bug #876499 [src:netbeans] netbeans: FTBFS:  GnomeKeyringLibrary.java:74: 
error: no suitable method found for 
loadLibrary(String,Class,Map)
Bug reassigned from package 'src:netbeans' to 
'src:netbeans,src:libnb-platform18-java'.
No longer marked as found in versions netbeans/8.2+dfsg1-1.
Ignoring request to alter fixed versions of bug #876499 to the same values 
previously set
> found 876499 8.2+dfsg1-1
Bug #876499 [src:netbeans,src:libnb-platform18-java] netbeans: FTBFS:  
GnomeKeyringLibrary.java:74: error: no suitable method found for 
loadLibrary(String,Class,Map)
Marked as found in versions netbeans/8.2+dfsg1-1 and 
libnb-platform18-java/8.2+dfsg1-1.
> thanks
Stopping processing here.

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

Bug#884704: marked as done (libgtksourceviewmm-3.0-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz)

Your message dated Mon, 18 Dec 2017 14:51:50 +
with message-id 
and subject line Bug#884704: fixed in libgtksourceviewmm 3.18.0-3
has caused the Debian Bug report #884704,
regarding libgtksourceviewmm-3.0-doc: fails to upgrade from 'testing' - trying 
to overwrite /usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz
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.)


-- 
884704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtksourceviewmm-3.0-doc
Version: 3.18.0-2
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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libgtksourceviewmm-3.0-doc.
  Preparing to unpack .../87-libgtksourceviewmm-3.0-doc_3.18.0-2_all.deb ...
  Unpacking libgtksourceviewmm-3.0-doc (3.18.0-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Vx1C3w/87-libgtksourceviewmm-3.0-doc_3.18.0-2_all.deb 
(--unpack):
   trying to overwrite '/usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz', 
which is also in package libgtksourceviewmm-3.0-dev:amd64 3.18.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


libgtksourceviewmm-3.0-dev=3.18.0-1_libgtksourceviewmm-3.0-doc=3.18.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libgtksourceviewmm
Source-Version: 3.18.0-3

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated libgtksourceviewmm 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Dec 2017 09:30:35 -0500
Source: libgtksourceviewmm
Binary: libgtksourceviewmm-3.0-0v5 libgtksourceviewmm-3.0-dev 
libgtksourceviewmm-3.0-doc
Architecture: source
Version: 3.18.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 libgtksourceviewmm-3.0-0v5 - C++ binding of GtkSourceView
 libgtksourceviewmm-3.0-dev - C++ binding of GtkSourceView - development files
 libgtksourceviewmm-3.0-doc - C++ binding of GtkSourceView
Closes: 884704
Changes:
 libgtksourceviewmm (3.18.0-3) unstable; urgency=medium
 .
   * Rename debian/libgtksourceviewmm-3.0-doc.docs to debian/docs
 to fix upgrade issue with debhelper compat 11 (Closes: #884704)
Checksums-Sha1:
 2e97e78a9689721bd09309128fe001cdfd1c5a94 2395 libgtksourceviewmm_3.18.0-3.dsc
 26d6218f43e6dcf17a933f572eeb35364f329c3e 5128 
libgtksourceviewmm_3.18.0-3.debian.tar.xz
 76f527583f04db9bcefd9294b3643506c4543193 8344 
libgtksourceviewmm_3.18.0-3_source.buildinfo
Checksums-Sha256:
 b812042f5a919a176de76794ebadbca33b5010fc941208c1cc4ba3aa3dbe095a 2395 
libgtksourceviewmm_3.18.0-3.dsc
 71fc3b6828d89f5afaa8f77dbe465cbc0e8d133238efd22f2a00b7450e004c8c 5128 
libgtksourceviewmm_3.18.0-3.debian.tar.xz
 6843aeb8c69efc344cc470a1ab7c8e26f21d0fb070973ce89e2094a08f2139c4 8344 
libgtksourceviewmm_3.18.0-3_source.buildinfo
Files:
 e4da96b23b4be202b9fc39235acf4710 2395 libs optional 
libgtksourceviewmm_3.18.0-3.dsc
 8a07bc057006d882ffd0cc4ef0226ce9 5128 libs optional 
libgtksourceviewmm_3.18.0-3.debian.tar.xz
 74b1fbadd6fd8116bfe1b966bfbd5dd1 8344 libs optional 
libgtksourceviewmm_3.18.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaN9FFAAoJEOZsd1rr/mx9aXYQAIZ17MOzIQ6hXy/Fdn+nKb/n
nwWDyc8HkbLVHPVltLPh2omhiaCu0TiWfpi77vySez66yByvp5Un9Rdnrnol5wsP
wo/bbfHpaipcmioHF6bC3RtPfIzqMRTZQPwt33ZiR67xOsvlzj/RxXJ5PzxAx0d2

Processed: tagging 884022

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

> tags 884022 + pending
Bug #884022 [src:kcachegrind] kcachegrind: FTBFS with recent Qt5: Could not 
find a package configuration file provided by "Qt5LinguistTools"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#882344: fixed in bpfcc 0.5.0-1

Processing control commands:

> reopen -1
Bug #882344 {Done: Ritesh Raj Sarraf } [src:bpfcc] bpfcc FTBFS 
on !amd64/ppc64el/ppc64: test_usdt_args.cc:63:14: error: 'parser' was not 
declared in this scope
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions bpfcc/0.5.0-1.
> notfixed -1 0.5.0-1
Bug #882344 [src:bpfcc] bpfcc FTBFS on !amd64/ppc64el/ppc64: 
test_usdt_args.cc:63:14: error: 'parser' was not declared in this scope
Ignoring request to alter fixed versions of bug #882344 to the same values 
previously set

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

Bug#884704: marked as pending

2017-12-18 Thread Jeremy Bicha

tag 884704 pending
thanks

Hello,

Bug #884704 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-gnome/gtksourceviewmm.git/commit/?id=144efef

---
commit 144efef51b22146a39d64354894a1a0d85f7fd3a
Author: Jeremy Bicha 
Date:   Mon Dec 18 09:27:56 2017 -0500

Rename debian/libgtksourceviewmm-3.0-doc.docs to debian/docs

to fix upgrade issue with debhelper compat 11

Closes: #884704

diff --git a/debian/changelog b/debian/changelog
index 006fecd..2f054da 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libgtksourceviewmm (3.18.0-3) UNRELEASED; urgency=medium
+
+  * Rename debian/libgtksourceviewmm-3.0-doc.docs to debian/docs
+to fix upgrade issue with debhelper compat 11 (Closes: #884704)
+
+ -- Jeremy Bicha   Mon, 18 Dec 2017 09:26:21 -0500
+
 libgtksourceviewmm (3.18.0-2) unstable; urgency=medium
 
   * Switch from cdbs to dh

Processed: Bug#884704 marked as pending

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

> tag 884704 pending
Bug #884704 [libgtksourceviewmm-3.0-doc] libgtksourceviewmm-3.0-doc: fails to 
upgrade from 'testing' - trying to overwrite 
/usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882344: fixed in bpfcc 0.5.0-1

2017-12-18 Thread Gianfranco Costamagna

control: reopen -1
control: notfixed -1 0.5.0-1

the regex seems wrong, only amd64 is picked up

G.



signature.asc
Description: OpenPGP digital signature

Bug#884710: ants: FTBFS: URL using bad/illegal format or missing URL

Source: ants
Version: 2.2.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

ants/experimental recently started to FTBFS:

[  0%] Generating 
/build/ants-2.2.0/obj-i686-linux-gnu/ExternalData/TestData/Data/r64slice.nii.gz
[  1%] Generating 
/build/ants-2.2.0/obj-i686-linux-gnu/ExternalData/TestData/Data/Frown.nii
cd /build/ants-2.2.0/obj-i686-linux-gnu/Examples/TestSuite && /usr/bin/cmake 
-Drelative_top=/build/ants-2.2.0/obj-i686-linux-gnu 
-Dfile=/build/ants-2.2.0/obj-i686-linux-gnu/ExternalData/TestData/Data/r64slice.nii.
gz -Dname=/build/ants-2.2.0/TestData/Data/r64slice.nii.gz -Dext=.md5 
-DExternalData_ACTION=fetch 
-DExternalData_CONFIG=/build/ants-2.2.0/obj-i686-linux-gnu/Examples/TestSuite/ANTSFetchData_config.cmake
 -P /build/a
nts-2.2.0/CMake/ExternalData.cmake
cd /build/ants-2.2.0/obj-i686-linux-gnu/Examples/TestSuite && /usr/bin/cmake 
-Drelative_top=/build/ants-2.2.0/obj-i686-linux-gnu 
-Dfile=/build/ants-2.2.0/obj-i686-linux-gnu/ExternalData/TestData/Data/Frown.nii
 -Dn
ame=/build/ants-2.2.0/TestData/Data/Frown.nii -Dext=.md5 
-DExternalData_ACTION=fetch 
-DExternalData_CONFIG=/build/ants-2.2.0/obj-i686-linux-gnu/Examples/TestSuite/ANTSFetchData_config.cmake
 -P /build/ants-2.2.0/CM
ake/ExternalData.cmake
-- Fetching 
"file:build/ants-2.2.0/debian/testdata/MD5/37aaa33029410941bf4a0479fa18"
CMake Error at /build/ants-2.2.0/CMake/ExternalData.cmake:743 (message):
  Object MD5=37aaa33029410941bf4a0479fa18 not found at:


file:build/ants-2.2.0/debian/testdata/MD5/37aaa33029410941bf4a0479fa18 
("URL using bad/illegal format or missing URL")
Call Stack (most recent call first):
  /build/ants-2.2.0/CMake/ExternalData.cmake:765 (_ExternalData_download_object)


Examples/TestSuite/CMakeFiles/ANTSFetchData.dir/build.make:70: recipe for 
target 'ExternalData/TestData/Data/r16slice.nii.gz.md5-stamp' failed
make[4]: *** [ExternalData/TestData/Data/r16slice.nii.gz.md5-stamp] Error 1


The four slashes after file: look suspicious.
I also tried a non-parallel build which resulted in the same failure.


Andreas


ants_2.2.0-1.log.gz
Description: application/gzip

Bug#884706: zfs-linux: make distclean deletes commands.cfg, which is not regenerated

2017-12-18 Thread Fabian Grünbichler

On Mon, Dec 18, 2017 at 02:49:48PM +0100, Andreas Beckmann wrote:
> Source: zfs-linux
> Version: 0.7.3-3
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Hi,
> 
> zfs-linux fails to build twice in a row. The first build succeeds, the
> subsequent 'debian/rules clean' runs 'make distclean' which deletes
> tests/zfs-tests/include/commands.cfg, but that file is not regenerated
> during the second build:
> 
> Making all in include
> make[5]: Entering directory '/build/zfs-linux-0.7.3/tests/zfs-tests/include'
> make[5]: *** No rule to make target 'commands.cfg', needed by 'all-am'.  Stop.
> make[5]: Leaving directory '/build/zfs-linux-0.7.3/tests/zfs-tests/include'
> Makefile:544: recipe for target 'all-recursive' failed
> 
> The full buildlog from pbuilder --twice is attached.
> 
> 
> Andreas

fixed upstream in b1490dd43e3c98649c7d23928d908f5bb019411b , which
applies cleanly on top of 0.7.4 (but upstream should probably be poked
to include it in 0.7.5)

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

2017-12-18 Thread Jim Cobley

Thank you. The update has just been applied and my systems are now up 
and running again with no UUID error.

Processed: affects

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

> affects #883987 libboost-dev
Bug #883987 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884184 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884185 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Added indication that 883987 affects libboost-dev
Added indication that 884184 affects libboost-dev
Added indication that 884185 affects libboost-dev
> --
Stopping processing here.

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

Bug#884706: zfs-linux: make distclean deletes commands.cfg, which is not regenerated

Source: zfs-linux
Version: 0.7.3-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

zfs-linux fails to build twice in a row. The first build succeeds, the
subsequent 'debian/rules clean' runs 'make distclean' which deletes
tests/zfs-tests/include/commands.cfg, but that file is not regenerated
during the second build:

Making all in include
make[5]: Entering directory '/build/zfs-linux-0.7.3/tests/zfs-tests/include'
make[5]: *** No rule to make target 'commands.cfg', needed by 'all-am'.  Stop.
make[5]: Leaving directory '/build/zfs-linux-0.7.3/tests/zfs-tests/include'
Makefile:544: recipe for target 'all-recursive' failed

The full buildlog from pbuilder --twice is attached.


Andreas


zfs-linux_0.7.3-3_twice.log.gz
Description: application/gzip

Bug#884704: libgtksourceviewmm-3.0-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz

Package: libgtksourceviewmm-3.0-doc
Version: 3.18.0-2
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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libgtksourceviewmm-3.0-doc.
  Preparing to unpack .../87-libgtksourceviewmm-3.0-doc_3.18.0-2_all.deb ...
  Unpacking libgtksourceviewmm-3.0-doc (3.18.0-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Vx1C3w/87-libgtksourceviewmm-3.0-doc_3.18.0-2_all.deb 
(--unpack):
   trying to overwrite '/usr/share/doc/libgtksourceviewmm-3.0-dev/NEWS.gz', 
which is also in package libgtksourceviewmm-3.0-dev:amd64 3.18.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


libgtksourceviewmm-3.0-dev=3.18.0-1_libgtksourceviewmm-3.0-doc=3.18.0-2.log.gz
Description: application/gzip

Bug#884703: osmo-ggsn: fails to upgrade from 'sid' - trying to overwrite /usr/bin/sgsnemu

Package: osmo-ggsn
Version: 1.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package osmo-ggsn.
  Preparing to unpack .../8-osmo-ggsn_1.1.0-1_amd64.deb ...
  Unpacking osmo-ggsn (1.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IS2ifk/8-osmo-ggsn_1.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/sgsnemu', which is also in package openggsn 
0.92-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-IS2ifk/8-osmo-ggsn_1.1.0-1_amd64.deb


cheers,

Andreas


openggsn=0.92-2_osmo-ggsn=1.1.0-1.log.gz
Description: application/gzip

Bug#883938:

2017-12-18 Thread technik

Hi,
we also had this bug and the downgrade saved our lifes.!
We also can see that the new package ist available - but is it fixed there?
best regards
Andreas

Bug#884660: marked as pending

tag 884660 pending
thanks

Hello,

Bug #884660 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-gnome/glib.git/commit/?id=e313c6d

---
commit e313c6d607dbf3c3db37616bf6baeb0d28597365
Author: Simon McVittie 
Date:   Mon Dec 18 11:21:42 2017 +

Allow even longer for the gdbus-threading test, and re-enable it on 32-bit 
ARM now that the timeout is longer (Closes: #884660)

diff --git a/debian/changelog b/debian/changelog
index e0c9958..29a66bf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,6 +5,10 @@ glib2.0 (2.54.2-3) UNRELEASED; urgency=medium
   * d/patches: Re-export with gbp pq
   * d/patches: Use `gbp pq export`-style metadata, retrieving authors
 and dates from d/changelog where needed
+  * d/p/gdbus-threading-test-Allow-even-longer-for-test_method_ca.patch:
+New patch. Allow even longer for the gdbus-threading test, and
+re-enable it on 32-bit ARM now that the timeout is longer
+(Closes: #884660)
 
  -- Simon McVittie   Mon, 18 Dec 2017 10:47:35 +

Processed: Bug#884660 marked as pending

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

> tag 884660 pending
Bug #884660 [src:glib2.0] glib2.0: sometimes FTBFS on reproducible-builds: 
gdbus-threading test: assertion failed (elapsed_msec < 8000): (8220 < 8000)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#884415: marked as done (prelude-lml,prelude-lml-rules: file conflict on /etc/prelude-lml/ruleset/apc-emu.rules)

Your message dated Mon, 18 Dec 2017 12:49:06 +
with message-id 
and subject line Bug#884415: fixed in prelude-lml 3.1.0-2
has caused the Debian Bug report #884415,
regarding prelude-lml,prelude-lml-rules: file conflict on 
/etc/prelude-lml/ruleset/apc-emu.rules
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.)


-- 
884415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prelude-lml,prelude-lml-rules
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package prelude-lml-rules.
  Preparing to unpack .../prelude-lml-rules_3.1.0-1_amd64.deb ...
  Unpacking prelude-lml-rules (3.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/prelude-lml-rules_3.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/etc/prelude-lml/ruleset/apc-emu.rules', which is also 
in package prelude-lml 3.1.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/prelude-lml-rules_3.1.0-1_amd64.deb


cheers,

Andreas


prelude-lml=3.1.0-1_prelude-lml-rules=3.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: prelude-lml
Source-Version: 3.1.0-2

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

Debian distribution maintenance software
pp.
Thomas Andrejak  (supplier of updated prelude-lml 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Dec 2017 21:15:47 +0100
Source: prelude-lml
Binary: prelude-lml
Architecture: source
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Pierre Chifflier 
Changed-By: Thomas Andrejak 
Description:
 prelude-lml - Security Information Management System [ Log Agent ]
Closes: 884415
Changes:
 prelude-lml (3.1.0-2) unstable; urgency=medium
 .
   * Push to unstable
   * Bump Standards-Version to 4.1.2, no changes needed
   * Remove rulesets since they are now in prelude-lml-rules
 package (Closes: #884415)
Checksums-Sha1:
 e48248e5ac11ebaa676cda9569d223c01f34d01b 2265 prelude-lml_3.1.0-2.dsc
 75a4e401795d340ea4e1c46d55d730d511c0ee3b 8256 prelude-lml_3.1.0-2.debian.tar.xz
 e02adedec41044d72ba008474d046f43dcd9e367 6645 
prelude-lml_3.1.0-2_amd64.buildinfo
Checksums-Sha256:
 d863de256e9bfe099a55e22790fa1cf927ee902548ab33ecdd4c0940890ff9ae 2265 
prelude-lml_3.1.0-2.dsc
 edb42861118b91cd76d1beebb2c26fc9e2fd8889e8d6a542b9ed575938244d13 8256 
prelude-lml_3.1.0-2.debian.tar.xz
 56c943be9067b808deaf31952ed2bc65af183d8f8bb7c7b8c4c8013b26188896 6645 
prelude-lml_3.1.0-2_amd64.buildinfo
Files:
 7913dcdd843a017562068a91d44a9b7c 2265 admin optional prelude-lml_3.1.0-2.dsc
 a19602c8f52d3c71fe729dc64bcc656f 8256 admin optional 
prelude-lml_3.1.0-2.debian.tar.xz
 1ba0d74656f5147f39c1c7a89abb4ce7 6645 admin optional 
prelude-lml_3.1.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlo3s70ACgkQCBa54Yx2
K60tow//Z8Xs+2/siy4WubB2roEtZuNsbFz8kjuZW4oPKPdNaStvzHhZ3TpqvgG7
1lcDBFYJYiBjFmbP8HvgkfkNXlyQQ6Im+OJBg7NEID6KqPI/9MZM7a5fqDisjfiw
bXn7f1p9dad+opLlLAGVJ9pMcUQtpms4CMatL/4gPyMy1a0thKqH7Y93hN+WOINa
DQvfvxAv49WrRYd6BmBbanSLKmZZI1LV4lNLG3pCc/gXyVL4wss+Jxhx6YTz4Q4R
5VW3GNa0eCTT0EnuJ0MKr7hPqu3dVEaFs0N2WIR02LSuPSL05/4Qoc7sLLAuZkVh
/ZiHvS0NmvYLm+45JvHi57XYBkqao9pNjcP3MRsyW3fIcwL1z9tYXrEFUV3i9OTT
ChH7VhTwmK7NB/Q5ZCWpXwe+/G2ust2QS1C33Eh9nctgAt7KGUyTLJG5CrqTPa6t
M/alzzc1oX0EanB2shTAwSWPMa63HHF9dPggjttzrlNgr8YWEK2eq+RpNSm2C5Vc

Bug#884415: marked as done (prelude-lml,prelude-lml-rules: file conflict on /etc/prelude-lml/ruleset/apc-emu.rules)

Your message dated Mon, 18 Dec 2017 12:49:13 +
with message-id 
and subject line Bug#884415: fixed in prelude-lml-rules 3.1.0-2
has caused the Debian Bug report #884415,
regarding prelude-lml,prelude-lml-rules: file conflict on 
/etc/prelude-lml/ruleset/apc-emu.rules
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.)


-- 
884415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prelude-lml,prelude-lml-rules
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
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/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package prelude-lml-rules.
  Preparing to unpack .../prelude-lml-rules_3.1.0-1_amd64.deb ...
  Unpacking prelude-lml-rules (3.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/prelude-lml-rules_3.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/etc/prelude-lml/ruleset/apc-emu.rules', which is also 
in package prelude-lml 3.1.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/prelude-lml-rules_3.1.0-1_amd64.deb


cheers,

Andreas


prelude-lml=3.1.0-1_prelude-lml-rules=3.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: prelude-lml-rules
Source-Version: 3.1.0-2

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

Debian distribution maintenance software
pp.
Thomas Andrejak  (supplier of updated 
prelude-lml-rules package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Dec 2017 21:15:47 +0100
Source: prelude-lml-rules
Binary: prelude-lml-rules
Architecture: source
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Thomas Andrejak 
Changed-By: Thomas Andrejak 
Description:
 prelude-lml-rules - Rules for Prelude LML [ Rules ]
Closes: 884415
Changes:
 prelude-lml-rules (3.1.0-2) unstable; urgency=medium
 .
   * Push to unstable
   * d/control: Fix wrong version in Breaks + Replaces against
 prelude-lml (Closes: #884415)
   * Bump Standards-Version to 4.1.2, no changes needed
Checksums-Sha1:
 26371553c7d5c9c34274f81aef6c75c5f6c96c69  prelude-lml-rules_3.1.0-2.dsc
 2fe1a21f703aa887b270ebe349fddca0bb61ac7f 3612 
prelude-lml-rules_3.1.0-2.debian.tar.xz
 f7d71ce8137c31ca2799d947b630e371eceb9cb7 5406 
prelude-lml-rules_3.1.0-2_amd64.buildinfo
Checksums-Sha256:
 9ee5a4aff98b9b201db0a7dab56a19e16b01eb68efbbbf5908ee62eb3d68b0c2  
prelude-lml-rules_3.1.0-2.dsc
 2054cee5884ad392cf965b9127ac9553cf3d18c1a53d4630ab55f1689d4a0f7b 3612 
prelude-lml-rules_3.1.0-2.debian.tar.xz
 ed2af09d17accfada0373e19a983a4bc6dd3f964810f9fa481abcf36922e9b8e 5406 
prelude-lml-rules_3.1.0-2_amd64.buildinfo
Files:
 4b3e22df9252db3a4674d0377e1774aa  admin optional 
prelude-lml-rules_3.1.0-2.dsc
 74e83d5c571dacd1af6605687cc65fb9 3612 admin optional 
prelude-lml-rules_3.1.0-2.debian.tar.xz
 42d1d73302f34e95f3366b909a743227 5406 admin optional 
prelude-lml-rules_3.1.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlo3s8QACgkQCBa54Yx2
K63nlRAAgRE2TTm6jYLT/J4gFs6DLePtIusKLkjRKWRmYBXtat2jQCjEvRtO57RL
1pB2xnJ5LELDP/KHYn5lYLRby0ZJAcWuLRTqMX9Z/hZOTQjnV2k55cxlPyZEbE4/
JHBp+4trVU9S8/jOIAh/IsaFakbpjusF6X9WBRH2miC7nsc049P9U4En54zHdAZX
Rj8S4p/Ros7vuJxSn4cluE0aaTbaFhJYys1ejdqgAcVc/9gTfpRwN2Fn0pOH3Oq5
LSI0lS3WZgy/84E1UyKKWJb4Aq2lT8wF/GiveBaw+ukFeF2esBsEkcHo2gF8zmqT
rRkGgOTbhO1k0jgPeRc2zbDUqGXRu1GKEt2PqZHgA5Bc0TVibcVEUL4bqmbmu8ui

Bug#884689: marked as done (python3-pyaes: missing depepdency on the python interpreter)

Your message dated Mon, 18 Dec 2017 12:34:56 +
with message-id 
and subject line Bug#884689: fixed in pyaes 1.6.0-2
has caused the Debian Bug report #884689,
regarding python3-pyaes: missing depepdency on the python interpreter
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.)


-- 
884689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyaes
Version: 1.6.0-1
Severity: serious

Dear maintainer,

python3-pyaes is a Python package but lacks any dependency, including
one on the Python interpreter itself.

Most of the times this is due to using the wrong substvar, for instance
using ${python3:Depends} on a python2 package (or the reverse,
${python:Depends on a python3 package).
--- End Message ---
--- Begin Message ---
Source: pyaes
Source-Version: 1.6.0-2

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

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated pyaes package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Dec 2017 14:11:08 +0200
Source: pyaes
Binary: python-pyaes python3-pyaes pypy-pyaes
Architecture: source
Version: 1.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Tristan Seligmann 
Description:
 pypy-pyaes - Pure-Python implementation of the AES cipher (PyPy)
 python-pyaes - Pure-Python implementation of the AES cipher (Python 2)
 python3-pyaes - Pure-Python implementation of the AES cipher (Python 3)
Closes: 884689
Changes:
 pyaes (1.6.0-2) unstable; urgency=medium
 .
   * Fix substvar use (closes: #884689).
   * Bump Standards-Version to 4.1.2 (no changes).
   * Add autopkgtest tests.
Checksums-Sha1:
 8773fad5732542a9751b222fc31c6871619d34e0 1974 pyaes_1.6.0-2.dsc
 0f0c9cb594651ddcc6a035a06221cf866e530ed5 2244 pyaes_1.6.0-2.debian.tar.xz
 60f088d0ad75653a9e3d129fd576b15976213dca 6371 pyaes_1.6.0-2_source.buildinfo
Checksums-Sha256:
 f0e14976484da609df1abc6d514540d036a3d7b691020031c88edf5ea11680fb 1974 
pyaes_1.6.0-2.dsc
 e3e607ae373caa571f3f1ae13462d0bb32b51e4025ac2d007127e2db094012fb 2244 
pyaes_1.6.0-2.debian.tar.xz
 6f265621b3aec33b441b688904b90bfc85fe2b1d613be82bac65829f65d04bc9 6371 
pyaes_1.6.0-2_source.buildinfo
Files:
 f9d6a46350331d32c6d50adb9eeef550 1974 python optional pyaes_1.6.0-2.dsc
 4c38913dacc4ede4dac608786d61 2244 python optional 
pyaes_1.6.0-2.debian.tar.xz
 aef612271d8ee3d81f9ee2cbfd5ca113 6371 python optional 
pyaes_1.6.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQGpBAEBCgCTFiEEXAZWhXVRbQoz/6ejwImQ+x9jeJMFAlo3tCZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDVD
MDY1Njg1NzU1MTZEMEEzM0ZGQTdBM0MwODk5MEZCMUY2Mzc4OTMVHG1pdGhyYW5k
aUBkZWJpYW4ub3JnAAoJEMCJkPsfY3iTEicH/jqWD1kQztBIpMZuuTqQhmjTzvmx
AGGVLQzTf9WktxqZxUPF9sDVhVOFciyIz/LdOOEyD2zAZi6b5iRECjHtxzhfixFu
VbeNny7Fh+8GDRGQd47Q3sq+xa24hQa5sejPnTqxjfldcesnog4WeOdRZKxZmPxa
BucmRoXDRCSj/t8AUGIMVPm4yUHu2sraSiZGSCWDuUL8qYuiPtNnSTsbRqDy3vDv
X0berB4Arl0ny4gTpOVefnvN4xP2WtAZvk3u01zr6adcTKfMv/xpolQyrmQ1EHjM
uLkVEz/if1lcWpKTNslRylx3asltLlSB0luyuhnO4ESrR3AF/goHcMRpLUw=
=6HBz
-END PGP SIGNATURE End Message ---

Processed: Bug#884689 marked as pending

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

> tag 884689 pending
Bug #884689 [python3-pyaes] python3-pyaes: missing depepdency on the python 
interpreter
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#884689: marked as pending

2017-12-18 Thread Tristan Seligmann

tag 884689 pending
thanks

Hello,

Bug #884689 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/python-modules/packages/pyaes.git/commit/?id=61b4d0e

---
commit 61b4d0eb7bbe95e3e1299a9a136efcb6f0b3e59c
Author: Tristan Seligmann 
Date:   Mon Dec 18 14:11:10 2017 +0200

Fix substvar use (closes: #884689).

diff --git a/debian/changelog b/debian/changelog
index 8259b77..86cc911 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pyaes (1.6.0-2) unstable; urgency=medium
+
+  * Fix substvar use (closes: #884689).
+
+ -- Tristan Seligmann   Mon, 18 Dec 2017 14:11:08 +0200
+
 pyaes (1.6.0-1) unstable; urgency=low
 
   * Initial release (closes: #870091).

Bug#872246: marked as done (rdkit: FTBFS with Sphinx 1.6: Needs build-dep on latexmk)

Your message dated Mon, 18 Dec 2017 12:04:17 +
with message-id 
and subject line Bug#872246: fixed in rdkit 201603.5+dfsg-1
has caused the Debian Bug report #872246,
regarding rdkit: FTBFS with Sphinx 1.6: Needs build-dep on latexmk
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.)


-- 
872246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rdkit
Version: 201603.5-2
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.6

Dear maintainer,

rdkit fails to build with Sphinx 1.6, currently available in experimental:

  make -C _build/latex all-pdf
  make[3]: Entering directory '/<>/Docs/Book/_build/latex'
  latexmk -pdf -dvi- -ps-  'RDKit.tex'
  make[3]: latexmk: Command not found
  Makefile:33: recipe for target 'RDKit.pdf' failed
  make[3]: *** [RDKit.pdf] Error 127

Since Sphinx 1.6, latexmk is required to build the LaTeX documentation [1].
Adding a build-dependency on latexmk should help.

[1]: https://github.com/sphinx-doc/sphinx/pull/3082

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rdkit
Source-Version: 201603.5+dfsg-1

We believe that the bug you reported is fixed in the latest version of
rdkit, 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.
Andreas Tille  (supplier of updated rdkit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Dec 2017 12:09:00 +0100
Source: rdkit
Binary: python-rdkit rdkit-doc rdkit-data librdkit1 librdkit-dev
Architecture: source
Version: 201603.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Andreas Tille 
Description:
 librdkit-dev - Collection of cheminformatics and machine-learning software 
(deve
 librdkit1  - Collection of cheminformatics and machine-learning software (shar
 python-rdkit - Collection of cheminformatics and machine-learning software
 rdkit-data - Collection of cheminformatics and machine-learning software (data
 rdkit-doc  - Collection of cheminformatics and machine-learning software (docu
Closes: 872246
Changes:
 rdkit (201603.5+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * Moved packaging from SVN to Git
   * DEP5
   * Repack tarball to exclude *.chm file
   * Build-Depends: latexmk
 Closes: #872246
   * Standards-Version: 4.1.2
Checksums-Sha1:
 68898fb419e2ec071bc0690d3a54fa0cdc323ad0 2560 rdkit_201603.5+dfsg-1.dsc
 4ff448119e3f47c1e7de57301d3e641eac270d6b 22667368 
rdkit_201603.5+dfsg.orig.tar.xz
 9cee982261d388a9dd3156d0aba951c78d0234f2 7932 
rdkit_201603.5+dfsg-1.debian.tar.xz
 e67b80c87d10e23215e36ddeb005cbc55bebc0dd 17561 
rdkit_201603.5+dfsg-1_source.buildinfo
Checksums-Sha256:
 8f744af4df7e5a0c3c6451038a5c454fa381a991e4bb5a8fb1bcf1a102473c2e 2560 
rdkit_201603.5+dfsg-1.dsc
 698d6dd6be27c87923c1c77a3bc491c58ee98832c3cf07f576c87c5fbfb58b1c 22667368 
rdkit_201603.5+dfsg.orig.tar.xz
 0dbe74d6c058a76b24251118ecb2daa4a62b34f7015a9fbff199c15f5f5687e1 7932 
rdkit_201603.5+dfsg-1.debian.tar.xz
 6ae2efb0948142f91b2a419a476043df3b95090f1a6ff823d0cd3c1aba726672 17561 
rdkit_201603.5+dfsg-1_source.buildinfo
Files:
 580be0c804a37f54420f3e6697f97d2b 2560 science optional 
rdkit_201603.5+dfsg-1.dsc
 f3354c55ab4db2d1c2775d980c5eda71 22667368 science optional 
rdkit_201603.5+dfsg.orig.tar.xz
 dde31ea3a86ce934213d44d2c6bf0f14 7932 science optional 
rdkit_201603.5+dfsg-1.debian.tar.xz
 08a19f99c5ea02bdc6eb9fc5ee7d5197 17561 science optional 
rdkit_201603.5+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlo3qfkOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtEppg/+MCTZHvkLyg5Ao66lpiJVmICGJqsSazuiG9mS
zwU57N9WyvmtrcOBnF9kh2rwJ/VtG4AjEsz/ppooutNyyJHCzO3SHgzaTslLFovt
/Sqkk3mqBiwWzyk3CSIkq1xqQdZUM5GvmMdfcenxH72SPBORuwp02zzvQmgZZImG
Kvew4M2OZlXvfBZMjrSSYyC1I9wTE6SNiGRHbvQWaBwkq+d/+rPH2Y5xQhHuII9O

Bug#853594: openmama: ftbfs with GCC-7

2017-12-18 Thread Juhani Numminen

Control: tags -1 + patch

Juhani Numminen kirjoitti 05.12.2017 klo 12:54:
> https://github.com/OpenMAMA/OpenMAMA/commit/46345f6d78

I put that into the attached patch.

--
Juhani
Description: Fixes FTBFS with GCC-7.
 Cherry-picked from upstream:
 LLVM 5.1 Fixes - pointer dereference
 .
 XCode 5.1 update includes LLVM 5.1 (CLang 3.4) which now fires a number of build
 errors.
 .
 Number of files dealing with partid on multi participant feeds do not dereference
 the pointer to the last dot char, before comparing to the null terminating
 character.  Compiler throws an error comparison of pointer against int.
Author: Phil Preston 
Origin: https://github.com/OpenMAMA/OpenMAMA/commit/46345f6d78f4de43137c4ed00da3d6501529b292
Bug-Debian: https://bugs.debian.org/853594
Last-Update: 2017-12-18

--- a/mamda/c_cpp/src/cpp/MamdaMultiParticipantManager.cpp
+++ b/mamda/c_cpp/src/cpp/MamdaMultiParticipantManager.cpp
@@ -367,7 +367,7 @@
 
 if (lastDot)
 {
-if (lastDot+1 != '\0')
+if (lastDot[1] != '\0')
 partId = lastDot +1;
 }
 
--- a/mamda/c_cpp/src/cpp/MamdaUtils.cpp
+++ b/mamda/c_cpp/src/cpp/MamdaUtils.cpp
@@ -62,7 +62,7 @@
 
 if (lastDot!= NULL)
 {
-if (lastDot+1 != '\0')
+if (lastDot[1] != '\0')
 {
 partId = lastDot+1;
 }
--- a/mamda/c_cpp/src/cpp/orderbooks/MamdaBookAtomicListener.cpp
+++ b/mamda/c_cpp/src/cpp/orderbooks/MamdaBookAtomicListener.cpp
@@ -534,7 +534,7 @@
 const char* lastDot = strrchr (symbol, '.');
 if (lastDot!= NULL)
 {
-if (lastDot+1 != '\0')
+if (lastDot[1] != '\0')
 {
 partId = lastDot+1;
 mPartId = partId;

Processed: Re: openmama: ftbfs with GCC-7

Processing control commands:

> tags -1 + patch
Bug #853594 [src:openmama] openmama: ftbfs with GCC-7
Added tag(s) patch.

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

Bug#884690: ImportError with astroid 1.5

Package: python-astroid
Version: 1.5.3-2
Severity: serious
Tags: sid buster

Installing python-astroid and running

$ python -c 'from astroid.node_classes import as_string'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/astroid/__init__.py", line 57, in 

from astroid.nodes import *
  File "/usr/lib/python2.7/dist-packages/astroid/nodes.py", line 30, in 
from astroid.node_classes import (
  File "/usr/lib/python2.7/dist-packages/astroid/node_classes.py", line 24, in

from astroid import bases
  File "/usr/lib/python2.7/dist-packages/astroid/bases.py", line 25, in 
MANAGER = manager.AstroidManager()
  File "/usr/lib/python2.7/dist-packages/astroid/util.py", line 24, in 
lambda: importlib.import_module('.' + module_name, 'astroid'))
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/usr/lib/python2.7/dist-packages/astroid/manager.py", line 21, in 

from astroid.interpreter._import import spec
  File "/usr/lib/python2.7/dist-packages/astroid/interpreter/_import/spec.py",
line 19, in 
from backports.functools_lru_cache import lru_cache
ImportError: No module named backports.functools_lru_cache

same issue in the autopkg test
https://ci.debian.net/data/packages/unstable/amd64/a/astroid/latest-autopkgtest/log.gz

this also breaks the python-requirements-detector test in a different way:

 
https://ci.debian.net/data/packages/unstable/amd64/p/python-requirements-detector/latest-autopkgtest/log.gz

ERROR: Failure: ImportError (cannot import name as_string)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File
"/tmp/autopkgtest-lxc._jq3zaeb/downtmp/build.7Qp/src/tests/test_parsing.py",
line 9, in 
from requirements_detector.requirement import DetectedRequirement,
_parse_egg_name, _strip_fragment
  File
"/tmp/autopkgtest-lxc._jq3zaeb/downtmp/build.7Qp/src/requirements_detector/__init__.py",
line 1, in 
from requirements_detector.detect import find_requirements
  File
"/tmp/autopkgtest-lxc._jq3zaeb/downtmp/build.7Qp/src/requirements_detector/detect.py",
line 4, in 
from astroid.builder import AstroidBuilder
  File "/usr/lib/python2.7/dist-packages/astroid/__init__.py", line 57, in 

from astroid.nodes import *
  File "/usr/lib/python2.7/dist-packages/astroid/nodes.py", line 30, in 
from astroid.node_classes import (
  File "/usr/lib/python2.7/dist-packages/astroid/node_classes.py", line 23, in

from astroid import as_string
ImportError: cannot import name as_string

Bug#884687: python-backports-shutil-get-terminal-size: missing depepdency on the python interpreter

Package: python-backports-shutil-get-terminal-size
Version: 1.0.0-3
Severity: serious

Dear maintainer,

python-backports-shutil-get-terminal-size is a Python package but lacks any 
dependency, including
one on the Python interpreter itself.

Most of the times this is due to using the wrong substvar, for instance
using ${python3:Depends} on a python2 package (or the reverse,
${python:Depends on a python3 package).

Bug#884686: python-cloudpickle: missing depepdency on the python interpreter

Package: python-cloudpickle
Version: 0.5.2-1
Severity: serious

Dear maintainer,

python-cloudpickle is a Python package but lacks any dependency, including
one on the Python interpreter itself.

Most of the times this is due to using the wrong substvar, for instance
using ${python3:Depends} on a python2 package (or the reverse,
${python:Depends on a python3 package).

Bug#884688: python3-xe: missing depepdency on the python interpreter

Package: python3-xe
Version: 1.0~prerelease-1
Severity: serious

Dear maintainer,

python3-xe is a Python package but lacks any dependency, including
one on the Python interpreter itself.

Most of the times this is due to using the wrong substvar, for instance
using ${python3:Depends} on a python2 package (or the reverse,
${python:Depends on a python3 package).

Bug#884689: python3-pyaes: missing depepdency on the python interpreter

Package: python3-pyaes
Version: 1.6.0-1
Severity: serious

Dear maintainer,

python3-pyaes is a Python package but lacks any dependency, including
one on the Python interpreter itself.

Most of the times this is due to using the wrong substvar, for instance
using ${python3:Depends} on a python2 package (or the reverse,
${python:Depends on a python3 package).

Processed: gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"

Processing control commands:

> reopen -1
Bug #882591 {Done: Jochen Sprickerhof } [src:gazebo] 
gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse error at 
"defined"
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gazebo/7.8.1+dfsg-3.
> notfixed -1 7.8.1+dfsg-3
Bug #882591 [src:gazebo] gazebo FTBFS: 
/usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"
Ignoring request to alter fixed versions of bug #882591 to the same values 
previously set

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

Bug#882591: gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"

2017-12-18 Thread Gianfranco Costamagna

control: reopen -1
control: notfixed -1 7.8.1+dfsg-3

Hello, the Ubuntu patch seems more complete, and your approach will probably 
FTBFS again if the user uses a new boost
(like Ubuntu does), or a new qt or whatever changes.
The Ubuntu patch is taken from Fedora, and seems to make it compile correctly 
with new toolchains, so I think using it
might be beneficial for the future, what do you think?

The failure message is the reason for reopening this bug

PATCH:
http://launchpadlibrarian.net/349631320/gazebo_7.8.1+dfsg-3build1_7.8.1+dfsg-3ubuntu1.diff.gz

FAILURE:
https://launchpad.net/ubuntu/+source/gazebo/7.8.1+dfsg-3/+build/13780015

/usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"
gazebo/gui/CMakeFiles/gazebo_gui.dir/build.make:75: recipe for target 
'gazebo/gui/moc_ApplyWrenchDialog.cxx' failed


thanks!

Gianfranco



signature.asc
Description: OpenPGP digital signature

Processed: isort: missing python dependency on python-isort

Processing control commands:

> close -1 4.2.5+ds1-3
Bug #884682 [python-isort] isort: missing python dependency on python-isort
There is no source info for the package 'python-isort' at version '4.2.5+ds1-3' 
with architecture ''
Unable to make a source version for version '4.2.5+ds1-3'
Marked as fixed in versions 4.2.5+ds1-3.
Bug #884682 [python-isort] isort: missing python dependency on python-isort
Marked Bug as done

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

Bug#884682: isort: missing python dependency on python-isort

2017-12-18 Thread Mattia Rizzolo

Package: python-isort
Version: 4.2.5+ds1-2
Severity: serious
Control: close -1 4.2.5+ds1-3

python-isort doesn't have any dependency, not even a python one, due to
the wrong substvar being used.
Fixed by s/python3/python/ in
https://anonscm.debian.org/viewvc/python-apps/packages/isort/trunk/debian/control?r1=14524=14523=14524

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#884680: xul-ext-quotecolors: Please depend on thunderbird | icedove

2017-12-18 Thread James Clarke

Package: xul-ext-quotecolors
Version: 0.3-4
Severity: serious

Hi,
Icedove has been re-rebranded to Thunderbird, but xul-ext-quotecolors
depends on icedove | iceape. Please fix this to depend on thunderbird
(perhaps | icedove) so the extension can be installed again.

Regards,
James

Bug#882538: jpeg-6b-steg/configure in outguess can be removed

2017-12-18 Thread Hilko Bengen

Control: tag -1 patch

Hi,

the configure file can be removed if the Makefile.in is patched to use
the existing makefile.unix to build the patched JPEG sources.

diff --git a/Makefile.in b/Makefile.in
index c911a5a..88a5717 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -45,7 +45,7 @@ extract: outguess
ln -sf outguess $@
 
 $(JPEGDEP):
-   cd $(JPEGDIR); $(MAKE) libjpeg.a
+   cd $(JPEGDIR); $(MAKE) -f makefile.unix CFLAGS=-DHAVE_STDC_HEADERS 
libjpeg.a
 
 install: all
$(INSTALL_PROG) -m 755 outguess $(install_prefix)$(bindir)

By the way, There *are* a few other packages that embed an old copy of
libjpeg with this specific configure file and without source: Search for
ijg_cv_have_prototypes on codesearch.debian.net.

Cheers,
-Hilko

Processed: jpeg-6b-steg/configure in outguess can be removed

Processing control commands:

> tag -1 patch
Bug #882538 [src:outguess] outguess: missing source for jpeg-6b-steg/configure
Added tag(s) patch.

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

Processed: nomacs: linked with incompatible quazip library

Processing control commands:

> block 875026 by -1
Bug #875026 [src:libquazip] [libquazip] Future Qt4 removal from Buster
875026 was not blocked by any bugs.
875026 was not blocking any bugs.
Added blocking bug(s) of 875026: 884679

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

Bug#884679: nomacs: linked with incompatible quazip library

2017-12-18 Thread Pino Toscano

Source: nomacs
Version: 3.8.0+dfsg-1
Severity: grave
Justification: renders package unusable
Control: block 875026 by -1

Hi,

it seems like nomacs is built against the Qt4 version of the quazip
library (libquazip-dev as build dependency, and links to libquazip1).
Considering nomacs uses Qt5, this combination will not ever work (hence
the 'grave' severity).

Please fix it so it uses the Qt5 version of quazip.

Thanks,
-- 
Pino

Bug#884661: glib2.0: sometimes FTBFS on reproducible-builds: gmenumodel test: assertion failed (items_changed_count == 1): (0 == 1)

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote:
> [#884661] might be new, or just rare.

https://tests.reproducible-builds.org/debian/logs/unstable/amd64/glib2.0_2.54.2-2.build2.log.gz
1..11
# Start of gmenu tests
ok 1 /gmenu/equality
PASS: gmenumodel 1 /gmenu/equality
ok 2 /gmenu/random
PASS: gmenumodel 2 /gmenu/random
ok 3 /gmenu/attributes
PASS: gmenumodel 3 /gmenu/attributes
ok 4 /gmenu/links
PASS: gmenumodel 4 /gmenu/links
ok 5 /gmenu/mutable
PASS: gmenumodel 5 /gmenu/mutable
ok 6 /gmenu/convenience
PASS: gmenumodel 6 /gmenu/convenience
ok 7 /gmenu/menuitem
PASS: gmenumodel 7 /gmenu/menuitem
# Start of dbus tests
ok 8 /gmenu/dbus/roundtrip
PASS: gmenumodel 8 /gmenu/dbus/roundtrip
# 
GLib-GIO:ERROR:../../../../../gio/tests/gmenumodel.c:850:test_dbus_subscriptions:
 assertion failed (items_changed_count == 1): (0 == 1)
ERROR: gmenumodel - too few tests run (expected 11, got 8)
ERROR: gmenumodel - exited with status 134 (terminated by signal 6?)

This is in test /gmenu/dbus/subscriptions, which connects to the
items-changed signal, appends 3 items to an empty menu, runs the main
loop for 200ms, and asserts that there has been one items-changed event
and the menu now has 3 items.

So this looks like some timing issue: something (another parallel
build?) is slowing down the test enough that 200ms is not long enough
to wait.

This test should ideally wait for the expected events to happen (and
optionally assert that the time elapsed is less than some arbitrary
maximum) instead of waiting an arbitrary time and asserting that the
expected events happened. That would often be quicker, too.

smcv

Bug#884466: mesa: firefox, thunderbird, chromium don't start with mesa 17.3.0-1

2017-12-18 Thread Michel Dänzer

On 2017-12-15 07:36 PM, Andreas Boll wrote:
> On Fri, Dec 15, 2017 at 05:04:26PM +0100, Rodolphe Pelloux-Prayer wrote:
>> Package: libglx-mesa0
>> Version: 17.3.0-1
>> Severity: important
>> File: mesa
>>
>> Dear Maintainer,
>>
>> after upgrading to 17.3.0-1, firefox, thunderbird and chromium don't start 
>> or more accuratly seems to not display ([AMD/ATI] Oland GL [FirePro W2100])
>>
>> Starting firefox in gdb:
>> Start it from the beginning? (y or n) y
>> Starting program: /usr/lib/firefox/firefox 
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> [New Thread 0x7fffe4844700 (LWP 9406)]
>> [Thread 0x7fffe4844700 (LWP 9406) exited]
>> Error: GDK_BACKEND does not match available displays

Looks like this might be due to the environment variable GDK_BACKEND
being set to an invalid value.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#884660: glib2.0: sometimes FTBFS on reproducible-builds: gdbus-threading test: assertion failed (elapsed_msec < 8000): (8220 < 8000)

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote:
> [#884660] can also be seen in
> https://tests.reproducible-builds.org/debian/rbuild/buster/amd64/glib2.0_2.54.1-1.rbuild.log

gdbus-threading.c tests that GDBus is thread-safe. Three client threads
call into a server: thread 1 calls the Sleep() method 100 times with a 40ms
argument, thread 2 calls the Sleep() method 20 times with a 200ms argument,
and thread 3 calls it 100 times with a 40ms argument. The Sleep() method
just waits the indicated time and returns. The main thread waits for the
three client threads - they should all take 4000ms, plus D-Bus overhead,
minus up to 40ms because GLib timeouts with 1ms granularity can finish
slightly early - and asserts that the time elapsed was in the range
[3950, 8000) ms. In this case it took 8220ms.

The 8 second limit is essentially arbitrary: David Zeuthen increased it
from 5 to 6 seconds in 2010 because an 867MHz PowerPC took too long, and
Martin Pitt increased it from 6 to 8 seconds in 2012 because a PandaBoard
(~1 GHz ARM) was also taking too long. So we can increase the timeout as
far as is necessary, within reason.

However, I'm surprised that a 2017 x86_64 server is doing this test slower
than a 2003 PowerPC laptop or a 2010 low-cost ARM developer board. Are
the reproducible-builds machines building multiple unrelated packages in
parallel? If so, then I don't think it's necessarily all that unexpected
that timing-dependent automated tests will sometimes fail.

smcv

Bug#884674: 2to binary moved to the 2to3 binary package

Package: src:sparql-wrapper-python
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

Bug#884670: 2to3 binary moved to it's own 2to3 package

Package: src:sqlparse
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

Bug#884659: glib2.0: sometimes FTBFS on reproducible-builds: gwakeup, gwakeup-fallback tests terminated by SIGALRM

(Re-sending to the correct bug, sorry for the noise. Please reply to
this copy, not the previous one.)

On Mon, 18 Dec 2017 at 09:17:46 +, Simon McVittie wrote:
> [#884654] is not new. It has also happened (more often for
> gwakeup-fallback) in earlier versions:
> https://tests.reproducible-builds.org/debian/rbuild/stretch/amd64/glib2.0_2.50.3-2.rbuild.log
> https://tests.reproducible-builds.org/debian/rbuild/buster/amd64/glib2.0_2.54.1-1.rbuild.log
> https://tests.reproducible-builds.org/debian/logs/buster/armhf/glib2.0_2.54.1-1.build2.log.gz
> Presumably it doesn't happen on the real buildds because the reproducible
> build workers are more heavily-loaded, or have more or fewer CPUs, or
> some other factor. It isn't the build vs. build2 variation, because this
> test failure has been seen in both.

It looks as though the failing test is always /gwakeup/threaded or
/gwakeup/threaded-fallback (we see /gwakeup/semantics{,-fallback} pass
before the test fails, and threaded{,-fallback} is the only other test
in this executable).

That's a multi-threaded stress-test for GWakeup:

- set an alarm for 60 seconds, so that on failure we don't block forever
- create 50 threads
- create 5 "tokens", each with a TTL of 100K
- each token is owned by one thread at a time
- each thread is woken up when it owns at least one token, and at that
  point it will do:
  - for each token:
- decrement the TTL
- if the TTL is nonzero, choose a random thread and send the token
  to that thread
- when all tokens' TTLs are zero, wake up the main thread, which exits

It reliably passes on the buildds (even those for weaker architectures
like mips). Are the reproducible-builds machines perhaps doing other
things in parallel with running the glib2.0 test suite, such as building
another package?

The 60 second alarm is completely arbitrary (it was increased from
30 because some ARM systems took more than 30 seconds to finish). The
thread count, number of tokens and token TTL are probably also completely
arbitrary, and could be reduced, at the cost of being less likely to
detect bugs (unfortunately this sort of threading stress-test is usually
probabilistic).

smcv

Bug#884672: 2to3 binary moved to the 2to3 package

Package: src:rdflib
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

Bug#884671: 2to3 binary moved to it's own 2to3 package

Package: src:uwsgi
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

Bug#884669: 2to3 binary moved to it's own 2to3 package

Package: src:pyzmq
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

Bug#884668: 2to3 binary moved to it's own 2to3 package

Package: src:python-dsv
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

Bug#884667: 2to3 binary moved to it's own 2to3 package

Package: src:pycxx
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

Bug#884666: 2to3 binary moved to it's own 2to3 package

Package: src:nuitka
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

Processed: Also corruption on shutdown/start

Processing control commands:

> severity -1 critical
Bug #884622 [src:linux] Migrating VM with kernel 3.16 between xen hosts results 
in fs corruption / data loss
Severity set to 'critical' from 'normal'

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

Processed: Also add affects on the src:

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

> affects 884627 src:appstream-generator src:appstream src:vibe.d
Bug #884627 [meson] vibe.d FTBFS with meson 0.44.0-1: Subproject_dir must not 
contain a path segment
Bug #884628 [meson] appstream-generator FTBFS with meson 0.44.0-1: 
Subproject_dir must not contain a path segment
Bug #884629 [meson] appstream FTBFS with meson 0.44.0-1
Added indication that 884627 affects src:appstream-generator, src:appstream, 
and src:vibe.d
Added indication that 884628 affects src:appstream-generator, src:appstream, 
and src:vibe.d
Added indication that 884629 affects src:appstream-generator, src:appstream, 
and src:vibe.d
> thanks
Stopping processing here.

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

Bug#884654: glib2.0: sometimes FTBFS on reproducible-builds: gwakeup, gwakeup-fallback tests terminated by SIGALRM