Bug#939002: r-cran-sf: autopkgtest failure prevents testing migration

[Bas Couwenberg]

Source: r-cran-sf
Version: 0.7-7+dfsg-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 931949 by -1

Dear Maintainer,

Since the upgrade to proj (6.1.1-1) the autopkgtest for your package
fail:

 https://ci.debian.net/packages/r/r-cran-sf/

This prevents testing migration of proj and its rdeps.

Please fix or remove the autopkgtest for your package.

Kind Regards,

Bas

Processed: r-cran-sf: autopkgtest failure prevents testing migration

[Debian Bug Tracking System]

Processing control commands:

> block 931949 by -1
Bug #931949 [release.debian.org] transition: proj
931949 was blocked by: 931944 931904 931943 931935 931908 931922 931914 931940 
931941 931931 931948 931945 936017 931872
931949 was blocking: 931950
Added blocking bug(s) of 931949: 939002

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

Processed: your mail

[Debian Bug Tracking System]

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

> affects 937330 + src:wxpython3.0
Bug #937330 [src:psychopy] psychopy: Python2 removal in sid/bullseye
Added indication that 937330 affects src:wxpython3.0
> affects 937623 + src:wxpython3.0
Bug #937623 [src:python-bumps] python-bumps: Python2 removal in sid/bullseye
Added indication that 937623 affects src:wxpython3.0
> affects 936578 + src:wxpython3.0
Bug #936578 [src:gamera] gamera: Python2 removal in sid/bullseye
Added indication that 936578 affects src:wxpython3.0
> affects 938081 + src:wxpython3.0
Bug #938081 [src:python-pyo] python-pyo: Python2 removal in sid/bullseye
Added indication that 938081 affects src:wxpython3.0
> affects 938827 + src:wxpython3.0
Bug #938827 [src:winpdb] winpdb: Python2 removal in sid/bullseye
Added indication that 938827 affects src:wxpython3.0
> affects 936210 + src:wxpython3.0
Bug #936210 [src:bittorrent] bittorrent: Python2 removal in sid/bullseye
Added indication that 936210 affects src:wxpython3.0
> affects 936261 + src:wxpython3.0
Bug #936261 [src:cain] cain: Python2 removal in sid/bullseye
Added indication that 936261 affects src:wxpython3.0
> affects 936395 + src:wxpython3.0
Bug #936395 [src:dicompyler] dicompyler: Python2 removal in sid/bullseye
Added indication that 936395 affects src:wxpython3.0
> affects 936404 + src:wxpython3.0
Bug #936404 [src:displaycal] displaycal: Python2 removal in sid/bullseye
Added indication that 936404 affects src:wxpython3.0
> affects 936424 + src:wxpython3.0
Bug #936424 [src:djvusmooth] djvusmooth: Python2 removal in sid/bullseye
Added indication that 936424 affects src:wxpython3.0
> affects 936469 + src:wxpython3.0
Bug #936469 [src:editra] editra: Python2 removal in sid/bullseye
Added indication that 936469 affects src:wxpython3.0
> affects 936543 + src:wxpython3.0
Bug #936543 [src:fontypython] fontypython: Python2 removal in sid/bullseye
Added indication that 936543 affects src:wxpython3.0
> affects 936578 + src:wxpython3.0
Bug #936578 [src:gamera] gamera: Python2 removal in sid/bullseye
Ignoring request to set affects of bug 936578 to the same value previously set
> affects 936583 + src:wxpython3.0
Bug #936583 [src:gastables] gastables: Python2 removal in sid/bullseye
Added indication that 936583 affects src:wxpython3.0
> affects 936630 + src:wxpython3.0
Bug #936630 [src:gnumed-client] gnumed-client: Python2 removal in sid/bullseye
Added indication that 936630 affects src:wxpython3.0
> affects 936655 + src:wxpython3.0
Bug #936655 {Done: Sebastiaan Couwenberg } [src:grass] 
grass: Python2 removal in sid/bullseye
Added indication that 936655 affects src:wxpython3.0
> affects 936792 + src:wxpython3.0
Bug #936792 [src:kicad] kicad: Python2 removal in sid/bullseye
Added indication that 936792 affects src:wxpython3.0
> affects 936795 + src:wxpython3.0
Bug #936795 [src:kiki] kiki: Python2 removal in sid/bullseye
Added indication that 936795 affects src:wxpython3.0
> affects 936966 + src:wxpython3.0
Bug #936966 [src:londonlaw] londonlaw: Python2 removal in sid/bullseye
Added indication that 936966 affects src:wxpython3.0
> affects 936996 + src:wxpython3.0
Bug #936996 [src:mayavi2] mayavi2: Python2 removal in sid/bullseye
Added indication that 936996 affects src:wxpython3.0
> affects 936497 + src:wxpython3.0
Bug #936497 [src:expeyes] expeyes: Python2 removal in sid/bullseye
Added indication that 936497 affects src:wxpython3.0
> affects 937057 + src:wxpython3.0
Bug #937057 [src:mmass] mmass: Python2 removal in sid/bullseye
Added indication that 937057 affects src:wxpython3.0
> affects 937061 + src:wxpython3.0
Bug #937061 [src:model-builder] model-builder: Python2 removal in sid/bullseye
Added indication that 937061 affects src:wxpython3.0
> affects 937200 + src:wxpython3.0
Bug #937200 [src:opendict] opendict: Python2 removal in sid/bullseye
Added indication that 937200 affects src:wxpython3.0
> affects 937282 + src:wxpython3.0
Bug #937282 [src:phatch] phatch: Python2 removal in sid/bullseye
Added indication that 937282 affects src:wxpython3.0
> affects 937302 + src:wxpython3.0
Bug #937302 [src:playonlinux] playonlinux: Python2 removal in sid/bullseye
Added indication that 937302 affects src:wxpython3.0
> affects 937325 + src:wxpython3.0
Bug #937325 [src:printrun] printrun: Python2 removal in sid/bullseye
Added indication that 937325 affects src:wxpython3.0
> affects 937228 + src:wxpython3.0
Bug #937228 [src:p9m4] p9m4: Python2 removal in sid/bullseye
Added indication that 937228 affects src:wxpython3.0
> affects 937457 + src:wxpython3.0
Bug #937457 [src:pyhoca-gui] pyhoca-gui: Python2 removal in sid/bullseye
Added indication that 937457 affects src:wxpython3.0
> affects 937464 + src:wxpython3.0
Bug #937464 [src:pykaraoke] pykaraoke: Python2 removal in sid/bullseye
Added indication that 937464 affects src:wxpython3.0
> affects 937506 + src:wxpython3.0
Bug #937506 [src:pype] pype: Python2 removal in sid/bullseye
Added indication that 937506 affects src:wxpython3.0
> affects 937321 + 

Bug#931609: marked as done (Update release names after the Buster release.)

[Debian Bug Tracking System]

Your message dated Sat, 31 Aug 2019 01:02:23 +
with message-id 
and subject line Bug#931609: fixed in reportbug 7.5.3~deb10u1
has caused the Debian Bug report #931609,
regarding Update release names after the Buster release.
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.)


-- 
931609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.5.2+deb10u1
Severity: important

Hi,

Please apply the attached patch to fix reportbug regarding the new release
name mappings. Please allow me to NMU this at least in Buster, if you
don't have time to upload yourself, as IMO, this is a bit critical. Indeed,
I tried to do:

"reportbug -b release.debian.org cloudkitty"

selected stretch-pu, thinking I'll fix later on, but reportbug just crashed
on me trying to fetch version numbers, as cloudkitty isn't in Stretch. This
isn't nice at all... :)

Cheers,

Thomas Goirand (zigo)
diff --git a/debian/changelog b/debian/changelog
index a8c7b04..8b167c9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+reportbug (7.5.2+deb10u1) buster; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix release names.
+
+ -- Thomas Goirand   Mon, 08 Jul 2019 10:22:29 +0200
+
 reportbug (7.5.2) unstable; urgency=medium
 
   * bin/reportbug
diff --git a/reportbug/__init__.py b/reportbug/__init__.py
index 5158a19..aecbd4f 100644
--- a/reportbug/__init__.py
+++ b/reportbug/__init__.py
@@ -25,7 +25,7 @@ SOFTWARE."""
 __all__ = ['bugreport', 'utils', 'urlutils', 'checkbuildd', 'checkversions',
'debbugs', 'exceptions', 'submit', 'tempfile']
 
-VERSION_NUMBER = "7.5.2"
+VERSION_NUMBER = "7.5.2+deb10u1"
 
 VERSION = "reportbug " + VERSION_NUMBER
 COPYRIGHT = VERSION + '\nCopyright (C) 1999-2008 Chris Lawrence 
' + \
diff --git a/reportbug/utils.py b/reportbug/utils.py
index 545504d..98e089a 100644
--- a/reportbug/utils.py
+++ b/reportbug/utils.py
@@ -93,11 +93,11 @@ fhs_directories = ['/', '/usr', '/usr/share', '/var', 
'/usr/X11R6',
'/usr/man', '/usr/doc', '/usr/bin']
 
 # A map between codenames and suites
-CODENAME2SUITE = {'wheezy': 'oldoldstable',
-'jessie': 'oldstable',
-'stretch': 'stable',
-'buster': 'testing',
-'bullseye': 'next-testing',
+CODENAME2SUITE = {'jessie': 'oldoldstable',
+'stretch': 'oldstable',
+'buster': 'stable',
+'bullseye': 'testing',
+'bookworm': 'next-testing',
 'sid': 'unstable',
 'experimental': 'experimental'}
 SUITE2CODENAME = dict([(suite, codename) for codename, suite in 
list(CODENAME2SUITE.items())])
--- End Message ---
--- Begin Message ---
Source: reportbug
Source-Version: 7.5.3~deb10u1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated reportbug package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Aug 2019 13:52:06 +0200
Source: reportbug
Architecture: source
Version: 7.5.3~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Reportbug Maintainers 
Changed-By: Andreas Beckmann 
Closes: 923631 925422 931609 932524 934472 935602
Changes:
 reportbug (7.5.3~deb10u1) buster; urgency=medium
 .
   * Non-maintainer upload.
   * Re-enable submitting stretch-pu requests.
   * Rebuild for buster.
 .
 reportbug (7.5.3) unstable; urgency=medium
 .
   * debian/control
 - replace emacs* Suggests with emacs-bin-common; Closes: #925422
 - bump Standards-Version to 4.4.0 (no changes needed)
 - add sensible-utils dep, patch by Nis Martensen
   * reportbug/debbugs.py
 - when handling ftp.d.o, dont look up package information if the package
   doesnt exist, fixing a crash; Closes: #923631
 - fix a crash with stable version lookup, patch by Nis Martensen;
   Closes: #935602
   * bin/reportbug
 - remove debug code when handling 

Bug#934886: marked as done (CVE-2019-9512 CVE-2019-9514 CVE-2019-9515)

[Debian Bug Tracking System]

Your message dated Sat, 31 Aug 2019 01:02:11 +
with message-id 
and subject line Bug#934886: fixed in h2o 2.2.5+dfsg2-2+deb10u1
has caused the Debian Bug report #934886,
regarding CVE-2019-9512 CVE-2019-9514 CVE-2019-9515
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.)


-- 
934886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: h2o
Severity: grave
Tags: security

h2o is affected by three of the recently announced HTTP2 issues:
https://github.com/h2o/h2o/issues/2090

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: h2o
Source-Version: 2.2.5+dfsg2-2+deb10u1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated h2o 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, 20 Aug 2019 22:29:07 +0200
Source: h2o
Binary: h2o h2o-dbgsym h2o-doc libh2o-dev libh2o-dev-common libh2o-evloop-dev 
libh2o-evloop0.13 libh2o-evloop0.13-dbgsym libh2o0.13 libh2o0.13-dbgsym
Architecture: source amd64 all
Version: 2.2.5+dfsg2-2+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Apollon Oikonomopoulos 
Changed-By: Anton Gladky 
Description:
 h2o- optimized HTTP/1.x, HTTP/2 server
 h2o-doc- optimized HTTP/1.x, HTTP/2 server - documentation
 libh2o-dev - dev helpers of the H2O library compiled with libuv
 libh2o-dev-common - H2O library headers
 libh2o-evloop-dev - dev helpers of the H2O library compiled with its own event 
loop
 libh2o-evloop0.13 - H2O library compiled with its own event loop
 libh2o0.13 - H2O library compiled with libuv
Closes: 934886
Changes:
 h2o (2.2.5+dfsg2-2+deb10u1) buster-security; urgency=high
 .
   * [d9b7843] Fix HTTP/2 DoS attack vulnerabilities.
   CVE-2019-9512 CVE-2019-9514 CVE-2019-9515. (Closes: #934886)
Checksums-Sha1:
 89b40d175eec1ea2302af81dc2ad14cc0d717cc1 2610 h2o_2.2.5+dfsg2-2+deb10u1.dsc
 fab346b873f07f5de65709d7a925c52555637f83 11138636 h2o_2.2.5+dfsg2.orig.tar.xz
 2bdd5490959b5fa66f7bd19d5247a7bd72f03e0a 14492 
h2o_2.2.5+dfsg2-2+deb10u1.debian.tar.xz
 9ed9c3a5a318981573b3e9ff7f87b96326bb4209 3857328 
h2o-dbgsym_2.2.5+dfsg2-2+deb10u1_amd64.deb
 8d90300d7814f3a8d63c3c4938d53ce76705dee7 834940 
h2o-doc_2.2.5+dfsg2-2+deb10u1_all.deb
 60b8a463267298781b3ffbfb6986e5dff23cc615 11600 
h2o_2.2.5+dfsg2-2+deb10u1_amd64.buildinfo
 47e2fd5b03bc207295043f4d8a0744cf6bc3f4ff 935304 
h2o_2.2.5+dfsg2-2+deb10u1_amd64.deb
 da8b7126597baf95bbae78647b6dec2ad649e037 56176 
libh2o-dev-common_2.2.5+dfsg2-2+deb10u1_all.deb
 57eb05c50c3c61ee64d1edc4c039ba149ee30445 20156 
libh2o-dev_2.2.5+dfsg2-2+deb10u1_amd64.deb
 09ce914270c1f67521bf2f70aae6094fabca7760 20160 
libh2o-evloop-dev_2.2.5+dfsg2-2+deb10u1_amd64.deb
 a8a12f8361c69767ca987433de4194cb051b082e 926268 
libh2o-evloop0.13-dbgsym_2.2.5+dfsg2-2+deb10u1_amd64.deb
 6312d36eca68e52d5dc688aa9b31a607bdfd895c 186152 
libh2o-evloop0.13_2.2.5+dfsg2-2+deb10u1_amd64.deb
 d2c6751f30a6596e3b24ec1c2ec1159b3ac650fe 971992 
libh2o0.13-dbgsym_2.2.5+dfsg2-2+deb10u1_amd64.deb
 e9d38e8760cf3da9e6cc25621276416a12dfeed0 183536 
libh2o0.13_2.2.5+dfsg2-2+deb10u1_amd64.deb
Checksums-Sha256:
 1f45e4f5eb0798f3fb49c185b07b0c31a1ca7485062c5df3fd92f29563a67408 2610 
h2o_2.2.5+dfsg2-2+deb10u1.dsc
 a46894bd85da6528d4ad90ce0443b48118718296175061a1a1156e9e3af60a0d 11138636 
h2o_2.2.5+dfsg2.orig.tar.xz
 f334540213807d0c88bfe77119bc7380f1d16c63d5ce960f7256f41379d33903 14492 
h2o_2.2.5+dfsg2-2+deb10u1.debian.tar.xz
 58ec626a4727e0f9be06301954b3de6d859a95f8628d943ad9e4514037951dd7 3857328 
h2o-dbgsym_2.2.5+dfsg2-2+deb10u1_amd64.deb
 4c05c8615437508483f17f289a7397741e71b6236859a99085a63d02c157ede4 834940 
h2o-doc_2.2.5+dfsg2-2+deb10u1_all.deb
 aecb5ccc897605f6b72f264e1247bd5ddbb8d02afab2f0b824631cd3dbe052e2 11600 
h2o_2.2.5+dfsg2-2+deb10u1_amd64.buildinfo
 508913c466272adc40d97aab6080a81cdfb33dd5c7b6c0ddba6913d81375c155 935304 
h2o_2.2.5+dfsg2-2+deb10u1_amd64.deb
 

Bug#935990: marked as done (mkgmap: Boundary preprocessor and splitter throw exceptions, likely dependency issue)

[Debian Bug Tracking System]

Your message dated Sat, 31 Aug 2019 01:02:22 +
with message-id 
and subject line Bug#935990: fixed in osmpbf 1.3.3-11+deb10u1
has caused the Debian Bug report #935990,
regarding mkgmap: Boundary preprocessor and splitter throw exceptions, likely 
dependency issue
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.)


-- 
935990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mkgmap
Version: 0.0.0+svn4262-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

It appears something is seriously wrong with dependency versions, linkage or
similar, as both mkgmap's boundary preprocessor and mkgmap-splitter are broken,
throwing exceptions.

I cannot determine what the problem is exactly, but from what I read similar
errors often are caused by dependency version mismatches, especially with
protobuf. Perhaps the classes are compiled with a mismatched protobuf compiler
version (compared to runtime)?

Upstream pre-compiled download ships with versions:
fastutil-6.5.15-mkg.1b.jar
osmpbf-1.3.3.jar
protobuf-java-2.5.0.jar

Upstream mkgmaps-splitter ships, in addition to the above three, with versions:
xpp3-1.1.4c.jar

If I use upstream's zip file, and the upstream-provided libraries/dependencies,
everything works fine. I use an utility called vermosm for generating the maps,
the following steps will reproduce the problem using the tiny country Luxembourg
to avoid downloading big files and to avoid long processing time. Around 300MiB
will be downloaded, processing will fail very quickly after downloading.

git clone https://git.mel.vin/osm/vermosm.git vermosm
cd vermosm
# Check required dependencies in README.md, optionals not needed to reproduce.
./vermosm.sh -c luxembourg -r europe -t asset/typ/freizeitkarte_contrast.txt -v

mkgmap boundary preprocessor throws:

java.util.concurrent.ExecutionException: java.lang.UnsupportedOperationException
java.util.concurrent.ExecutionException: java.lang.UnsupportedOperationException
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at 
uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreprocessor.runPreprocessing(BoundaryPreprocessor.java:186)
at 
uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreprocessor.main(BoundaryPreprocessor.java:129)
Caused by: java.lang.UnsupportedOperationException
at crosby.binary.Fileformat$BlobHeader.dynamicMethod(Unknown Source)
at com.google.protobuf.GeneratedMessageLite.dynamicMethod(Unknown 
Source)
at com.google.protobuf.GeneratedMessageLite.isInitialized(Unknown 
Source)
at com.google.protobuf.GeneratedMessageLite.isInitialized(Unknown 
Source)
at 
com.google.protobuf.GeneratedMessageLite.checkMessageInitialized(Unknown Source)
at com.google.protobuf.GeneratedMessageLite.parseFrom(Unknown Source)
at crosby.binary.Fileformat$BlobHeader.parseFrom(Unknown Source)
at crosby.binary.file.FileBlockHead.readHead(Unknown Source)
at crosby.binary.file.FileBlock.process(Unknown Source)
at crosby.binary.file.BlockInputStream.process(Unknown Source)
at 
uk.me.parabola.mkgmap.reader.osm.bin.OsmBinHandler.parse(OsmBinHandler.java:57)
at 
uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.parse(OsmMapDataSource.java:171)
at 
uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:152)
at 
uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreprocessor.createRawData(BoundaryPreprocessor.java:97)
at 
uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreprocessor.run(BoundaryPreprocessor.java:74)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Bnd files converted in 1148 ms

mkgmap-splitter throws:

java.lang.UnsupportedOperationException
at crosby.binary.Fileformat$BlobHeader.dynamicMethod(Unknown Source)
at com.google.protobuf.GeneratedMessageLite.dynamicMethod(Unknown 
Source)
at com.google.protobuf.GeneratedMessageLite.isInitialized(Unknown 
Source)
at 

Bug#931801: marked as done (mariadb-server-core-10.3: mysqld segfaults when database `information_schema` is accessed)

[Debian Bug Tracking System]

Your message dated Sat, 31 Aug 2019 01:02:20 +
with message-id 
and subject line Bug#931801: fixed in mariadb-10.3 1:10.3.17-0+deb10u1
has caused the Debian Bug report #931801,
regarding mariadb-server-core-10.3: mysqld segfaults when database 
`information_schema` is accessed
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.)


-- 
931801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-server-core-10.3
Version: 1:10.3.15-1
Severity: critical
Justification: causes serious data loss



-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-server-core-10.3 depends on:
ii  libaio1 0.3.112-3
ii  libc6   2.28-10
ii  libgnutls30 3.6.7-4
ii  liblz4-11.8.3-1
ii  libpcre32:8.39-12
ii  libsnappy1v51.1.7-1
ii  libstdc++6  8.3.0-6
ii  libsystemd0 241-5
ii  mariadb-common  1:10.3.15-1
ii  zlib1g  1:1.2.11.dfsg-1

mariadb-server-core-10.3 recommends no packages.

mariadb-server-core-10.3 suggests no packages.

-- no debconf information

How to trigger the issue:
 * install mariadb-server
 * start 'mysql' in a terminal
 * enter 'user information_schema'

The process mysqld will segfault, thus terminating all existing processes 
within the server.
It writes the following to the error log (e.g. /var/lib/mysql/error.log:

---
190710 16:45:48 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.3.15-MariaDB-1
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467420 K  
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x55b4ef5ef738
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7f2beceeadd8 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55b4eda6ea5e]
/usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55b4ed5d8fcd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f2bf1f27730]
/usr/sbin/mysqld(+0xc6b67a)[0x55b4edad167a]
/usr/sbin/mysqld(_Z17find_schema_tableP3THDPK25st_mysql_const_lex_stringPb+0x55)[0x55b4ed475eb5]
/usr/sbin/mysqld(_Z11open_tablesP3THDRK14DDL_options_stPP10TABLE_LISTPjPP19Sroutine_hash_entryjP19Prelocking_strategy+0x8cf)[0x55b4ed3b59af]
/usr/sbin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTjj+0x64)[0x55b4ed3b6684]
/usr/sbin/mysqld(_Z18mysqld_list_fieldsP3THDP10TABLE_LISTPKc+0x35)[0x55b4ed466655]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x24c8)[0x55b4ed413b68]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x170)[0x55b4ed4140b0]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x20a)[0x55b4ed4e25da]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x55b4ed4e277d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7f2bf1f1cfa3]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f2bf15a64cf]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x55b4ef5fd1f0):
Connection ID (thread ID): 36
Status: NOT_KILLED

Optimizer switch: 

Processed: severity of 936341 is serious, affects 936341

[Debian Bug Tracking System]

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

> severity 936341 serious
Bug #936341 [src:createrepo] createrepo: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> affects 936341 + koji-servers obs-server
Bug #936341 [src:createrepo] createrepo: Python2 removal in sid/bullseye
Added indication that 936341 affects koji-servers and obs-server
> thanks
Stopping processing here.

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

Bug#935733: marked as done (libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 23:04:52 +
with message-id 
and subject line Bug#935733: fixed in bladerf 0.2019.07-4
has caused the Debian Bug report #935733,
regarding libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/doc/libbladerf-dev/CONTRIBUTORS
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.)


-- 
935733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbladerf-doc
Version: 0.2019.07-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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libbladerf-doc_0.2019.07-1_all.deb ...
  Unpacking libbladerf-doc (0.2019.07-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbladerf-doc_0.2019.07-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libbladerf-dev/CONTRIBUTORS', which is 
also in package libbladerf-dev:amd64 0.2017.12~rc1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libbladerf-doc_0.2019.07-1_all.deb


cheers,

Andreas


libbladerf-dev=0.2017.12~rc1-2_libbladerf-doc=0.2019.07-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bladerf
Source-Version: 0.2019.07-4

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated bladerf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Aug 2019 18:20:01 -0400
Source: bladerf
Architecture: source
Version: 0.2019.07-4
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 935733
Changes:
 bladerf (0.2019.07-4) unstable; urgency=medium
 .
   * Correct Breaks:/Replaces: (Closes: #935733)
Checksums-Sha1:
 6760b456bbd998573f5fc69e405ee79f654eeb0a 3088 bladerf_0.2019.07-4.dsc
 e2a5d965d6c7c04cf7841f77e932ecc79be76da4 68316 
bladerf_0.2019.07-4.debian.tar.xz
 fc774670f97dcdad9d9e8ec0e462fce7dbddb5dd 12554 
bladerf_0.2019.07-4_amd64.buildinfo
Checksums-Sha256:
 59045847a74fbb9739cf1b8e1c4340d71dce3ff622950454a74b87370b58dce7 3088 
bladerf_0.2019.07-4.dsc
 16232ed4ffb24e849c63e7bb1d4b33d14eefa5b8c4b1303288cb1c8c3b04fb84 68316 
bladerf_0.2019.07-4.debian.tar.xz
 aa8c27503fcef62eeb8683211db8bb54859416cc9ddb15c6d0667698ed4f72b2 12554 
bladerf_0.2019.07-4_amd64.buildinfo
Files:
 d118842169de953b71b046095e9abb11 3088 comm optional bladerf_0.2019.07-4.dsc
 b285c7eb9a138445a433cd5485c28d36 68316 comm optional 
bladerf_0.2019.07-4.debian.tar.xz
 4017555b3c105b5b8ee7f256989ab142 12554 comm optional 
bladerf_0.2019.07-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAl1ppD0ACgkQUEHxiR9E
4JAfaRAAz+xxnFGvEs3NQJNRexcXLFz2lZYMeSqnzb6pZusl0CAzSU9ONKr2g/Fo
23kiT7vPLu7nXUfV/anb9TKrJdt32km32x1OJmtiZ1zyAFNXogu5AtUW7l2gqcDQ
hU1V3FH1Z/YrP+r1QWX6nuL3z9VNmoWJ0XDgaLfdIJZ7Yh1quLoXDetPfFhX+tWZ
vG1tE1LaPwFBBxKHWd5+ZCHXHSEwmyin5e5mjIatvYhGBx5Cd6aWWx/miuSoxm24
121wGZ0tkkBtmRVGTai2n2G8cwCUw6lyf655x7IC56PiuQ9cG8uN7qGiLM/mNiic
jVJbXzzf5Nf6nCpc7mNMK9akBofO7eU3EfCcWqPsiKa84tRJC+pRPW7EFKeoWoaL
jZkv00jWl3RNV+UeS4E+yrvdgK0jk+hkLBPH+/CvcY/Un8SUxQzjG7DcvzoIt8Z+
tD95x8mGGj4yT6oM/2hE1XGdcgmzWvZjllRLB0oz1Lur5NJ2u/bnptvaCnTKoFvU
KHoEmJVabwLTnYK+8yNpucD6vjEJLE3JjSY19pcpVVDfE6pFn2Rjma8bKy0FRasb
U7G+k/zSHJJAsGk5ZFzielPqaueyvultIU1/4F/lrvB2MBBMZtbtDmWfkd7feaNN
QuXyN2HZuX/mSJC//PdhvmaZ6Vg8NhN+oDtnhPSIrdP3BKuWlPY=
=R4Qc
-END PGP SIGNATURE End Message ---

Bug#938996: cl-swank: starting clisp under SLIME explodes with: FUNCALL: undefined function SWANK::MAKE-OUTPUT-STREAM-FOR-TARGET

[Christoph Badura]

Package: cl-swank
Version: 2:2.24+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

this is on a Raspberry PI 2 installed off https://people.debian.org/~gwolf/raspb
errypi/20190628/20190628_raspberry-pi-2_buster_PREVIEW.img.xz

To preproduce:

Enable testing in sources.list.
apt-get -t=testing install clisp slime
emacs -q -nw
ESC:(require 'slime)RET
ESCxslimeRET

This drops into sldb with:
FUNCALL: undefined function SWANK::MAKE-OUTPUT-STREAM-FOR-TARGET
   [Condition of type SYSTEM::SIMPLE-UNDEFINED-FUNCTION]

This doesn't happen when starting SLIME 2.24 from melpa (slime-20190818.1634).
Clisp does crash the same way as in #938993 though.

Thanks,
--chb

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (400, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 4.19.0-5-armmp (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Processed: severity of 684743 is serious

[Debian Bug Tracking System]

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

> severity 684743 serious
Bug #684743 [python-lamson] python-lamson: missing dependency on 
python-pkg-resources
Severity set to 'serious' from 'important'
> severity 771615 serious
Bug #771615 [python-lamson] python-lamson: non-functioning email address for 
Maintainer
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#938995: python-statsmodels-doc: missing Breaks+Replaces: python-statsmodels (<< 0.9)

[Andreas Beckmann]

Package: python-statsmodels-doc
Version: 0.9.0-3
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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python-statsmodels-doc_0.9.0-3_all.deb ...
  Unpacking python-statsmodels-doc (0.9.0-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-statsmodels-doc_0.9.0-3_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/python-statsmodels/examples/incomplete/arima.py', which is also 
in package python-statsmodels 0.8.0-9
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python-statsmodels-doc_0.9.0-3_all.deb


cheers,

Andreas


python-statsmodels=0.8.0-9_python-statsmodels-doc=0.9.0-3.log.gz
Description: application/gzip

Bug#938993: clisp crashes under slime when doing tab-completion

[Christoph Badura]

Package: clisp
Version: 1:2.49.20180218+really2.49.92-3+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

this is on a Raspberry PI 2 installed off 
https://people.debian.org/~gwolf/raspberrypi/20190628/20190628_raspberry-pi-2_buster_PREVIEW.img.xz

To reproduce:

apt-get -qy install emacs slime clisp

emacs -q -nw
ESC:(require 'slime)RET
ESCxslimeRET
TAB

The mini-buffer shows the message "Lisp connection closed unexpectedly"

The *inferior-lisp* buffer has, apart from the usual warnings, the following
relevant output:

*** - handle_fault error2 ! address = 0x60022 not in [0x48060004,0x4835739c) !
SIGSEGV cannot be cured. Fault address = 0x60022.
GC count: 43
Space collected by GC: 0 27406896
Run time: 15 153135
Real time: 19 963098
GC time: 2 133641
Permanently allocated: 94496 bytes.
Currently in use: 4772368 bytes.
Free space: 1090634 bytes.

Process inferior-lisp segmentation fault

The expected outcome would have been a working REPL, of course. ;-)

In case you are wondering, I've updated slime, cl-swank and clisp to the
versions in testing. But that explodes while trying to load swank. I'll
open a separate bug for that.

BTW, could someone address the warnings in #655273?  That would be nice.

Thanks,
--chb

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (400, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 4.19.0-5-armmp (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages clisp depends on:
ii  libc6  2.28-10
ii  libffcall1b2.1-2
ii  libncurses66.1+20181013-2
ii  libreadline7   7.0-5
ii  libsigsegv22.12-2
ii  libtinfo6  6.1+20181013-2
ii  libunistring2  0.9.10-1

clisp recommends no packages.

Versions of packages clisp suggests:
pn  clisp-doc 
pn  clisp-module-berkeley-db  
pn  clisp-module-clx  
pn  clisp-module-dbus 
pn  clisp-module-gdbm 
pn  clisp-module-pcre 
pn  clisp-module-postgresql   
pn  clisp-module-zlib 
pn  gdb   
ii  slime 2:2.23+dfsg-2

-- no debconf information

Bug#923481: alpine: replies lose In-Reply-To and References headers

[Unit 193]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Control: severity -1 important

Howdy,

On Mon, 19 Aug 2019, Thorsten Glaser wrote:


On Tue, 13 Aug 2019, Unit 193 wrote:


Ah right.  Though while looking through several of my recent sent items, it
seems it preserved those fields as expected.  I am using alpine 2.21.


Please try this, from the original submission:


I've confirmed this does indeed remove them.


If I take a message, reply to it, then go to the Subject line,
press ^K to remove the existing (possibly damaged) text and type
new text (possibly to change the subthread subject), the eMail


When just replying to a message without changing Subject, alpine
indeed keeps the headers just fine.


Given that it normally leaves the headers intact, and that the email client is 
still entirely usable even if you do hit this bug, I'm lowering the severity as 
it most certainly isn't RC worthy.



~Unit 193
Unit193 @ freenode
Unit193 @ OFTC

-BEGIN PGP SIGNATURE-

iQIcBAEBCQAGBQJdaZjPAAoJEFAB4bCao3RLlewP/i0i1bFwjq+ApIDXE8vI3rRe
SqYn35l+v3o/RENmHIBJ+9DkJaRLkwwWr003Aeiup+/WdPzFV3QwWZDMoUQe9gu6
TwKwlIoA6dBscN448oUTK803B5uzRtOfFG0RVwes4EQD2qyh6BfyzlSrUtxEUWNB
/SCenJ97B5pwH1NDMvgstVqctGlLrGXzGaiNbUxyWCYn2ZsJ2ovi8No5pOsvuOLV
qHz4wxCa6VgYBdIVqUkVfZheihjQbZQ1I53X0+CvfyCB3KE41pb4NLANd06t+YAd
m6Ygnu3SNk5ZN4+tcF0d7i3N0BH7zCqRGAQ/U2KjBcfDuMOndjUvNnk39/RZFkAA
4S4JqSaEgc8guuXzjJt6xg4hkAx8YGDJye1+l8D2vcs6hhhVYmeywMAQmV+m2vh3
x0WO3LLW8VJJPGjPCl9kYYNXv50+9Iq3YR/kIWtXrQ6sqWHST7grqnzFoY3/aWRm
6+vmKgUO1u4n/BOGv9tyAlTvqpe1lCzmbras8uy9x1qCxFtof2PC0OFLMg5Ro3vO
Yj8026GBBTk26BzRExrToBjGMFazASTHMZsfftaCpEIF/AREmqui7QQkW2DnFfr6
7zrW4ysB+Gw63kMUFcRhpuFzZY4obpFINAEjuUCR3obPegc4X/UMsRi/eXnSfEta
IYWC8wh3OJLVyINQMJrL
=+IvI
-END PGP SIGNATURE-

Processed: Re: alpine: replies lose In-Reply-To and References headers

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #923481 [alpine] alpine: replies lose In-Reply-To and References headers
Severity set to 'important' from 'serious'

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

Processed: affects 938035

[Debian Bug Tracking System]

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

> affects 938035 tritium
Bug #938035 [src:python-plwm] python-plwm: Python2 removal in sid/bullseye
Added indication that 938035 affects tritium
> thanks
Stopping processing here.

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

Processed: severity of 938035 is serious

[Debian Bug Tracking System]

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

> severity 938035 serious
Bug #938035 [src:python-plwm] python-plwm: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 937662 is serious

[Debian Bug Tracking System]

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

> severity 937662 serious
Bug #937662 [src:python-contract] python-contract: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: affects 937632

[Debian Bug Tracking System]

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

> affects 937632 libkate
Bug #937632 [src:pythoncard] pythoncard: Python2 removal in sid/bullseye
Added indication that 937632 affects libkate
> thanks
Stopping processing here.

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

Processed: severity of 937632 is serious

[Debian Bug Tracking System]

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

> severity 937632 serious
Bug #937632 [src:pythoncard] pythoncard: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: affects 937662

[Debian Bug Tracking System]

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

> affects 937662 tritium
Bug #937662 [src:python-contract] python-contract: Python2 removal in 
sid/bullseye
Added indication that 937662 affects tritium
> thanks
Stopping processing here.

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

Bug#938959: marked as done (nettle: uncoordinated FTBFS transition)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 20:46:26 +
with message-id 
and subject line Bug#938959: fixed in nettle 3.5.1+really3.4.1-1
has caused the Debian Bug report #938959,
regarding nettle: uncoordinated FTBFS transition
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.)


-- 
938959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nettle
Version: 3.5.1-1
Severity: serious
Tags: ftbfs

nettle 3.5.1-1 does an soname bump. This was not coordinated with the
release team (according to Ivo de Decker) and there is no transition
bug. It also ftbfs everywhere but amd64 due to symbol differences. It
seems a bit like the nettle upload should have gone to experimental
where it would have been appropriate.

I suggest that you upload a revert to unstable asap, upload this package
to experimental and file a transition bug against release.d.o to acquire
a transition slot.

Helmut
--- End Message ---
--- Begin Message ---
Source: nettle
Source-Version: 3.5.1+really3.4.1-1

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

Debian distribution maintenance software
pp.
Magnus Holmgren  (supplier of updated nettle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Aug 2019 21:37:04 +0200
Source: nettle
Binary: libhogweed4 libhogweed4-dbgsym libnettle6 libnettle6-dbgsym nettle-bin 
nettle-bin-dbgsym nettle-dev
Architecture: source amd64
Version: 3.5.1+really3.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Magnus Holmgren 
Changed-By: Magnus Holmgren 
Description:
 libhogweed4 - low level cryptographic library (public-key cryptos)
 libnettle6 - low level cryptographic library (symmetric and one-way cryptos)
 nettle-bin - low level cryptographic library (binary tools)
 nettle-dev - low level cryptographic library (development files)
Closes: 938959
Changes:
 nettle (3.5.1+really3.4.1-1) unstable; urgency=low
 .
   * Revert to 3.4.1 to acquire a transition slot (Closes: #938959). Not
 building with --enable-fat either because symbol differences between
 platforms need to be checked.
Checksums-Sha1:
 09749d1df4ebad2e826766310b5d36824a58de54 2098 nettle_3.5.1+really3.4.1-1.dsc
 56a81ed4a8d35489d8bddd99d5262fe3958a52b4 1947053 
nettle_3.5.1+really3.4.1.orig.tar.gz
 db3239b3b9b6a6fafe1a7c5cca22ff7c59e85249 20180 
nettle_3.5.1+really3.4.1-1.debian.tar.xz
 4271763133de7645c972207152c6812f90d97a3f 202456 
libhogweed4-dbgsym_3.5.1+really3.4.1-1_amd64.deb
 b56f4b6a29714fbfeb5c0eaacbc5856bcc9ab784 141200 
libhogweed4_3.5.1+really3.4.1-1_amd64.deb
 3ff7e4534bdcdd159a07f3cb4b981b397dd22b2c 219496 
libnettle6-dbgsym_3.5.1+really3.4.1-1_amd64.deb
 f7b4432953ee7a81f8ee21f4f24d5c4f53bed150 215264 
libnettle6_3.5.1+really3.4.1-1_amd64.deb
 258e40d0bc680af0f1e1d2302a54dcfc9f3727b9 170116 
nettle-bin-dbgsym_3.5.1+really3.4.1-1_amd64.deb
 8a3a4828defdf6db55f4dab50bbb47c9c134146e 25112 
nettle-bin_3.5.1+really3.4.1-1_amd64.deb
 f96a92cbca353e5541b5a8a754e1df7275cd1424 1077700 
nettle-dev_3.5.1+really3.4.1-1_amd64.deb
 02980c9c3b9ac17e0e885a7902710d6735e66381 8517 
nettle_3.5.1+really3.4.1-1_amd64.buildinfo
Checksums-Sha256:
 59c1eaffa5b79338e202cfb816861d4c720516d589437edf327d834262600674 2098 
nettle_3.5.1+really3.4.1-1.dsc
 f941cf1535cd5d1819be5ccae5babef01f6db611f9b5a777bae9c7604b8a92ad 1947053 
nettle_3.5.1+really3.4.1.orig.tar.gz
 0d3c6c5fa8bda688262b9bec88a230653fa1de4d9183ea2968910d59455bc5b9 20180 
nettle_3.5.1+really3.4.1-1.debian.tar.xz
 68698c61d4500e981e48697b3abb545474fcb55ac8d1aedb7bedb158e41e1a69 202456 
libhogweed4-dbgsym_3.5.1+really3.4.1-1_amd64.deb
 eecf98433a8fd279fd3d0beae871ccf80609997d919080b00901b7e08371b730 141200 
libhogweed4_3.5.1+really3.4.1-1_amd64.deb
 6bf07f9959e564be733ea5dd9b10607bc9ce1d843e9bfbd8a38acd6eaabf4308 219496 
libnettle6-dbgsym_3.5.1+really3.4.1-1_amd64.deb
 917aa06391a018453db89b3bc724841349b6856c6b037f515de8938e95834434 215264 
libnettle6_3.5.1+really3.4.1-1_amd64.deb
 

Processed: block 937842 with 937542 927101 936168 927100 936216 927131 936668 935677 936580 927132 927134 936724 927135 938348 927136 938877

[Debian Bug Tracking System]

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

> block 937842 with 937542 927101 936168 927100 936216 927131 936668 935677 
> 936580 927132 927134 936724 927135 938348 927136 938877
Bug #937842 [src:python-ipaddr] python-ipaddr: Python2 removal in sid/bullseye
937842 was not blocked by any bugs.
937842 was not blocking any bugs.
Added blocking bug(s) of 937842: 936216, 935677, 927131, 938348, 936580, 
937542, 927100, 927136, 936668, 927101, 936168, 927134, 927132, 938877, 936724, 
and 927135
> thanks
Stopping processing here.

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

Processed: block 937542 with 927100 936216 927137 938724

[Debian Bug Tracking System]

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

> block 937542 with 927100 936216 927137 938724
Bug #937542 [src:pyspf] pyspf: Python2 removal in sid/bullseye
937542 was not blocked by any bugs.
937542 was blocking: 936163
Added blocking bug(s) of 937542: 936216, 927137, 938724, and 927100
> thanks
Stopping processing here.

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

Bug#927418: sysdig-dkms: Does not compile with Kernel 5.0 from Debian Experimental

[Sven Eckelmann]

Control: tag -1 + patch

On Fri, 19 Apr 2019 13:12:44 +0200 Axel Beckert  wrote:
[...]
> DKMS make.log for sysdig-0.24.1 for kernel 5.0.0-trunk-amd64 (x86_64)
> Fri Apr 19 13:03:01 CEST 2019
> make: Entering directory '/usr/src/linux-headers-5.0.0-trunk-amd64'
>   CC [M]  /var/lib/dkms/sysdig/0.24.1/build/main.o
>   CC [M]  /var/lib/dkms/sysdig/0.24.1/build/dynamic_params_table.o
>   CC [M]  /var/lib/dkms/sysdig/0.24.1/build/fillers_table.o
>   CC [M]  /var/lib/dkms/sysdig/0.24.1/build/flags_table.o
>   CC [M]  /var/lib/dkms/sysdig/0.24.1/build/ppm_events.o
> /var/lib/dkms/sysdig/0.24.1/build/ppm_events.c: In function 
> ‘ppm_copy_from_user’:
> /var/lib/dkms/sysdig/0.24.1/build/ppm_events.c:89:48: error: macro 
> "access_ok" passed 3 arguments, but takes just 2
>   if (likely(ppm_access_ok(VERIFY_READ, from, n)))
> ^
> In file included from 
> /usr/src/linux-headers-5.0.0-trunk-common/include/linux/export.h:45,
>  from 
> /usr/src/linux-headers-5.0.0-trunk-common/include/linux/linkage.h:7,
>  from 
> /usr/src/linux-headers-5.0.0-trunk-common/arch/x86/include/asm/cache.h:5,
>  from 
> /usr/src/linux-headers-5.0.0-trunk-common/include/linux/cache.h:6,
>  from 
> /usr/src/linux-headers-5.0.0-trunk-common/include/linux/time.h:5,
>  from 
> /usr/src/linux-headers-5.0.0-trunk-common/include/linux/compat.h:10,
>  from /var/lib/dkms/sysdig/0.24.1/build/ppm_events.c:12:
> /var/lib/dkms/sysdig/0.24.1/build/ppm_events.c:49:23: error: ‘access_ok’ 
> undeclared (first use in this function); did you mean ‘access_flags’?

The API incompatibilities with Linux 5.0 and 5.1 can be fixed with the 
attached patch. It should now be possible to build the kernel module even 
against Linux 5.3(-rc5).

Kind regards,
SvenFrom: Sven Eckelmann 
Date: Fri, 30 Aug 2019 21:16:27 +0200
Subject: Fix build of sysdig-dkms against Linux 5.0-5.3 (Closes: #927418)

diff --git a/debian/patches/ftbfs-linux-5.0.patch b/debian/patches/ftbfs-linux-5.0.patch
new file mode 100644
index ..af8a22ceaaa77a5a92d8592595590b7cac6419e4
--- /dev/null
+++ b/debian/patches/ftbfs-linux-5.0.patch
@@ -0,0 +1,36 @@
+From: Colin Ian King 
+Date: Thu, 31 Jan 2019 10:54:00 +
+Subject: Update for change to access_ok in Linux 5.0
+
+Linux 5.0 removed the 1st argument 'type' from the access_ok macro.
+Update the ppm_access_ok() macro to cater for this change for Linux
+5.0
+
+Bug: https://github.com/draios/sysdig/issues/1299
+sysdig-CLA-1.0-signed-off-by: Colin Ian King 
+
+Signed-off-by: Colin Ian King 
+
+Bug-Debian: https://bugs.debian.org/927418
+Origin: backport, https://github.com/draios/sysdig/commit/2c8f0263382bf64800faec5fba5cc3e005d9fb1e
+---
+ driver/ppm_events.c | 6 +-
+ 1 file changed, 5 insertions(+), 1 deletion(-)
+
+diff --git a/driver/ppm_events.c b/driver/ppm_events.c
+index a101b7c..07c96c3 100644
+--- a/driver/ppm_events.c
 b/driver/ppm_events.c
+@@ -46,7 +46,11 @@ or GPL2.txt for full copies of the license.
+ #ifdef access_ok_noprefault
+ #define ppm_access_ok access_ok_noprefault
+ #else
+-#define ppm_access_ok access_ok
++#if LINUX_VERSION_CODE < KERNEL_VERSION(5, 0, 0)
++#define ppm_access_ok(type, addr, size)	access_ok(type, addr, size)
++#else
++#define ppm_access_ok(type, addr, size)	access_ok(addr, size)
++#endif
+ #endif
+ 
+ extern bool g_tracers_enabled;
diff --git a/debian/patches/ftbfs-linux-5.1.patch b/debian/patches/ftbfs-linux-5.1.patch
new file mode 100644
index ..77b39a6e39a9253fd76cea2d6d8c17a520b85e72
--- /dev/null
+++ b/debian/patches/ftbfs-linux-5.1.patch
@@ -0,0 +1,1594 @@
+From: Nathan Baker <7409217+natha...@users.noreply.github.com>
+Date: Thu, 23 May 2019 09:59:06 -0400
+Subject: Changes to build the kmod with 5.1 kernels [SMAGENT-1643] (#1413)
+
+[SMAGENT-1643] Changes to build the kmod with 5.1 kernels
+
+* The syscall_get_arguments function changed its parameters.
+* The mmap symbols changed header locations
+* Wrapped the kernel version check in a function
+
+Bug-Debian: https://bugs.debian.org/927418
+Origin: backport, https://github.com/draios/sysdig/commit/a6ab1e66fc05a02178e051ea2441633996d5871e
+---
+ driver/main.c |  21 ++-
+ driver/ppm.h  |   2 +
+ driver/ppm_events.c   |  47 ---
+ driver/ppm_fillers.c  | 333 --
+ driver/ppm_flag_helpers.h |   3 +-
+ 5 files changed, 221 insertions(+), 185 deletions(-)
+
+diff --git a/driver/main.c b/driver/main.c
+index b2e320b..adce675 100644
+--- a/driver/main.c
 b/driver/main.c
+@@ -216,6 +216,15 @@ do {\
+ 		pr_info(fmt, ##__VA_ARGS__);			\
+ } while (0)
+ 
++inline void ppm_syscall_get_arguments(struct task_struct *task, struct pt_regs *regs, unsigned long *args)
++{
++#if (LINUX_VERSION_CODE < KERNEL_VERSION(5, 1, 0))
++

Processed: Re: sysdig-dkms: Does not compile with Kernel 5.0 from Debian Experimental

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #927418 [sysdig-dkms] sysdig-dkms: module does not compile with Kernel 5.x
Ignoring request to alter tags of bug #927418 to the same tags previously set

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

Processed: Re: sysdig-dkms: Does not compile with Kernel 5.0 from Debian Experimental

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #927418 [sysdig-dkms] sysdig-dkms: module does not compile with Kernel 5.x
Added tag(s) patch.

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

Bug#938984: librust-pangocairo-sys-dev : Depends: librust-cairo-sys-rs-0.7+default-dev but it is not installable

[Steve Langasek]

Source: rust-pangocairo-sys
Version: 0.8.0-1
Severity: serious
Tags: sid
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

Hi Andrej,

The rust-pangocairo-sys package is uninstallable in unstable because it
depends on obsoleted versions of several other packages lower down the
stack.

The following packages have unmet dependencies:
 librust-pangocairo-sys-dev : Depends: librust-cairo-sys-rs-0.7+default-dev but 
it is not installable
  Depends: librust-glib-sys-0.7+default-dev but it 
is not installable
  Depends: librust-pango-sys-0.7+default-dev but it 
is not installable
E: Unable to correct problems, you have held broken packages.

This blocks migration of a number of other packages, and presumably requires
an update to a new upstream version of pangocairo-sys.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#875088: marked as done ([phonon-backend-vlc] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 19:20:49 +
with message-id 
and subject line Bug#875088: fixed in phonon-backend-vlc 0.10.3-2
has caused the Debian Bug report #875088,
regarding [phonon-backend-vlc] Future Qt4 removal from 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.)


-- 
875088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phonon-backend-vlc
Version: 0.9.0-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: phonon-backend-vlc
Source-Version: 0.10.3-2

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
phonon-backend-vlc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Aug 2019 16:08:05 -0300
Source: phonon-backend-vlc
Architecture: source
Version: 0.10.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 875088
Changes:
 phonon-backend-vlc (0.10.3-2) unstable; urgency=medium
 .
   * Drop Qt 4 support (Closes: #875088).
   * Fail the build if there are missing files not installed.
   * Remove dbg migration command.
   * Switch to debhelper compatibility 12.
Checksums-Sha1:
 56f88cc9504ddd96c4966628a95babeb1cd84bc6 2427 phonon-backend-vlc_0.10.3-2.dsc
 e99a28db42d3b81cb1450429aa50b1e9c3782ead 9864 
phonon-backend-vlc_0.10.3-2.debian.tar.xz
 00fc9e08b68286df3d0e84122005a85e8e99f1df 5750 
phonon-backend-vlc_0.10.3-2_source.buildinfo
Checksums-Sha256:
 e0169557e74fed2dc4c9c6d145b6364813cf1d8c639199dcb230bd5d7abf4551 2427 
phonon-backend-vlc_0.10.3-2.dsc
 58934772d963e0ee7c11f8882da034b2bdb8cac522356e609c5e7f459c8c8de9 9864 
phonon-backend-vlc_0.10.3-2.debian.tar.xz
 cd885c8bac271a899cb78effa1fed433ec21b49075c75f4ae3fae833dc1b739d 5750 
phonon-backend-vlc_0.10.3-2_source.buildinfo
Files:
 30b9355db3b6c3a96a9343c8958b2b74 2427 sound optional 
phonon-backend-vlc_0.10.3-2.dsc
 79a65608b796acb19a78b0c8c0ec2f9f 9864 sound optional 
phonon-backend-vlc_0.10.3-2.debian.tar.xz
 d00928400c4efbf822bdcc59cd774293 5750 sound 

Processed: fixed in salsa MR

[Debian Bug Tracking System]

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

> tags 935294 + fixed-upstream patch
Bug #935294 [src:realmd] realmd: FTBFS on amd64
Added tag(s) fixed-upstream and patch.
> forwarded 935294 https://salsa.debian.org/utopia-team/realmd/merge_requests/1
Bug #935294 [src:realmd] realmd: FTBFS on amd64
Set Bug forwarded-to-address to 
'https://salsa.debian.org/utopia-team/realmd/merge_requests/1'.
> thanks
Stopping processing here.

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

Bug#936115: marked as done (alacarte: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 19:04:04 +
with message-id 
and subject line Bug#936115: fixed in alacarte 3.11.91-5
has caused the Debian Bug report #936115,
regarding alacarte: Python2 removal in sid/bullseye
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.)


-- 
936115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:alacarte
Version: 3.11.91-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:alacarte

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: alacarte
Source-Version: 3.11.91-5

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated alacarte 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: Fri, 30 Aug 2019 21:45:44 +0300
Source: alacarte
Architecture: source
Version: 3.11.91-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Dmitry Shachnev 
Closes: 936115
Changes:
 alacarte (3.11.91-5) unstable; urgency=medium
 .
   * Port to Python 3. (Closes: #936115)
   * Add Homepage URL.
   * Bump Standards-Version to 4.4.0, no changes needed.
Checksums-Sha1:
 5551f78053388f78c9a0a9ae67421ade0f1ddf9f 2225 alacarte_3.11.91-5.dsc
 7946fcf1e95fb634630e18cf713ea70c31671a1c 8584 alacarte_3.11.91-5.debian.tar.xz
 c804ef103fdd3852f91a451c8203c3aae43ef86b 8378 
alacarte_3.11.91-5_source.buildinfo
Checksums-Sha256:
 cf8f1905f93fac37ded89abbedbe52d7af71974977531e7b09c7f0ed5c8e0f9e 2225 
alacarte_3.11.91-5.dsc
 22d4cc63906dba59629c925674cac51780d181545ca78614499ec538b623 8584 
alacarte_3.11.91-5.debian.tar.xz
 304e1cf033ca765d007bd9ec2c37e79c10ea975f6134ae48775c224f65e233ae 8378 
alacarte_3.11.91-5_source.buildinfo

Bug#938982: xcffib: internet connection during build

[Gianfranco Costamagna]

Source: xcffib
Version: 0.8.1-0.3
Severity: serious

hello, looks like the package is attempting internet connection during build 
(you can see e.g. on Ubuntu builds)

see build log:
make xcffib
make[2]: Entering directory '/<>'
cabal --config-file=./cabal.config new-run exe:xcffibgen -- --input 
/usr/share/xcb --output ./xcffib
Warning: Unknown/unsupported 'ghc' version detected (Cabal 2.2.0.1 supports
'ghc' version < 8.5): /usr/bin/ghc is version 8.6.5
Warning: Caught exception during _mirrors lookup:user error (res_query(3)
failed)
Warning: No mirrors found for http://hackage.haskell.org/
dieVerbatim: user error (cabal: Couldn't establish HTTP connection. Possible 
cause: HTTP proxy server
is down.
)
make[2]: *** [Makefile:16: xcffib] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:8: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:16: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


cheers,

Gianfranco

Bug#875087: marked as done ([phonon-backend-gstreamer] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 18:36:41 +
with message-id 
and subject line Bug#875087: fixed in phonon-backend-gstreamer 4:4.9.1-2
has caused the Debian Bug report #875087,
regarding [phonon-backend-gstreamer] Future Qt4 removal from 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.)


-- 
875087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phonon-backend-gstreamer
Version: 4:4.9.0-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: phonon-backend-gstreamer
Source-Version: 4:4.9.1-2

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
phonon-backend-gstreamer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Aug 2019 15:10:32 -0300
Source: phonon-backend-gstreamer
Architecture: source
Version: 4:4.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 875087
Changes:
 phonon-backend-gstreamer (4:4.9.1-2) unstable; urgency=medium
 .
   * Drop Qt 4 version. Heavily based on Moritz Mühlenhoff's patch, thanks!
 (Closes: #875087).
   * Switch to debhelper compat 12.
 - Override dh_missing instead of dh_install to call --fail-missing.
   * Drop dbg migration command, it is no longer necessary.
Checksums-Sha1:
 98dee878421d5d25c041842987fbd2f7d4ee31d1 2639 
phonon-backend-gstreamer_4.9.1-2.dsc
 49165635a522b20f94292bbf7e27e13da635e72b 9680 
phonon-backend-gstreamer_4.9.1-2.debian.tar.xz
 08238ea96dadd7ca8d9d92d92edeb73db19ef2a0 5810 
phonon-backend-gstreamer_4.9.1-2_source.buildinfo
Checksums-Sha256:
 9ab219b99d1e10b44e1ac186b42b09779922c0c7cfe23b35873d8eb0c5f2880d 2639 
phonon-backend-gstreamer_4.9.1-2.dsc
 ed26f039cab5db1f45126c57c0e49664bbe92b5a3d863c5560b10b8bfbe82477 9680 
phonon-backend-gstreamer_4.9.1-2.debian.tar.xz
 696f49ab6d676246f7a9925975cc8f157b1c9a887b0901928907a4384de64686 5810 
phonon-backend-gstreamer_4.9.1-2_source.buildinfo
Files:
 d4a6fad17421e859134af1430746fb72 2639 sound optional 

Bug#931609: marked as done (Update release names after the Buster release.)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 18:32:52 +
with message-id 
and subject line Bug#931609: fixed in reportbug 7.1.7+deb9u3
has caused the Debian Bug report #931609,
regarding Update release names after the Buster release.
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.)


-- 
931609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.5.2+deb10u1
Severity: important

Hi,

Please apply the attached patch to fix reportbug regarding the new release
name mappings. Please allow me to NMU this at least in Buster, if you
don't have time to upload yourself, as IMO, this is a bit critical. Indeed,
I tried to do:

"reportbug -b release.debian.org cloudkitty"

selected stretch-pu, thinking I'll fix later on, but reportbug just crashed
on me trying to fetch version numbers, as cloudkitty isn't in Stretch. This
isn't nice at all... :)

Cheers,

Thomas Goirand (zigo)
diff --git a/debian/changelog b/debian/changelog
index a8c7b04..8b167c9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+reportbug (7.5.2+deb10u1) buster; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix release names.
+
+ -- Thomas Goirand   Mon, 08 Jul 2019 10:22:29 +0200
+
 reportbug (7.5.2) unstable; urgency=medium
 
   * bin/reportbug
diff --git a/reportbug/__init__.py b/reportbug/__init__.py
index 5158a19..aecbd4f 100644
--- a/reportbug/__init__.py
+++ b/reportbug/__init__.py
@@ -25,7 +25,7 @@ SOFTWARE."""
 __all__ = ['bugreport', 'utils', 'urlutils', 'checkbuildd', 'checkversions',
'debbugs', 'exceptions', 'submit', 'tempfile']
 
-VERSION_NUMBER = "7.5.2"
+VERSION_NUMBER = "7.5.2+deb10u1"
 
 VERSION = "reportbug " + VERSION_NUMBER
 COPYRIGHT = VERSION + '\nCopyright (C) 1999-2008 Chris Lawrence 
' + \
diff --git a/reportbug/utils.py b/reportbug/utils.py
index 545504d..98e089a 100644
--- a/reportbug/utils.py
+++ b/reportbug/utils.py
@@ -93,11 +93,11 @@ fhs_directories = ['/', '/usr', '/usr/share', '/var', 
'/usr/X11R6',
'/usr/man', '/usr/doc', '/usr/bin']
 
 # A map between codenames and suites
-CODENAME2SUITE = {'wheezy': 'oldoldstable',
-'jessie': 'oldstable',
-'stretch': 'stable',
-'buster': 'testing',
-'bullseye': 'next-testing',
+CODENAME2SUITE = {'jessie': 'oldoldstable',
+'stretch': 'oldstable',
+'buster': 'stable',
+'bullseye': 'testing',
+'bookworm': 'next-testing',
 'sid': 'unstable',
 'experimental': 'experimental'}
 SUITE2CODENAME = dict([(suite, codename) for codename, suite in 
list(CODENAME2SUITE.items())])
--- End Message ---
--- Begin Message ---
Source: reportbug
Source-Version: 7.1.7+deb9u3

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated reportbug package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 29 Aug 2019 16:19:25 +0200
Source: reportbug
Binary: reportbug python3-reportbug
Architecture: source
Version: 7.1.7+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Reportbug Maintainers 
Changed-By: Andreas Beckmann 
Description:
 python3-reportbug - Python modules for interacting with bug tracking systems
 reportbug  - reports bugs in the Debian distribution
Closes: 931609 932524
Changes:
 reportbug (7.1.7+deb9u3) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Exclude *.pyc from source package.
   * reportbug/utils.py
 - update release names, following Buster releases, patch by Nicolas
   Braud-Santoni; Closes: #932524, #931609
Checksums-Sha1:
 b11e9bf1ed11443ababe8b626e2fca490c37546c 1873 reportbug_7.1.7+deb9u3.dsc
 bde312a55d0a64ce0994b08cf6f6de4e4197dd27 193411 reportbug_7.1.7+deb9u3.tar.bz2
 5cd50fb60127de84403d93b56403898650fe8c97 6046 
reportbug_7.1.7+deb9u3_source.buildinfo
Checksums-Sha256:
 

Bug#938970: marked as done (mpi4py: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 18:21:11 +
with message-id 
and subject line Bug#938970: fixed in mpi4py 3.0.2-13
has caused the Debian Bug report #938970,
regarding mpi4py: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
938970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpi4py
Version: 3.0.2-12
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf debian/rules -- cythonize
make[2]: Entering directory '/<>'
D: removing previously generated by Cython sources
find -iname *.c | xargs grep -l 'Generated by Cython' | xargs -r rm
python3 setup.py build_src
running build_src
cythonizing 'mpi4py.MPI.pyx' -> 'mpi4py.MPI.c'
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:367: FutureWarning: 
Cython directive 'language_level' not set, using 2 for now (Py2). This will 
change in a later release! File: /<>/src/mpi4py/MPI.pxd
  tree = Parsing.p_module(s, pxd, full_module_name)

[... snipped ...]

make[1]: Leaving directory '/<>'
   dh_install -i -O--buildsystem=pybuild
   dh_installdocs -i -O--buildsystem=pybuild
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/<>'
dh_sphinxdoc -ppython-mpi4py-doc
make[1]: Leaving directory '/<>'
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<>'
dh_installchangelogs CHANGES.rst
make[1]: Leaving directory '/<>'
   dh_installman -i -O--buildsystem=pybuild
   dh_installinfo -i -O--buildsystem=pybuild
   dh_python2 -i -O--buildsystem=pybuild
   dh_python3 -i -O--buildsystem=pybuild
E: dh_python3 dh_python3:176: no package to act on (python3-foo or one with 
${python3:Depends} in Depends)
   dh_installinit -i -O--buildsystem=pybuild
   dh_installsystemduser -i -O--buildsystem=pybuild
   dh_perl -i -O--buildsystem=pybuild
   dh_link -i -O--buildsystem=pybuild
   dh_strip_nondeterminism -i -O--buildsystem=pybuild
   debian/rules override_dh_compress
make[1]: Entering directory '/<>'
dh_compress -X.py -X.html -X.css -X.jpg -X.txt -X.js -X.json -X.rtc -X.par 
-X.bin -Xobjects.inv
make[1]: Leaving directory '/<>'
   dh_fixperms -i -O--buildsystem=pybuild
   dh_missing -i -O--buildsystem=pybuild
   debian/rules override_dh_dwz
make[1]: Entering directory '/<>'
echo "dh_dwz is currently deactivated since it generates an error: 
\".debug_line reference above end of section\""
dh_dwz is currently deactivated since it generates an error: ".debug_line 
reference above end of section"
make[1]: Leaving directory '/<>'
   debian/rules override_dh_strip
make[1]: Entering directory '/<>'
dh_strip -ppython-mpi4py --dbg-package=python-mpi4py-dbg
dh_strip: All requested packages have been excluded (e.g. via a Build-Profile 
or due to architecture restrictions).
dh_strip -ppython3-mpi4py --dbg-package=python3-mpi4py-dbg
dh_strip: All requested packages have been excluded (e.g. via a Build-Profile 
or due to architecture restrictions).
# dh_strip seemingly doesn't catch the PEP 3149-style debug names
rm debian/python3-mpi4py/usr/lib/python3*/*-packages/*/*.cpython-3?d*.so
rm: cannot remove 
'debian/python3-mpi4py/usr/lib/python3*/*-packages/*/*.cpython-3?d*.so': No 
such file or directory
make[1]: *** [debian/rules:135: override_dh_strip] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:46: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


See also:

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

The usual recipe for this is to split override_dh_strip
into override_dh_strip-arch and override_dh_strip-indep.

Thanks.
--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 3.0.2-13

We believe that the bug you reported is fixed in the latest version of
mpi4py, 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 938...@bugs.debian.org,

Bug#936115: marked as pending in alacarte

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #936115 in alacarte reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/alacarte/commit/afc02a456674ca5008e8324e8746d0e4394d63d6


Port to Python 3.

Closes: #936115.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/936115

Processed: Bug#936115 marked as pending in alacarte

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #936115 [src:alacarte] alacarte: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#938961: aufs: needs update for new linux

[Jan Luca Naumann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I will take care of the update next week. This week I'm on holidays
without a real computer.

Sorry for the delay and best
Jan

Am 30.08.19 um 17:26 schrieb Ivo De Decker:
> package: aufs severity: serious tags: bullseye sid
> 
> Hi,
> 
> The version of aufs in testing and unstable build-depends on 
> linux-kbuild-4.19, which is no longer availabe in testing.
> 
> Thanks,
> 
> Ivo
> 
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEwNbeTg2NJIWRcwSlfhHX8Rn5cbsFAl1pZfgACgkQfhHX8Rn5
cbvOpw//WnObpPyNiJXd9UmIoC6eLI8MNDc/tGrwhWOyssR05sEOM56o4JkyaohF
tIkjHYHhypsCxkLtoETkfJjjhpxTxQVHs2NiDjGmo/S4zEwk/OTKZMOp8wyWNRhP
j8PvhcBz4jplGwF3RSsIt4wqXdygIgjG7mogzXtsbg+T6WOzQE583xZ3syUs/dbH
jJ4Jo2/BuZKO54tEd8WvDHDsL9v0fZlhv6wATCe9buMAlmSPtAaYp986nDLsvZIr
Gc7TXf02+CVqZ4GsuUNBIIHLuvP6zf6mryIIk5UsyCfQNRAZca4qH/UR1+bd5ZI3
NRJmYuUqtODwW6oh3p3ckoZ2ZY7gdljmAAiciWPxtkXpJAootlS39TmCePbK08CG
FecA2nSO8AxIAP5cm79lXkiUA7MRlwAvWmDfUcpxvjWosynsERy0Jp1b5zDv/yRY
bo4wnHopQHOcPwMsUdIoGWMjjRO6pp53I/nZM5TjHpnLFNoW8KJKd8udfbQCSvXx
m2dpbCX/QFFd7vQNeaXWM5YsiUvc6EHyFPCOaucxvu/W5IALL6mAqSGbnrtBvYKq
tn4bbyuOkLfvi/5aesEPpClWGUL+W9u6seStYqjOiuvFa7yG2LUBiV3iyJa+7zlL
Mo2JS8lpibru7Ue0VcgEIUpdzQTRfjfWFqtvDKqoEzt7AD+J2Ts=
=hISk
-END PGP SIGNATURE-

Bug#938970: marked as pending in mpi4py

[Drew Parsons]

Control: tag -1 pending

Hello,

Bug #938970 in mpi4py reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/science-team/mpi4py/commit/8182d9e9c9d75cf4b591f4d951ed234626f0c070


fix override_dh_strip to ignore missing debug .so files

not installed in doc arch-indep builds

Closes: #938970.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938970

Processed: Bug#938970 marked as pending in mpi4py

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #938970 [src:mpi4py] mpi4py: FTBFS when built with dpkg-buildpackage -A
Added tag(s) pending.

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

Bug#935496: Fails to install: Invalid action '-p'

[Michael Biebl]

Am 30.08.19 um 11:04 schrieb Simon McVittie:
> Control: tags -1 + bullseye sid
> 
> On Fri, 23 Aug 2019 at 10:04:28 +0200, Michael Biebl wrote:
>> Setting up fuse (2.9.9-1) ...
>> dpkg: error processing package fuse (--configure):
>>  installed fuse package post-installation script subprocess returned error 
>> exit status 1
> ...
>> # udevadm test --action -p /devices/virtual/misc/fuse
>> Invalid action '-p'
> 
> Similar to the equivalent fuse3 bug #934293, this seems to be a regression
> since buster: the same binary package installs OK on buster. Maybe
> udevadm became more strict about its parameter parsing?

I'm currently investigating, whether this is a regression in udevadm or not

That said:

> Similar to fuse3, it would be helpful if the maintainer script had less
> "> /dev/null 2>&1" so that error messages would appear.
> 
>> I'm not exactly sure what this code is supposed to achieve.
>> Since fuse no longer ships its own udev rules, maybe it can be dropped
>> altogether?
> 
> Or if the postinst is still necessary, maybe fuse3 could take over the
> fuse binary package name for bullseye (with a transitional package) so that
> bugs like this one don't need to be fixed in both places?

That unhelpful redirection aside, that maintainer scripts code (in
fuse/fuse3) looks fishy and should be carefully reviewed if it is
actually still needed and if so, add a comment or two.


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



signature.asc
Description: OpenPGP digital signature

Bug#938970: mpi4py: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: src:mpi4py
Version: 3.0.2-12
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf debian/rules -- cythonize
make[2]: Entering directory '/<>'
D: removing previously generated by Cython sources
find -iname *.c | xargs grep -l 'Generated by Cython' | xargs -r rm
python3 setup.py build_src
running build_src
cythonizing 'mpi4py.MPI.pyx' -> 'mpi4py.MPI.c'
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:367: FutureWarning: 
Cython directive 'language_level' not set, using 2 for now (Py2). This will 
change in a later release! File: /<>/src/mpi4py/MPI.pxd
  tree = Parsing.p_module(s, pxd, full_module_name)

[... snipped ...]

make[1]: Leaving directory '/<>'
   dh_install -i -O--buildsystem=pybuild
   dh_installdocs -i -O--buildsystem=pybuild
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/<>'
dh_sphinxdoc -ppython-mpi4py-doc
make[1]: Leaving directory '/<>'
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<>'
dh_installchangelogs CHANGES.rst
make[1]: Leaving directory '/<>'
   dh_installman -i -O--buildsystem=pybuild
   dh_installinfo -i -O--buildsystem=pybuild
   dh_python2 -i -O--buildsystem=pybuild
   dh_python3 -i -O--buildsystem=pybuild
E: dh_python3 dh_python3:176: no package to act on (python3-foo or one with 
${python3:Depends} in Depends)
   dh_installinit -i -O--buildsystem=pybuild
   dh_installsystemduser -i -O--buildsystem=pybuild
   dh_perl -i -O--buildsystem=pybuild
   dh_link -i -O--buildsystem=pybuild
   dh_strip_nondeterminism -i -O--buildsystem=pybuild
   debian/rules override_dh_compress
make[1]: Entering directory '/<>'
dh_compress -X.py -X.html -X.css -X.jpg -X.txt -X.js -X.json -X.rtc -X.par 
-X.bin -Xobjects.inv
make[1]: Leaving directory '/<>'
   dh_fixperms -i -O--buildsystem=pybuild
   dh_missing -i -O--buildsystem=pybuild
   debian/rules override_dh_dwz
make[1]: Entering directory '/<>'
echo "dh_dwz is currently deactivated since it generates an error: 
\".debug_line reference above end of section\""
dh_dwz is currently deactivated since it generates an error: ".debug_line 
reference above end of section"
make[1]: Leaving directory '/<>'
   debian/rules override_dh_strip
make[1]: Entering directory '/<>'
dh_strip -ppython-mpi4py --dbg-package=python-mpi4py-dbg
dh_strip: All requested packages have been excluded (e.g. via a Build-Profile 
or due to architecture restrictions).
dh_strip -ppython3-mpi4py --dbg-package=python3-mpi4py-dbg
dh_strip: All requested packages have been excluded (e.g. via a Build-Profile 
or due to architecture restrictions).
# dh_strip seemingly doesn't catch the PEP 3149-style debug names
rm debian/python3-mpi4py/usr/lib/python3*/*-packages/*/*.cpython-3?d*.so
rm: cannot remove 
'debian/python3-mpi4py/usr/lib/python3*/*-packages/*/*.cpython-3?d*.so': No 
such file or directory
make[1]: *** [debian/rules:135: override_dh_strip] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:46: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


See also:

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

The usual recipe for this is to split override_dh_strip
into override_dh_strip-arch and override_dh_strip-indep.

Thanks.

Bug#910679: cegui-mk2 should build-depend on updated pyside-tools package

[Olek Wojnar]

Based on a conversation with Muammar, I created a Salsa repository under
the Games Team and my updates are in that repository. I don't believe
Muammar has had an opportunity to review my commits but, barring any
requested changes, I believe that this package is ready for upload.

I am only a DM however (and don't even have DM upload rights to CEGUI) so,
as much as I'd like to get this bug closed, I'm afraid that I've done all I
can do.

Muammar: will you be able to review my commits or would you prefer that a
DD member of the Games Team do so?

-Olek

Bug#899010: marked as done (python-ckanclient: Depends on unmaintained python-gdata)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 15:57:58 +
with message-id 
and subject line Bug#938936: Removed package(s) from unstable
has caused the Debian Bug report #899010,
regarding python-ckanclient: Depends on unmaintained python-gdata
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.)


-- 
899010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ckanclient
Version: 0.9-1.1
Severity: important

Dear maintainer,

Your package currently uses python-gdata, which is dead upstream and had no
upstream release since 2013. It also does not support Python 3.

The recommended alternative is using google-api-python-client [1], which is
packaged in Debian as python-googleapi.

I would like to remove python-gdata from Debian Buster, so please update
your package.

[1]: https://github.com/google/google-api-python-client

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.9-1.1+rm

Dear submitter,

as the package ckanclient has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/938936

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#935613: marked as done (qgis: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/icons/hicolor/128x128/mimetypes/qgis-mime.png)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 15:35:42 +
with message-id 
and subject line Bug#935613: fixed in qgis 3.4.11+dfsg-1
has caused the Debian Bug report #935613,
regarding qgis: fails to upgrade from 'stable' to 'sid' - trying to overwrite 
/usr/share/icons/hicolor/128x128/mimetypes/qgis-mime.png
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.)


-- 
935613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qgis
Version: 3.4.10+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../010-qgis_3.4.10+dfsg-1_amd64.deb ...
  Unpacking qgis (3.4.10+dfsg-1) over (2.18.28+dfsg-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-g8AHYp/010-qgis_3.4.10+dfsg-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/share/icons/hicolor/128x128/mimetypes/qgis-mime.png', which is also in 
package qgis-common 2.18.28+dfsg-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)


cheers,

Andreas


qgis_3.4.10+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qgis
Source-Version: 3.4.11+dfsg-1

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated qgis 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: Fri, 30 Aug 2019 14:13:38 +0200
Source: qgis
Architecture: source
Version: 3.4.11+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 935613
Changes:
 qgis (3.4.11+dfsg-1) unstable; urgency=medium
 .
   * Add Breaks/Replaces to fix upgrade from 2.18.18.
 (closes: #935613)
   * Update symbols for other architectures.
   * Move from experimental to unstable.
Checksums-Sha1:
 1721c13890c1560146a2bffcff0ed8d6aec848f4 4655 qgis_3.4.11+dfsg-1.dsc
 f07505fadccc63a32d8cfe505888b93c7725f831 265996 
qgis_3.4.11+dfsg-1.debian.tar.xz
 17392b7168ba33e8f05384aeba11e9bca7a4021d 34988 
qgis_3.4.11+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 dde45f174873426485a4ed7212b643f7dd32f81dde046db118c183c466094e11 4655 
qgis_3.4.11+dfsg-1.dsc
 f4779918d26d02d85a42efc77baa35492d916d699bdec94d697c8a7d78a6bd81 265996 
qgis_3.4.11+dfsg-1.debian.tar.xz
 02b88ce2d0add4eeff2447d86a2ffd61bfe4e96563e008a2e3dde951cf8e9159 34988 
qgis_3.4.11+dfsg-1_amd64.buildinfo
Files:
 12b2b3d7e3c7d3b81207d4a77b4096bb 4655 science optional qgis_3.4.11+dfsg-1.dsc
 1b76e772d9724e83c7d7f26cf54edbe9 265996 science optional 
qgis_3.4.11+dfsg-1.debian.tar.xz
 dd5bfd8dbf00d7c3a89c1100d0c226e1 34988 science optional 
qgis_3.4.11+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl1pORgACgkQZ1DxCuiN
SvGhJhAAzQqCSnz/ZquScBfCQFYQku1RdmMMjrcQF4e2wD2s6k3Y3/6xukzdQo20
HG23OKWMRf2gwqRBtm5LQoYUhosa0XcmfWs/T03G+s5VeYhlQZ9jmY3NEBPBZ8dS
ZQmfp1xvKnstt6zrPz7th+y9zoy3OQgM0pp5O0N4YAiSJubWolEksPzHxPC7kyjX
15fMpefTYtyyukOFWs7Q0F8lodxTnH9NCROszsQmhnJ01jUhGftErMCtoEcRFS3K
qzJssYPYtLh5wzmCGG/i1jmRmCSoN5dp9eewsSCmmi86KXENqbB4zbN8DBQ8DSG5
aKg3dqQHsb6qf3/7y73WoWIyvrxvfoqyJdEbRuL4CQz8putK5MoXP3daFxYpoSGa
0HUrh6a+2iQt0h371GaBQo5uWryaw2IseeBkjb4NgLwRGf/HJWENaCR93oMPhIB/
yUkGsDgyfF5V2HPAO9FlZuvXnoajnGu4HMwMIaAa5xNK7qI0U9yUsrjt1QR0Di3a
43Lh1Gi5UXth0fOr26N8GjDnWp0aRm6jazdLI0o5lcWM2AFPA7PsmFqKoLGyMAAq
hVmF4xWgghwxAHBRywf6YXQPXZXffC3iDSifvjXGCUSuRx/7k+kUDDnk05YDqLRr

Bug#938963: python-pygal: stop depending and shipping python2 packages

[Gianfranco Costamagna]

Source: python-pygal
Version: 2.4.0-2
Severity: serious

Hello, your package depends on python-cairosvg, removed in unstable and testing.

Please update the dependencies to stop using it,

(dropping python2 packages is a release goal, so better stop shipping it? looks 
like it has no rdeps anymore) 

Gianfranco

Bug#938962: user-mode-linux needs update for new linux

[Ivo De Decker]

package: user-mode-linux
severity: serious
tags: bullseye sid

Hi,

The version of user-mode-linux in testing and unstable build-depends on
linux-source-4.19, which is no longer available in testing.

Thanks,

Ivo

~

Bug#938961: aufs: needs update for new linux

[Ivo De Decker]

package: aufs
severity: serious
tags: bullseye sid

Hi,

The version of aufs in testing and unstable build-depends on
linux-kbuild-4.19, which is no longer availabe in testing.

Thanks,

Ivo

Bug#938959: nettle: uncoordinated FTBFS transition

[Helmut Grohne]

Source: nettle
Version: 3.5.1-1
Severity: serious
Tags: ftbfs

nettle 3.5.1-1 does an soname bump. This was not coordinated with the
release team (according to Ivo de Decker) and there is no transition
bug. It also ftbfs everywhere but amd64 due to symbol differences. It
seems a bit like the nettle upload should have gone to experimental
where it would have been appropriate.

I suggest that you upload a revert to unstable asap, upload this package
to experimental and file a transition bug against release.d.o to acquire
a transition slot.

Helmut

Bug#938956: python3-hpilo: missing Breaks+Replaces: python-hpilo

[Andreas Beckmann]

Package: python3-hpilo
Version: 4.3-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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python3-hpilo_4.3-2_all.deb ...
  Unpacking python3-hpilo (4.3-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-hpilo_4.3-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/hpilo_cli', which is also in package 
python-hpilo 4.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-hpilo_4.3-2_all.deb


cheers,

Andreas


python-hpilo=4.3-1_python3-hpilo=4.3-2.log.gz
Description: application/gzip

Bug#922869: libtool: file date issue

[Vincent Lefevre]

On 2019-02-27 16:37:15 +0100, Vincent Lefevre wrote:
> On 2019-02-27 15:12:24 +, Alastair McKinstry wrote:
> > Where did you see this error ? I cannot repeat it. Builds work fine locally
> > / pdebuild, and it appears the buildds ?
> 
> When attempting to rebuild libtool on a machine. A second build
> (after a reboot due to an issue with the nouveau driver that
> made the machine very slow) was fine, though. Still, it appears
> that the test is wrong and can yield failures like there.

Alternatively, it could be due to a kernel bug, as 4.19 is seriously
broken. I haven't noticed any issue with 5.2 yet, so I'll see what I
get with it.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#938955: pylint-doc: missing Breaks+Replaces: pylint (<< 2)

[Andreas Beckmann]

Package: pylint-doc
Version: 2.2.2-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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../pylint-doc_2.2.2-2_all.deb ...
  Unpacking pylint-doc (2.2.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/pylint-doc_2.2.2-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/pylint/examples/custom.py', which is 
also in package pylint 1.9.4-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/pylint-doc_2.2.2-2_all.deb


cheers,

Andreas


pylint=1.9.4-1_pylint-doc=2.2.2-2.log.gz
Description: application/gzip

Bug#935968: marked as done (texlive-latex-extra: Font U/esint/m/n/10.95=esint10 at 10.95pt not loadable: Metric (TFM) file not found)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 15:00:51 +
with message-id 
and subject line Bug#935968: fixed in texlive-extra 2019.20190830-1
has caused the Debian Bug report #935968,
regarding texlive-latex-extra: Font U/esint/m/n/10.95=esint10 at 10.95pt not 
loadable: Metric (TFM) file not found
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.)


-- 
935968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-extra
Version: 2019.20190824-1
Severity: grave
Justification: renders package unusable

After updating:

Unpacking texlive-latex-extra (2019.20190824-1) over (2019.20190710-1) ...

Trying to build documentation:

[…]
(/usr/share/texlive/texmf-dist/tex/latex/inconsolata/t1zi4.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd)

kpathsea: Running mktextfm esint10
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
input esint10
This is METAFONT, Version 2.7182818 (TeX Live 2019/Debian) (preloaded base=mf)

(/usr/share/texlive/texmf-dist/fonts/source/public/esint/esint10.mf)
! Emergency stop.
<*> ...=ljfour; mag:=1; nonstopmode; input esint10

Transcript written on esint10.log.
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input 
esint10' failed.
kpathsea: Appending font creation commands to missfont.log.
(/usr/share/texlive/texmf-dist/tex/latex/esint/uesint.fd)
! Font U/esint/m/n/10.95=esint10 at 10.95pt not loadable: Metric (TFM) file not
 found.
 
   relax
l.94 \end{minipage}

!  ==> Fatal error occurred, no output PDF file produced!
[…]


I’ll try to make an MWE.

##
 List of ls-R files

-rw-r--r-- 1 root root 1997 Aug 28 12:21 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Jul 31 09:21 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Aug 24 08:16 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Aug 24 08:16 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Aug  5 20:05 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Aug 24 08:16 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Aug 24 08:16 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5089 Aug 28 12:20 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Feb 28 15:28 mktex.cnf
-rw-r--r-- 1 root root 475 Aug  5 20:05 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages texlive-latex-extra depends on:
ii  preview-latex-style11.91-2
ii  python 2.7.16-1
ii  python33.7.3-1
ii  tex-common 6.12
ii  texlive-base   2019.20190824-1
ii  texlive-binaries   2019.20190605.51237-2
ii  texlive-latex-recommended  2019.20190824-1
ii  texlive-pictures   2019.20190824-1

Versions of packages texlive-latex-extra recommends:
ii  texlive-fonts-recommended  2019.20190824-1
ii  texlive-plain-generic  2019.20190824-1

Versions of packages texlive-latex-extra suggests:
pn  icc-profiles
ii  libfile-which-perl  1.23-1
pn  libspreadsheet-parseexcel-perl  
pn  python-pygments 
ii  texlive-latex-extra-doc 2019.20190824-1

Versions of packages tex-common depends on:
ii  dpkg  1.19.7
ii  ucf   3.0038+nmu1

Versions of packages tex-common suggests:
ii  debhelper  12.5.3

Versions of packages texlive-latex-extra is related to:
ii  tex-common6.12
ii  texlive-binaries  2019.20190605.51237-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190830-1

We believe that the bug you reported is 

Bug#938953: libhugetlbfs-bin: missing Breaks+Replaces: libhugetlbfs0 (<< 2.21-2)

[Andreas Beckmann]

Package: libhugetlbfs-bin
Version: 2.21-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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libhugetlbfs-bin_2.21-2_amd64.deb ...
  Unpacking libhugetlbfs-bin (2.21-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libhugetlbfs-bin_2.21-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/ld.hugetlbfs', which is also in package 
libhugetlbfs0:amd64 2.21-1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libhugetlbfs-bin_2.21-2_amd64.deb


cheers,

Andreas


libhugetlbfs0=2.21-1+b1_libhugetlbfs-bin=2.21-2.log.gz
Description: application/gzip

Bug#925744: marked as done (libgpiod: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 14:56:50 +
with message-id 
and subject line Bug#925744: fixed in libgpiod 1.4.1-1
has caused the Debian Bug report #925744,
regarding libgpiod: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgpiod
Version: 1.2-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/libgpiod_1.2-3_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
Making install in python
make[4]: Entering directory '/<>/bindings/python'
Making install in .
make[5]: Entering directory '/<>/bindings/python'
make[6]: Entering directory '/<>/bindings/python'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/python3.7/site-packages'
 /bin/bash ../../libtool   --mode=install /usr/bin/install -c   gpiod.la 
'/<>/debian/tmp/usr/lib/python3.7/site-packages'
libtool: warning: relinking 'gpiod.la'
libtool: install: (cd /<>/bindings/python; /bin/bash 
"/<>/libtool"  --tag CC --mode=relink gcc -I../../include/ -Wall 
-Wextra -g -I/usr/include/python3.7m -I/usr/include/python3.7m -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -module -avoid-version -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed -o gpiod.la -rpath /usr/lib/python3.7/site-packages 
gpiod_la-gpiodmodule.lo ../../src/lib/libgpiod.la -lpython3.7m -lcrypt 
-lpthread -ldl -lutil -lm -inst-prefix-dir /<>/debian/tmp)
libtool: relink: gcc -shared  -fPIC -DPIC  .libs/gpiod_la-gpiodmodule.o   
-L/<>/debian/tmp/usr/lib/x86_64-linux-gnu 
-L/usr/lib/x86_64-linux-gnu -lgpiod -lpython3.7m -lcrypt -lpthread -ldl -lutil 
-lm  -g -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now 
-Wl,--as-needed   -Wl,-soname -Wl,gpiod.so -o .libs/gpiod.so
libtool: install: /usr/bin/install -c .libs/gpiod.soT 
/<>/debian/tmp/usr/lib/python3.7/site-packages/gpiod.so
libtool: install: /usr/bin/install -c .libs/gpiod.lai 
/<>/debian/tmp/usr/lib/python3.7/site-packages/gpiod.la
libtool: install: /usr/bin/install -c .libs/gpiod.a 
/<>/debian/tmp/usr/lib/python3.7/site-packages/gpiod.a
libtool: install: chmod 644 
/<>/debian/tmp/usr/lib/python3.7/site-packages/gpiod.a
libtool: install: ranlib 
/<>/debian/tmp/usr/lib/python3.7/site-packages/gpiod.a
libtool: warning: remember to run 'libtool --finish 
/usr/lib/python3.7/site-packages'
make[6]: Nothing to be done for 'install-data-am'.
make[6]: Leaving directory '/<>/bindings/python'
make[5]: Leaving directory '/<>/bindings/python'
Making install in examples
make[5]: Entering directory '/<>/bindings/python/examples'
make[6]: Entering directory '/<>/bindings/python/examples'
make[6]: Nothing to be done for 'install-exec-am'.
make[6]: Nothing to be done for 'install-data-am'.
make[6]: Leaving directory '/<>/bindings/python/examples'
make[5]: Leaving directory '/<>/bindings/python/examples'
make[4]: Leaving directory '/<>/bindings/python'
make[3]: Leaving directory '/<>/bindings'
make[3]: Entering directory '/<>'
make[4]: Entering directory '/<>'
make[4]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
 /usr/bin/install -c -m 644 libgpiod.pc 

Bug#931935: marked as done (openorienteering-mapper: FTBFS with PROJ 6)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 14:56:56 +
with message-id 
and subject line Bug#931935: fixed in openorienteering-mapper 0.8.4-2
has caused the Debian Bug report #931935,
regarding openorienteering-mapper: FTBFS with PROJ 6
to be marked as done.

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

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


-- 
931935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openorienteering-mapper
Version: 0.8.4-1
Severity: important
Tags: upstream patch
User: debian-...@lists.debian.org
Usertags: proj-6

Dear Maintainer,

Your package FTBFS with PROJ 6 from experimental.

The attached patch fixes the issue by defining 
ACCEPT_USE_OF_DEPRECATED_PROJ_API_H.

Note that this is only a temporary workaround, proj_api.h will be
removed in PROJ 7 scheduled for March 2020.

Upstream is aware of the issue, see:

 https://github.com/OpenOrienteering/mapper/issues/1214

Kind Regards,

Bas
diff -Nru openorienteering-mapper-0.8.4/debian/changelog 
openorienteering-mapper-0.8.4/debian/changelog
--- openorienteering-mapper-0.8.4/debian/changelog  2018-12-25 
12:21:02.0 +0100
+++ openorienteering-mapper-0.8.4/debian/changelog  2019-04-13 
18:22:32.0 +0200
@@ -1,3 +1,10 @@
+openorienteering-mapper (0.8.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Define ACCEPT_USE_OF_DEPRECATED_PROJ_API_H for PROJ 6.0.0 compatibility.
+
+ -- Bas Couwenberg   Sat, 13 Apr 2019 18:22:32 +0200
+
 openorienteering-mapper (0.8.4-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru openorienteering-mapper-0.8.4/debian/rules 
openorienteering-mapper-0.8.4/debian/rules
--- openorienteering-mapper-0.8.4/debian/rules  2018-12-25 10:59:12.0 
+0100
+++ openorienteering-mapper-0.8.4/debian/rules  2019-04-13 18:22:30.0 
+0200
@@ -3,6 +3,10 @@
 # output every command that modifies files on the build system.
 #DH_VERBOSE = 1
 
+# Workaround for proj_api.h deprecation in PROJ 6.0.0
+export DEB_CFLAGS_MAINT_APPEND=-DACCEPT_USE_OF_DEPRECATED_PROJ_API_H
+export DEB_CXXFLAGS_MAINT_APPEND=-DACCEPT_USE_OF_DEPRECATED_PROJ_API_H
+
 # see EXAMPLES in dpkg-buildflags(1) and read /usr/share/dpkg/*
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/default.mk
--- End Message ---
--- Begin Message ---
Source: openorienteering-mapper
Source-Version: 0.8.4-2

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated openorienteering-mapper 
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: Fri, 30 Aug 2019 13:35:14 +
Source: openorienteering-mapper
Architecture: source
Version: 0.8.4-2
Distribution: unstable
Urgency: medium
Maintainer: Gaudenz Steinlin 
Changed-By: Graham Inggs 
Closes: 931935
Changes:
 openorienteering-mapper (0.8.4-2) unstable; urgency=medium
 .
   * Define ACCEPT_USE_OF_DEPRECATED_PROJ_API_H for PROJ 6.0.0 compatibility,
 thanks Bas Couwenberg (Closes: #931935)
   * Switch to debhelper 12
   * Set Rules-Requires-Root: no
   * Bump Standards-Version to 4.4.0, no changes
Checksums-Sha1:
 a31d852827ce6184c04a7faeeabbc2eb16d8c10f 2270 
openorienteering-mapper_0.8.4-2.dsc
 fe1b5bf02f103e22d7d36287a0acdb5e186ab521 5520 
openorienteering-mapper_0.8.4-2.debian.tar.xz
Checksums-Sha256:
 dd02d48f095a24af471ddff8c2d13c49cf9239e95b659a36432a99a6a4157370 2270 
openorienteering-mapper_0.8.4-2.dsc
 ad671e46f55082c88a019dd76604317a60642821a82b350f2a2c3a457e500236 5520 
openorienteering-mapper_0.8.4-2.debian.tar.xz
Files:
 fb0c0505ff697f00d8d9a5495797a7fb 2270 graphics optional 
openorienteering-mapper_0.8.4-2.dsc
 950554c3438a33563c2c6d26485800a7 5520 graphics optional 
openorienteering-mapper_0.8.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl1pKCoACgkQr8/sjmac
4cJZBhAAttMmMtzMJkavyZ/7q7ZJHqvi1X/YTdv3kXBg/17sUJkkSTbXLBv7u/T2
WXWe946BSVrisLrydmBAyPTjt3HjY96pja0gPZKEl1hxicgrrinNLgB/JrAo7oWB

Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed

[Jean-Marc LACROIX]

Package: sysvinit
Version: 2.93-8
Severity: grave

Dear maintainers,

It seems there is a dependency issue when installing sysvinit-core as 
indicated in following trace



ansible@pinebook:~$ LC_ALL=C LANG=C LANGUAGE=C sudo apt install 
sysvinit-core

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dconf-service : Depends: default-dbus-session-bus or
  dbus-session-bus
 libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not 
going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.


My configuration is  :
ansible@pinebook:~$ cat /etc/debian_version
10.0

ansible@pinebook:~$ uname -a
Linux pinebook 5.2.5-sunxi64 #5.92 SMP Fri Aug 2 07:51:38 CEST 2019 
aarch64 GNU/Linux



ansible@pinebook:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#"
/etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb 
http://ftp.fr.debian.org/debian buster-backports main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb 
http://ftp.debian.org/debian/ buster main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb 
http://ftp.debian.org/debian/ stretch main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb 
http://security.debian.org buster/updates main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb 
http://ftp.fr.debian.org/debian buster-updates main contrib non-free



ansible@pinebook:~$ cat 
/etc/apt/preferences.d/preferences_debian_v_10_buster* |grep -v "#" 
|grep -v "^$"

Package: dhcpcd5
Pin: release *
Pin-Priority: -1
Package: *systemd*
Pin: release *
Pin-Priority: -1


Package: *
Pin: release o=Debian,l=Debian,n=buster-update
Pin-Priority: 901
Package: *
Pin: release o=Debian,l=Debian,n=buster
Pin-Priority: 900
Package: *
Pin: release o=Debian,l=Debian,n=buster-backports
Pin-Priority: -1
Package: *
Pin: release o=Debian,l=Debian,n=stretch
Pin-Priority: 400
Package: *
Pin: release o=Debian,l=Debian,n=testing
Pin-Priority: -1
Package: *
Pin: release o=Debian,l=Debian,n=unstable
Pin-Priority: -1

ansible@pinebook:~$ dpkg -l |grep -v ii
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| 
État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements

|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version 
Architecture Description

+++-===---===


Thanks in advance for your help
Best regards

Bug#938949: statsmodels: test failures on some architectures

[Rebecca N. Palmer]

Package: statsmodels
Version: 0.9.0-3
Severity: serious
Control: notfound -1 0.8.0-9

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

This might actually be more than one bug.  Some of the armhf ones look 
like #924036, but not all of them.


This may be reduced to non-RC with an xfail *and a user-facing warning* 
(like in #924036's xfail_kalman_armhf.patch).

Processed: statsmodels: test failures on some architectures

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 0.8.0-9
Bug #938949 [statsmodels] statsmodels: test failures on some architectures
There is no source info for the package 'statsmodels' at version '0.8.0-9' with 
architecture ''
Unable to make a source version for version '0.8.0-9'
Ignoring request to alter found versions of bug #938949 to the same values 
previously set

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

Processed: Re: Bug#937448: pygobject: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 936371
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
937448 was not blocked by any bugs.
937448 was not blocking any bugs.
Added blocking bug(s) of 937448: 936371

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

Bug#937448: pygobject: Python2 removal in sid/bullseye

[Simon McVittie]

Control: block -1 by 936371

On Fri, 30 Aug 2019 at 15:24:16 +0200, Andreas Henriksson wrote:
> Reverse-Recommends
> ==
...
> * python-dbus   (for python-gi)
> * python-dbus-tests (for python-gi)

Lots of packages depend on python-dbus, too (see #936371) so I don't
think I am going to have the opportunity to remove that binary package
any time soon.

smcv

Bug#935800: rss2email: AttributeError: module 'html2text' has no attribute 'unescape'

[Samuel Thibault]

Hello,

Baruch Siach, le ven. 30 août 2019 16:41:17 +0300, a ecrit:
> On Wed, Aug 28 2019, Samuel Thibault wrote:
> > Jakub Wilk, le lun. 26 août 2019 12:47:04 +0200, a ecrit:
> >>   return _html2text.unescape(name)
> >>   AttributeError: module 'html2text' has no attribute 'unescape'
> >
> > This seems to be due to the upgrade of python3-html2text to version
> > 2019.8.11-1.
> 
> Upstream fix is:
> 
>   Replacing html2text.unescape with html.unescape
>   
> https://github.com/rss2email/rss2email/commit/81824e25723dcd2936f25f64ebc16f2e8ec9f310
> 
> I applied it locally and it works for me.

That works here too indeed.

Samuel

Processed: block 936371 with 937325 937338 937339 894806 937513 937688 937870 937956 938114 938160 938316 938327 938329 935358 938503 938581 938583 938584 938586 938588 938591 938592 938593 938595 938

[Debian Bug Tracking System]

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

> block 936371 with 937325 937338 937339 894806 937513 937688 937870 937956 
> 938114 938160 938316 938327 938329 935358 938503 938581 938583 938584 938586 
> 938588 938591 938592 938593 938595 938596 938604 938642 938667 938749 938799 
> 938823 938884 892359 937321 937388 938329 849086 938643
Bug #936371 [src:dbus-python] dbus-python: Python2 removal in sid/bullseye
936371 was blocked by: 936531 936981 937125 781914 937233 936812 936987 936104 
936270 936948 936173 936721 937137 937044 936555 936757 937073 938637 936166 
936813 937224 936594 612636 936297
936371 was blocking: 938625
Added blocking bug(s) of 936371: 937688, 938799, 937513, 938583, 935358, 
849086, 938643, 938667, 938160, 938749, 938604, 938591, 938503, 938327, 938823, 
938642, 937321, 937338, 938329, 938114, 894806, 938593, 938884, 938586, 937339, 
937956, 938596, 938595, 937388, 938316, 937870, 892359, 938581, 938592, 937325, 
938584, and 938588
> thanks
Stopping processing here.

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

Bug#935800: rss2email: AttributeError: module 'html2text' has no attribute 'unescape'

[Baruch Siach]

Hi Samuel,

On Wed, Aug 28 2019, Samuel Thibault wrote:
> Jakub Wilk, le lun. 26 août 2019 12:47:04 +0200, a ecrit:
>>   return _html2text.unescape(name)
>>   AttributeError: module 'html2text' has no attribute 'unescape'
>
> This seems to be due to the upgrade of python3-html2text to version
> 2019.8.11-1.

Upstream fix is:

  Replacing html2text.unescape with html.unescape
  
https://github.com/rss2email/rss2email/commit/81824e25723dcd2936f25f64ebc16f2e8ec9f310

I applied it locally and it works for me.

Thanks,
baruch

-- 
 http://baruch.siach.name/blog/  ~. .~   Tk Open Systems
=}ooO--U--Ooo{=
   - bar...@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

Processed: Add some blocking bugs for Python2 removal

[Debian Bug Tracking System]

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

> # python-changelog
> block 937642 by 936985 937716
Bug #937642 [src:python-changelog] python-changelog: Python2 removal in 
sid/bullseye
937642 was not blocked by any bugs.
937642 was not blocking any bugs.
Added blocking bug(s) of 937642: 937716 and 936985
> # python-textile
> block 938216 by 938682
Bug #938216 [src:python-textile] python-textile: Python2 removal in sid/bullseye
938216 was not blocked by any bugs.
938216 was not blocking any bugs.
Added blocking bug(s) of 938216: 938682
> # python-secretstorage
> block 938160 by 935015 937870
Bug #938160 [src:python-secretstorage] python-secretstorage: Python2 removal in 
sid/bullseye
938160 was not blocked by any bugs.
938160 was not blocking any bugs.
Added blocking bug(s) of 938160: 937870 and 935015
> # python-snowballstemmer
> block 938179 by 938426
Bug #938179 [src:python-snowballstemmer] python-snowballstemmer: Python2 
removal in sid/bullseye
938179 was not blocked by any bugs.
938179 was not blocking any bugs.
Added blocking bug(s) of 938179: 938426
> # sphinxcontrib-websupport
> block 938540 by 937287
Bug #938540 [src:sphinxcontrib-websupport] sphinxcontrib-websupport: Python2 
removal in sid/bullseye
938540 was not blocked by any bugs.
938540 was not blocking any bugs.
Added blocking bug(s) of 938540: 937287
> thanks
Stopping processing here.

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

Processed: Re: pygobject: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #937448 [src:pygobject] pygobject: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Processed: Add blocking bugs for python-keyring removal

[Debian Bug Tracking System]

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

> # keyrings.alt
> block 936789 by 935015 937965
Bug #936789 [src:keyrings.alt] keyrings.alt: Python2 removal in sid/bullseye
936789 was not blocked by any bugs.
936789 was not blocking any bugs.
Added blocking bug(s) of 936789: 937965 and 935015
> # python-keyring
> block 937870 by 935015 937012 937049 937872 937879 937957 937963 937965 
> 938091 938627
Bug #937870 [src:python-keyring] python-keyring: Python2 removal in sid/bullseye
937870 was not blocked by any bugs.
937870 was not blocking any bugs.
Added blocking bug(s) of 937870: 937965, 937957, 935015, 937879, 937963, 
938091, 938627, 937012, 937872, and 937049
> thanks
Stopping processing here.

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

Processed: Re: pygobject-2: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #937447 [src:pygobject-2] pygobject-2: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Processed: Re: Bug#936100: cinnamon-settings fails to start: ValueError: Namespace Nemo not available

[Debian Bug Tracking System]

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

> forcemerge 936089 936100
Bug #936089 [cinnamon] nemo: Missing gir1.2-nemo-3.0 dependency
Bug #936100 [cinnamon] cinnamon-settings fails to start: ValueError: Namespace 
Nemo not available
Severity set to 'normal' from 'serious'
Added tag(s) pending.
Bug #936089 [cinnamon] nemo: Missing gir1.2-nemo-3.0 dependency
Marked as found in versions cinnamon/4.0.10-1.
Merged 936089 936100
> thanks
Stopping processing here.

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

Bug#936100: cinnamon-settings fails to start: ValueError: Namespace Nemo not available

[Norbert Preining]

forcemerge 936089 936100
thanks

On Fri, 30 Aug 2019, Michael Biebl wrote:
> After installing gir1.2-nemo-3.0, cinnamon-settings starts successfully.
> Looks like a missing dependency.

Already fixed in the git repo.

Thanks for the report.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: pygtk: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #937452 [src:pygtk] pygtk: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Processed: Re: libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.2019.07-3
Bug #935733 {Done: bott...@debian.org (A. Maitland Bottoms)} [libbladerf-doc] 
libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/doc/libbladerf-dev/CONTRIBUTORS
Marked as found in versions bladerf/0.2019.07-3; no longer marked as fixed in 
versions bladerf/0.2019.07-3 and reopened.

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

Bug#935733: libbladerf-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/libbladerf-dev/CONTRIBUTORS

[Andreas Beckmann]

Followup-For: Bug #935733
Control: found -1 0.2019.07-3

Hi,

in libbladerf-doc you want to use
  Breaks+Replaces: libbladerf-dev (<< 0.2019.07)
(the currently used version does not match the package in testing)

Andreas

Processed: Re: pygtksourceview: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #937453 [src:pygtksourceview] pygtksourceview: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> block -1 by 822586
Bug #937453 [src:pygtksourceview] pygtksourceview: Python2 removal in 
sid/bullseye
937453 was not blocked by any bugs.
937453 was not blocking any bugs.
Added blocking bug(s) of 937453: 822586
> affects -1 cherrytree
Bug #937453 [src:pygtksourceview] pygtksourceview: Python2 removal in 
sid/bullseye
Added indication that 937453 affects cherrytree

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

Bug#938931: python-cpuset: missing Breaks+Replaces: cpuset (<< 1.6)

[Andreas Beckmann]

Package: python-cpuset
Version: 1.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python-cpuset_1.6-1_all.deb ...
  Unpacking python-cpuset (1.6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-cpuset_1.6-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/cpuset/__init__.py', 
which is also in package cpuset 1.5.6-5.1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-cpuset_1.6-1_all.deb


cheers,

Andreas


cpuset=1.5.6-5.1_python-cpuset=1.6-1.log.gz
Description: application/gzip

Processed: Re: gamin: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #936579 [src:gamin] gamin: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Processed: Re: Bug#936248: bubbros: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #936248 [src:bubbros] bubbros: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Processed: Re: jhbuild: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #936764 [src:jhbuild] jhbuild: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Bug#938929: Dependency problem with iptables and libvirt-daemon-system

[Julian Hyordey]

Package: libvirt-daemon-system
Version: 5.0.0-4
Severity: grave
File: /usr/sbin/libvirtd

apt show libvirt-daemon-system
Package: libvirt-daemon-system
Version: 5.0.0-4
Priority: optional
Section: admin
Source: libvirt
Maintainer: Debian Libvirt Maintainers <
pkg-libvirt-maintain...@lists.alioth.debian.org>
Installed-Size: 466 kB
Depends: debconf (>= 0.5) | debconf-2.0, libacl1 (>= 2.2.23), libapparmor1
(>= 2.6~devel), libaudit1 (>= 1:2.2.1), libblkid1 (>= 2.16), libc6 (>=
2.14), libcap-ng0 (>= 0.7.9), libdbus-1-3 (>= 1.9.14), libdevmapper1.02.1
(>= 2:1.02.20), libgnutls30 (>= 3.6.5), libnl-3-200 (>= 3.2.7),
libnl-route-3-200 (>= 3.2.7), libnuma1 (>= 2.0.11), libselinux1 (>=
2.0.82), libvirt0 (>= 5.0.0), libxml2 (>= 2.7.4), libyajl2 (>= 2.0.4),
adduser, gettext-base, lsb-base, libvirt-clients (= 5.0.0-4),
libvirt-daemon (= 5.0.0-4), iptables (>= 1.8.1-1) | firewalld, logrotate,
policykit-1
[...]
 .
So If I want to migrate from iptables to nftables on my KVM hypervisor, I
can't remove iptables without removing  libvirt-daemon-system. A bit
annoying for an hypervisor.

Maybe linked to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935313 ?
Not sure, so I submit.

Regards,

Processed: Re: alacarte: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #936115 [src:alacarte] alacarte: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> affects -1 + gnome-panel
Bug #936115 [src:alacarte] alacarte: Python2 removal in sid/bullseye
Added indication that 936115 affects gnome-panel

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

Bug#935496: Fails to install: Invalid action '-p'

[Simon McVittie]

Control: tags -1 + bullseye sid

On Fri, 23 Aug 2019 at 10:04:28 +0200, Michael Biebl wrote:
> Setting up fuse (2.9.9-1) ...
> dpkg: error processing package fuse (--configure):
>  installed fuse package post-installation script subprocess returned error 
> exit status 1
...
> # udevadm test --action -p /devices/virtual/misc/fuse
> Invalid action '-p'

Similar to the equivalent fuse3 bug #934293, this seems to be a regression
since buster: the same binary package installs OK on buster. Maybe
udevadm became more strict about its parameter parsing?

Similar to fuse3, it would be helpful if the maintainer script had less
"> /dev/null 2>&1" so that error messages would appear.

> I'm not exactly sure what this code is supposed to achieve.
> Since fuse no longer ships its own udev rules, maybe it can be dropped
> altogether?

Or if the postinst is still necessary, maybe fuse3 could take over the
fuse binary package name for bullseye (with a transitional package) so that
bugs like this one don't need to be fixed in both places?

smcv

Processed: Re: Bug#935496: Fails to install: Invalid action '-p'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + bullseye sid
Bug #935496 [fuse] Fails to install: Invalid action '-p'
Added tag(s) bullseye and sid.

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

Processed: Re: Bug#934293: fuse3.postinst fails

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #934293 [fuse3] fuse3.postinst fails
Severity set to 'grave' from 'normal'
> tags  -1 + bullseye sid
Bug #934293 [fuse3] fuse3.postinst fails
Added tag(s) bullseye and sid.

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

Bug#938925: xmds2: fails mpi hdf5 tests

[Drew Parsons]

Source: xmds2
Version: 3.0.0+dfsg-2
Severity: serious

xmds2's mpi/hdf5 tests (test_mpi_xsilloading_hdf5 etc) have recently started
failing.

h5py was recently (2.9.0-4) updated to build with mpi support, that is
built against libhdf5-mpi-dev (aided by mpi4py) rather than libhdf5-dev.

I don't know if it means xmds2 just needs to be rebuilt against the
new h5py/mpi4py packages or if the problem is more complex than that.

The xmds2 autopkgtest failure is holding back h5py with mpi support
from migrating to testing.



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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: tagging 930363, tagging 935699, tagging 936095, found 936091 in 0.24.post1-4, tagging 936091

[Debian Bug Tracking System]

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

> tags 930363 + sid bullseye
Bug #930363 [src:faad2] faad2: fix build with gcc-9 [patch]
Added tag(s) bullseye and sid.
> tags 935699 + sid bullseye experimental
Bug #935699 {Done: Simon McVittie } [gdm3] gdm3: uninstallable 
on s390x
Added tag(s) bullseye, experimental, and sid.
> tags 936095 + sid bullseye
Bug #936095 [src:sardana] sardana: Obsolete libs (Python 2) - Depends on to be 
removed packages
Added tag(s) sid and bullseye.
> found 936091 0.24.post1-4
Bug #936091 [src:aff4] aff4: please package new upstream release (needed by 
rekall), port to python3
Marked as found in versions aff4/0.24.post1-4.
> tags 936091 + sid bullseye
Bug #936091 [src:aff4] aff4: please package new upstream release (needed by 
rekall), port to python3
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: affects 933932

[Debian Bug Tracking System]

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

> affects 933932 + src:pyatspi
Bug #933932 [src:strongwind] strongwind: State of the package, remove?
Added indication that 933932 affects src:pyatspi
> thanks
Stopping processing here.

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

Processed: block 937388 with 933932

[Debian Bug Tracking System]

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

> block 937388 with 933932
Bug #937388 [src:pyatspi] pyatspi: Python2 removal in sid/bullseye
937388 was blocked by: 933025
937388 was not blocking any bugs.
Added blocking bug(s) of 937388: 933932
> thanks
Stopping processing here.

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

Bug#933822: closed by Jan Dittberner (Bug#933822: fixed in virtualenvwrapper 4.8.4-1)

[Jan Dittberner]

On Thu, Aug 29, 2019 at 10:41:42PM +0100, Peter Green wrote:
> On 28/08/2019 09:12, Debian Bug Tracking System wrote:
> > This is an automatic notification regarding your Bug report
> > which was filed against the virtualenvwrapper package:
> > 
> > #933822: virtualenvwrapper depends on cruft package python-stevedore
> Is there a reason that the fix was only uploaded to experimental? and/or an 
> ETA for getting the fix in unstable?

The reason is that the package introduced new binary packages that needed to
go through the NEW queue. I will perform a source only upload to unstable
during the weekend. This is the recommended way of adding new binary
packages to unstable [1].

[1] https://lists.debian.org/debian-release/2019/07/msg00053.html


Regards
Jan

-- 
Jan Dittberner - Debian Developer
GPG-key: 4096R/0xA73E008FB8DD 2009-05-10
 B2FF 1D95 CE8F 7A22 DF4C  F09B A73E 0055 558F B8DD
https://portfolio.debian.net/ - https://people.debian.org/~jandd/


signature.asc
Description: PGP signature

Bug#936088: [Debian-med-packaging] Bug#936088: marked as done (libmurmurhash autopkg tests fail)

[Fabian Klötzl]

I saw that there was something wrong with the CI of libmurmurhash but 
didn't have the time to look into it, yet. Thanks to Matthias for the 
patch and to Andreas for releasing a new version so quickly.


Best,
Fabian

Bug#936100: cinnamon-settings fails to start: ValueError: Namespace Nemo not available

[Michael Biebl]

Package: cinnamon
Version: 4.0.10-1
Severity: serious

Trying to run cinnamon-settings, I get

$ cinnamon-settings
Traceback (most recent call last):
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 620, 
in 
window = MainWindow()
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 248, 
in __init__
for module in modules:
  File "/usr/share/cinnamon/cinnamon-settings/modules/cs_desktop.py", line 6, 
in 
gi.require_version('Nemo', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Nemo not available


$ apt-cache policy gir1.2-nemo-3.0
gir1.2-nemo-3.0:
  Installiert:   (keine)
  Installationskandidat: 4.0.6-1
  Versionstabelle:
 4.0.6-1 500
500 http://ftp.debian.org/debian sid/main amd64 Packages
 3.8.5-1+b1 500
500 http://ftp.debian.org/debian buster/main amd64 Packages

After installing gir1.2-nemo-3.0, cinnamon-settings starts successfully.
Looks like a missing dependency.

Regards,
Michael


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cinnamon depends on:
ii  cinnamon-common  4.0.10-1
ii  cinnamon-control-center  4.0.1-1
ii  cinnamon-desktop-data4.0.1-1
ii  cinnamon-screensaver 4.0.3-1
ii  cinnamon-session 4.0.0-1
ii  cinnamon-settings-daemon 4.0.3-1
ii  cjs  4.0.0-1
ii  cups-pk-helper   0.2.6-1+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-caribou-1.0   0.4.21-7
ii  gir1.2-clutter-1.0   1.26.2+dfsg-12
ii  gir1.2-cmenu-3.0 4.0.0-1
ii  gir1.2-cogl-1.0  1.22.4-3
ii  gir1.2-cvc-1.0   4.0.1-1
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-gkbd-3.0  3.26.1-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gnomedesktop-3.0  3.30.2.1-2
ii  gir1.2-gtk-3.0   3.24.10-1
ii  gir1.2-gtkclutter-1.01.8.4-4
ii  gir1.2-keybinder-3.0 0.3.2-1+b1
ii  gir1.2-meta-muffin-0.0   4.0.7-1
ii  gir1.2-nm-1.01.20.0-1
ii  gir1.2-nma-1.0   1.8.22-2
ii  gir1.2-notify-0.70.7.8-1
ii  gir1.2-pango-1.0 1.42.4-7
ii  gir1.2-polkit-1.00.105-26
ii  gir1.2-soup-2.4  2.64.2-2
ii  gir1.2-upowerglib-1.00.99.10-1
ii  gir1.2-xapp-1.0  1.4.9-1
ii  gkbd-capplet 3.26.1-1
ii  gnome-backgrounds3.30.0-1
ii  gnome-themes-extra   3.28-1
ii  gsettings-desktop-schemas3.28.1-1
ii  iso-flags-png-320x2401.0.2-1
ii  libatk-bridge2.0-0   2.32.0-7
ii  libatk1.0-0  2.33.3+really2.32.0-4
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcinnamon-desktop4 4.0.1-1
ii  libcinnamon-menu-3-0 4.0.0-1
ii  libcjs0  4.0.0-1
ii  libcroco30.6.13-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libgirepository-1.0-11.58.3-2
ii  libgl1   1.1.0-1+b1
ii  libglib2.0-0 2.60.6-2
ii  libglib2.0-bin   2.60.6-2
ii  libgstreamer1.0-01.16.0-2.1
ii  libgtk-3-0   3.24.10-1
ii  libmuffin0   4.0.7-1
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libstartup-notification0 0.12-6
ii  libx11-6 2:1.6.7-1
ii  libxfixes3  

Bug#936088: marked as done (libmurmurhash autopkg tests fail)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 07:04:25 +
with message-id 
and subject line Bug#936088: fixed in libmurmurhash 1.5-2
has caused the Debian Bug report #936088,
regarding libmurmurhash autopkg tests fail
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.)


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

Package: src:libmurmurhash
Version: 1.5-1
Severity: serious
Tags: sid bullseye

Apparently the package needs a rebuild at least, some tests don't work anymore.

autopkgtest [22:47:58]: test run-unit-test: [---
/usr/bin/ld: /tmp/ccNY3NFj.o: in function `main':
mmh.c:(.text.startup+0xe2): undefined reference to `lmmh_x86_32'
/usr/bin/ld: mmh.c:(.text.startup+0x11a): undefined reference to `lmmh_x86_128'
/usr/bin/ld: mmh.c:(.text.startup+0x159): undefined reference to `lmmh_x64_128'
collect2: error: ld returned 1 exit status

CFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -O2 -fstack-protector-strong -Wformat 
-Werror=format-security"

gcc ${CFLAGS} -o mmh -lmurmurhash mmh.c
gcc ${CFLAGS} -o mmh_old -lmurmurhash mmh_old.c

- libraries have to appear last on the command line

- it's questionable to hard code the hardening flags.
  you should ask dpkg-buildflags about that, and add
  dpkg-dev to the test dependencies.
--- End Message ---
--- Begin Message ---
Source: libmurmurhash
Source-Version: 1.5-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libmurmurhash package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Aug 2019 08:09:00 +0200
Source: libmurmurhash
Binary: libmurmurhash2 libmurmurhash-dev
Architecture: source
Version: 1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libmurmurhash-dev - libmurmurhash header files
 libmurmurhash2 - Portable MurmurHash Implementation
Closes: 936088
Changes:
 libmurmurhash (1.5-2) unstable; urgency=medium
 .
   [ Matthias Klose ]
   * Team upload.
   * Fix linking of autopkg tests with ld --as-needed.
 Closes: #936088
 .
   [ Andreas Tille ]
   * debhelper-compat 12
   * Standards-Version: 4.4.0
   * Remove trailing whitespace in debian/changelog
Checksums-Sha1:
 b72f043b9876eae7e5df505bc68262c1d03ad3bd 2124 libmurmurhash_1.5-2.dsc
 b01a9bf998e561eaa01465b981006b09bd5a47b7 2608 libmurmurhash_1.5-2.debian.tar.xz
Checksums-Sha256:
 f6b6eda56166d4e94460106d650f7b26c34936f728ef175c0f7d1e2f0c250ec8 2124 
libmurmurhash_1.5-2.dsc
 9eb7797ec565d56c822631d1b95ea769f6807721316eae3b940f6ca3a1b1cdf1 2608 
libmurmurhash_1.5-2.debian.tar.xz
Files:
 bf8e3a07754cb4cc364ed154de28b643 2124 libs optional libmurmurhash_1.5-2.dsc
 4eb89dfbdea755e5e39365cde88fe9cc 2608 libs optional 
libmurmurhash_1.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl1ovmARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFu5g//ZdNSrzaj5C8XK20o2Bd6RaVHQHuEjped
e2+L8pAp6z6gPuujzsWW3txaxsFxvy6ZwPEbHm9CCeyJFpqgN0YScbAAuZBYZqmm
qtqYOknSq6d8Iqm1bMDlA8OXlM0cHLCRj+qKG8JnaLT4s20SB0XkDIVHeQMlKBAt
SNje6YslrMvxxZXN09EKUeoSeKauvYyxLeAgwWQlFj+TrXzWPs6vzP3pHoWXwfcp
19RA2ykwl7SQeWJlx2I2KUEcy4lS1S9oscA0p2iZuFA9/IXBaPrZ8vtwCB8inMx6
9EL5YNmqx1RdLV5dDvxZH/vUEFl51Ea4R19VnntEUKfHuPmJssnBy7WHts4f8n5F
nWLCUAdKMQ5+Z7CxzXHrxXJh47EwC9MrULavH9VQJ/OxTSWfovanna0KnBKFNRD8
Sal7Kjx+GU3iYCH3r9cQhfvZbZ+kVyeLA78tESu4J5eSUI6LOEvL7WXjs3rNZsIa
jNpQMvykQeQaY1HKMIU6TPPYzfJcOEqln9bDljFKDaMoEiyrFrg8ep/tqZjD4Ixo
KFKQU75nyOuUgFyuxqLYx7g1XJjLT5klA+VTHEy04DA59mUbEJBEEoN7CkW3tBPP
o8qPmW/EOIZSvUKEKPqERJ8snoMuCDOQuu/d6ZQpH5X5TWsEjCX3mj2k/o6BbNEd
VuelP1r3vvI=
=FnWY
-END PGP SIGNATURE End Message ---

Bug#936099: rust-num-traits: test failure on i386

[Gianfranco Costamagna]

Source: rust-num-traits
Version: 0.2.8-1
Severity: serious
Forwarded: https://github.com/rust-num/num-traits/issues/124

Hello, looks like enabling the testsuite resulted in a failure on i386 
architecture.
Could you please have a look?
thanks

Gianfranco

Bug#918595: marked as done (ruby-seed-fu FTBFS with rails 5.2)

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 06:19:51 +
with message-id 
and subject line Bug#918595: fixed in ruby-seed-fu 2.3.7-3
has caused the Debian Bug report #918595,
regarding ruby-seed-fu FTBFS with rails 5.2
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.)


-- 
918595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-seed-fu
Version: 2.3.7-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/mbleigh/seed-fu/issues/132

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-seed-fu.html

...

Failures:

  1) SeedFu::Seeder should raise an ActiveRecord::RecordNotSaved exception if 
any records fail to save
 Failure/Error: expect { SeededModel.seed(:fail_to_save => true, :title => 
"Foo") }.to raise_error(ActiveRecord::RecordNotSaved)
   expected ActiveRecord::RecordNotSaved but nothing was raised
 # ./spec/seeder_spec.rb:173:in `block (2 levels) in '

  2) SeedFu::Writer should successfully write some seeds out to a file and then 
import them back in
 Failure/Error: FileUtils.rm(@file_name)

 NameError:
   uninitialized constant FileUtils
 # ./spec/writer_spec.rb:9:in `block (2 levels) in '

  3) SeedFu::Writer should support chunking
 Failure/Error: FileUtils.rm(@file_name)

 NameError:
   uninitialized constant FileUtils
 # ./spec/writer_spec.rb:9:in `block (2 levels) in '

  4) SeedFu::Writer should support specifying the output to use 'seed_once' 
rather than 'seed'
 Failure/Error: FileUtils.rm(@file_name)

 NameError:
   uninitialized constant FileUtils
 # ./spec/writer_spec.rb:9:in `block (2 levels) in '

Deprecation Warnings:

Using `should` from rspec-expectations' old `:should` syntax without explicitly 
enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly 
enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` 
instead. Called from /build/1st/ruby-seed-fu-2.3.7/spec/runner_spec.rb:7:in 
`block (2 levels) in '.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

1 deprecation warning total

Finished in 0.30367 seconds (files took 1.58 seconds to load)
17 examples, 4 failures
--- End Message ---
--- Begin Message ---
Source: ruby-seed-fu
Source-Version: 2.3.7-3

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

Debian distribution maintenance software
pp.
Jongmin Kim  (supplier of updated ruby-seed-fu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 29 Aug 2019 23:49:28 +0900
Source: ruby-seed-fu
Architecture: source
Version: 2.3.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Jongmin Kim 
Closes: 918595
Changes:
 ruby-seed-fu (2.3.7-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Jongmin Kim ]
   * Fix the API mismatch bug for ActiveRecord 5.1+ (Closes: #918595)
   * Fix the RSpec deprecated syntax
   * Bump the policy std-ver to 4.4.0 (no changes)
   * Bump the debhelper to 12
Checksums-Sha1:
 d84f2de449645f5f6266827b0757dc2b2d874c66 2127 ruby-seed-fu_2.3.7-3.dsc
 b6d88b771d062e4b8d47a0d2656e432bd9f95e2f 4360 
ruby-seed-fu_2.3.7-3.debian.tar.xz
 b62d2055708753ecca0073218d0c929f38678b52 9333 
ruby-seed-fu_2.3.7-3_amd64.buildinfo
Checksums-Sha256:
 7ebfa974d5acb04c1cee096b07b9af80922b9b2512f3174d569822af47a76f1e 2127 
ruby-seed-fu_2.3.7-3.dsc
 d93fcbb3646809f60cfb455f8fa5da094e7bbd713cfe5ee613969046f82cdc2d 4360 
ruby-seed-fu_2.3.7-3.debian.tar.xz
 82741879418f92eaa136d55c070c3b0a902ba57422d1a5059475818e67f6885a 9333 
ruby-seed-fu_2.3.7-3_amd64.buildinfo
Files:
 f3b9a1c4bd1980a8bdec1c2939ece5cb 2127 ruby optional ruby-seed-fu_2.3.7-3.dsc
 e33198ce27aa2de5f366de7486f0ac71 4360 ruby 

Bug#935794: xfce4-sntray-plugin FTBFS

[mike . gabriel]

Hi,

Am Donnerstag, 29. August 2019 schrieb peter green:
> It looks like that class was dropped from vala-panel in 
> https://gitlab.com/vala-panel-project/vala-panel/commit/87493a6dfab9868f77b7b19b57fca40a06fe80af
> 
> Unfortunately the commit message doesn't give any clues to what if-anything 
> it should be replaced with.
> 
> If a proper fix cannot be found then one option would be to drop the 
> vala-panel support from this package. The popcon figures for the vala-panel 
> variant are the lowest of any of the variants. 
> https://qa.debian.org/popcon.php?package=xfce4-sntray-plugin . I decided to 
> go ahead and do that in raspbian for the moment to complete the transition 
> there.
> 
> A debdiff should appear soon at 
> https://debdiffs.raspbian.org/main/x/xfce4-sntray-plugin . No intent to NMU 
> in Debian.
> 
> There does seem to be some upstream activity on xfce4-sntray-plugin at 
> https://github.com/rilian-la-te/xfce4-sntray-plugin but I can't find anything 
> relavent to this issue.
> 

I hope that upstream makes a new release soon, see
https://gitlab.com/vala-panel-project/xfce4-sntray-plugin/issues/34

In the past, Konstantin has been really quick with such requests.

Mike

-- 
Gesendet von meinem Fairphone2 (powered by Sailfish OS).

Bug#936017: marked as done (mapnik: FTBFS with scons 3.1.1 (environment variables not used))

[Debian Bug Tracking System]

Your message dated Fri, 30 Aug 2019 06:04:58 +
with message-id 
and subject line Bug#936017: fixed in mapnik 3.0.22+ds1-1
has caused the Debian Bug report #936017,
regarding mapnik: FTBFS with scons 3.1.1 (environment variables not used)
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.)


-- 
936017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mapnik
Version: 3.0.22+ds-2
Severity: serious
Tags: upstream
Justification: makes the package in question unusable or mostly so
Control: block 931949 by -1
Control: forwarded -1 https://github.com/mapnik/mapnik/issues/4081

Mapnik 3.0.22 FTBFS as part of the proj transition, seemingly due to
scons being updated to 3.1.1.

The environment variables set in debian/rules nor ones set in SConstruct
are actually used by the scons build.
--- End Message ---
--- Begin Message ---
Source: mapnik
Source-Version: 3.0.22+ds1-1

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated mapnik 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: Fri, 30 Aug 2019 06:44:17 +0200
Source: mapnik
Architecture: source
Version: 3.0.22+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 936017
Changes:
 mapnik (3.0.22+ds1-1) unstable; urgency=medium
 .
   * New repacked upstream release.
   * Don't exclude scons from upstream tarball.
   * Add license & copyright for scons sources.
   * Use embedded copy of scons for the build.
 (closes: #936017)
   * Add lintian override for spelling-error-in-binary false positive.
Checksums-Sha1:
 95ddc34eb1a92740d14f706ca033bd3301c99a62 3020 mapnik_3.0.22+ds1-1.dsc
 3120f6b6654e7f03946d1202bd05e19cc9798e4f 3784724 mapnik_3.0.22+ds1.orig.tar.xz
 4aa7b0244b29384aa773b272d78164c7a1a0118a 18384 
mapnik_3.0.22+ds1-1.debian.tar.xz
 9d7823194db79572607b455fe5c9e9153baaedc6 15279 
mapnik_3.0.22+ds1-1_amd64.buildinfo
Checksums-Sha256:
 fbd64907ee367090988e3c3e5bc2d54100855ef26dc228e12d8b4ab53420c555 3020 
mapnik_3.0.22+ds1-1.dsc
 c7da42d8d5e97494386e13ce50c71678c95b8233d6dcb0a6c8257d47c9ca3dd5 3784724 
mapnik_3.0.22+ds1.orig.tar.xz
 ff4394cdd2d63d473f07893ce1b3b7abb3857a2ec4f11f90d23b2d2249aa56f5 18384 
mapnik_3.0.22+ds1-1.debian.tar.xz
 e99a6fcf7379ff8dec7003ff28673023bc38d6bafdb2f1e23e47e6c937d798f0 15279 
mapnik_3.0.22+ds1-1_amd64.buildinfo
Files:
 69c493561aa14987b5e52a7f85bce3ec 3020 libs optional mapnik_3.0.22+ds1-1.dsc
 ce7b72669d9fe235eb609b1f992105dc 3784724 libs optional 
mapnik_3.0.22+ds1.orig.tar.xz
 83be22052a39342e8c2cbd76b9d06a0d 18384 libs optional 
mapnik_3.0.22+ds1-1.debian.tar.xz
 36318b6ce827231b3cb2d39d43f56bd7 15279 libs optional 
mapnik_3.0.22+ds1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl1osUYACgkQZ1DxCuiN
SvErtw/+JK/W1pwJenSSdlwk7CZZfsMErQwlGJB5B+qDLL/DIkZMB7Bs6/cWcgyw
VyJRPLpyTqiM9xW23UnaTYxNMod0CvBj3fbMteRyRO+rKo5gCYWUWyvW5Lyvn3Nt
SVA8hR27ZqsqmNK4C7JY7Z90egzFDqr7+6+9fBfRHEvGAiE8TFXWJpaHrMmnzgZM
z9vA5tzT6qkAo3HD8Ojx/zgQBe6k5wRMLWr5Wad3yJN2Arq9XKVYgfdqBgcjdyU9
nbWO25DsMSvJ59q4i9ZJv2p5pvOrmIx/tHkmuLvqr1GbNVCcbPwrVZIj4KFNjJ2A
YvWbs+jJxIm3qynNGoGf+K0WWYhLu86gZxY0QWdRmNYP8gnXjFF4eyajGbjp1R77
uweBblGJOfkCbO3za32QnRvnYArXjiQ3phErnDiJ4rQXtdQ8JDD/+l9vvSeZcQle
GoTRTl2M06xhvZuCKtgjI0fpFqDrPSuVtCXY2b4OR2APnJbJdGrxNj6wspU3/Pul
4gUW5TEYEUQGrqXhnZ6HG25exZpxVRlXzJBoL+3EjkCVftqd2pmCyY0K0WFOJHhB
mHqo5Vrx0SjHKy2OnvtYNSQyGA1DZk17549O4NiRuByGwq6BOUNcAm/dVXtUItpV
k9TWZ5Pm3tDp9za9a8uceVD7JtFlXJQU8jGCwZZYSM7dkYeuQGc=
=lL/I
-END PGP SIGNATURE End Message ---