Processed: tagging 926549, found 940012 in 2.2.2-3

[Debian Bug Tracking System]

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

> tags 926549 + sid bullseye
Bug #926549 [direwolf] libgps changed API of gps_read
Added tag(s) bullseye and sid.
> found 940012 2.2.2-3
Bug #940012 [src:pylint] pylint: renaming broke reverse-dependencies
Marked as found in versions pylint/2.2.2-3.
> thanks
Stopping processing here.

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

Processed: notfound 910434 in 3.4.2-1, found 910434 in 3.4.2-1, fixed 928964 in 2.2.16-1 ..., tagging 885497 ...

[Debian Bug Tracking System]

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

> # fix bug metadata to allow archival
> notfound 910434 3.4.2-1
Bug #910434 {Done: Noah Meyerhans } [spamassassin] Add 
libbsd-resource-perl to recommend/suggest list
No longer marked as found in versions spamassassin/3.4.2-1.
> found 910434 3.4.2-1
Bug #910434 {Done: Noah Meyerhans } [spamassassin] Add 
libbsd-resource-perl to recommend/suggest list
Marked as found in versions spamassassin/3.4.2-1 and reopened.
> fixed 928964 2.2.16-1
Bug #928964 {Done: Daniel Kahn Gillmor } [gpg] gpg 
fails to emit OpenPGP secret keys if the stored keyfile has a comment or a uri
There is no source info for the package 'gpg' at version '2.2.16-1' with 
architecture ''
Unable to make a source version for version '2.2.16-1'
Marked as fixed in versions 2.2.16-1.
> fixed 929583 5.2.6-1
Bug #929583 {Done: Ben Hutchings } [src:linux] 
linux-image-5.0.0-trunk-amd64: Please build with 
CONFIG_ALLOW_LOCKDOWN_LIFT_BY_SYSRQ
Marked as fixed in versions linux/5.2.6-1.
> tags 885497 - buster
Bug #885497 {Done: Dmitry Smirnov } [src:xpra] xpra: 
Depends on unmaintained pygtk
Removed tag(s) buster.
> notfixed 914652 3.30.5-2
Bug #914652 {Done: Pedro Beja } [nautilus] nautilus: takes 
many seconds to start; becomes irresponsive on search
No longer marked as fixed in versions 3.30.5-2.
> reassign 921293 doxygen 1.8.15-1~exp1
Bug #921293 {Done: Paolo Greppi } [hwloc] hwloc: FTBFS 
with upcoming doxygen 1.8.15
Bug reassigned from package 'hwloc' to 'doxygen'.
No longer marked as found in versions hwloc/1.11.12-1.
No longer marked as fixed in versions doxygen/1.8.16-1~exp1.
Bug #921293 {Done: Paolo Greppi } [doxygen] hwloc: 
FTBFS with upcoming doxygen 1.8.15
Marked as found in versions doxygen/1.8.15-1~exp1.
> fixed 921293 1.8.16-1~exp1
Bug #921293 {Done: Paolo Greppi } [doxygen] hwloc: 
FTBFS with upcoming doxygen 1.8.15
Marked as fixed in versions doxygen/1.8.16-1~exp1.
> tags 885294 - buster
Bug #885294 {Done: bott...@debian.org (A. Maitland Bottoms)} [src:gnuradio] 
gnuradio: Depends on unmaintained pygtk
Removed tag(s) buster.
> tags 912960 - buster
Bug #912960 {Done: bott...@debian.org (A. Maitland Bottoms)} [gnuradio] 
python-gnuradio: depends on deprecated python-gobject-2
Removed tag(s) buster.
> tags 885354 - buster
Bug #885354 {Done: Debian FTP Masters } 
[src:musiclibrarian] musiclibrarian: Depends on unmaintained pygtk
Removed tag(s) buster.
> tags 885474 - buster
Bug #885474 {Done: Debian FTP Masters } 
[src:pythontracer] pythontracer: Depends on unmaintained pygtk
Removed tag(s) buster.
> notfound 929749 2.24.0-1
Bug #929749 {Done: Alberto Garcia } [libwebkit2gtk-4.0-37] 
libwebkit2gtk-4.0-37: version 2.24.2-1 does not play some streams
No longer marked as found in versions webkit2gtk/2.24.0-1.
> found 929749 2.24.1-1
Bug #929749 {Done: Alberto Garcia } [libwebkit2gtk-4.0-37] 
libwebkit2gtk-4.0-37: version 2.24.2-1 does not play some streams
Marked as found in versions webkit2gtk/2.24.1-1.
> fixed 929749 2.25.4-1
Bug #929749 {Done: Alberto Garcia } [libwebkit2gtk-4.0-37] 
libwebkit2gtk-4.0-37: version 2.24.2-1 does not play some streams
Marked as fixed in versions webkit2gtk/2.25.4-1.
> fixed 931507 5.2.7-1
Bug #931507 {Done: Ben Hutchings } [src:linux] 
kernel-wedge: HDA sound board detection takes 60s in d-i
Marked as fixed in versions linux/5.2.7-1.
> fixed 873012 1:2.10.0-1
Bug #873012 {Done: Michael Tokarev } [qemu-kvm] not working 
live migration in qemu ( vm's block storage is LVM )
There is no source info for the package 'qemu-kvm' at version '1:2.10.0-1' with 
architecture ''
Unable to make a source version for version '1:2.10.0-1'
Marked as fixed in versions 1:2.10.0-1.
> tags 885880 - buster
Bug #885880 {Done: Andrew Starr-Bochicchio } [deluge-gtk] 
deluge: Depends on unmaintained pygtk
Removed tag(s) buster.
> fixed 902599 1:2.0.1-1
Bug #902599 {Done: Riku Voipio } [mtd-utils] Wrong 
off_t and loff_t printf format strings in mtd-utils
Marked as fixed in versions mtd-utils/1:2.0.1-1.
> tags 933829 + buster
Bug #933829 {Done: Didier Raboud } [win32-loader] 
win32-loader: Checksums need to be updated for new stable release, download 
fails to validate Release file.
Added tag(s) buster.
> fixed 657730 3.43.0+dfsg-1
Bug #657730 {Done: Nicholas D Steeves } [calibre] calibre: 
crashes before starting
Marked as fixed in versions calibre/3.43.0+dfsg-1.
> reopen 613646
Bug #613646 {Done: Debian FTP Masters } 
[pylint] pylint.el redefines emacs key bindings which are reserved for the user
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.9.4-1+rm.
> reopen 860983
Bug #860983 {Done: Debian FTP Masters } 
[pylint] pylint: called emacs-package-install as a new-style add-on, but has no 
compat file
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add 

Bug#941523: marked as done (geomview: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Wed, 16 Oct 2019 04:34:24 +
with message-id 
and subject line Bug#941523: fixed in geomview 1.9.5-3
has caused the Debian Bug report #941523,
regarding geomview: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
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.)


-- 
941523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: geomview
Version: 1.9.5-2
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Hi Steve,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
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
diff -Nru geomview-1.9.5/debian/control geomview-1.9.5/debian/control
--- geomview-1.9.5/debian/control   2018-01-25 00:42:20.0 -0800
+++ geomview-1.9.5/debian/control   2019-10-01 13:14:22.0 -0700
@@ -15,7 +15,7 @@
texi2html,
xutils-dev,
texinfo,
-   texlive-generic-recommended,
+   texlive-plain-generic,
texlive-fonts-recommended
 Build-Conflicts: libutahglx-dev
 Standards-Version: 4.1.3
--- End Message ---
--- Begin Message ---
Source: geomview
Source-Version: 1.9.5-3

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated geomview package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Oct 2019 23:15:12 -0500
Source: geomview
Architecture: source
Version: 1.9.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Steve M. Robbins 
Closes: 941523
Changes:
 geomview (1.9.5-3) unstable; urgency=medium
 .
   [ Steven Robbins ]
   * Update texlive dependencies.  Add texlive-font-utils for epstopdf.
 Closes: #941523
Checksums-Sha1:
 cb3b92ce6a989d3dd27681eb04e87416f592476b 2292 geomview_1.9.5-3.dsc
 e49901e8154642bc212afe5dcf33873acadb45fe 9712 geomview_1.9.5-3.debian.tar.xz
 69e90076a61ec47cbbf1c3d239928eb06473830d 10239 
geomview_1.9.5-3_source.buildinfo
Checksums-Sha256:
 046f39d187c81724e37415c9bdf87303879fd5a3fcb537ec6c4b53b9dae3237c 2292 
geomview_1.9.5-3.dsc
 9937f38b6016cbb0c5049f8b4b251d4f044914435cf8203e81feab05b687ae16 9712 
geomview_1.9.5-3.debian.tar.xz
 4c950b500a020ea018d2fbc7f5d065be2b3cdfa725a0747d7e3d500fe3323d88 10239 
geomview_1.9.5-3_source.buildinfo
Files:
 8d4e74c89ccd261c393d7e25ddf2d5b0 2292 math optional geomview_1.9.5-3.dsc
 ebe075a53e6062df4b32499d19e27f24 9712 math optional 
geomview_1.9.5-3.debian.tar.xz
 e2812053ecb8ec7d89533c99a6b9ee22 10239 math optional 
geomview_1.9.5-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEy89k8fa3rclNjyokyeVeL63I9LkFAl2mmfUPHHNtckBkZWJp
YW4ub3JnAAoJEMnlXi+tyPS5tLIP/2V7Mq/m0hYvWneZUpQr48wWGb7hhTRO5hLf
pZvAyTLe3O7e+B1riskH0LsNxxzTm/TSDTthZ36k5DhWP5SnfAKVempVeWJR5LFT
pp+GlUKj3AltJ/Q5RDAe0wSMcfs7B0zxrmzyJSCM55utq5jIojCjmbt69C8ubrUV
Rop6DQxKq0onaaBDfdONN1daXfp1LViVOKgACD0HJkKYhYLygnfrwRFqi4pxFU25
tK+HNKEQwTT4/UZJ7p5U5gvUw8vIARMJaaPMBz5hDdtJF9clZvYj2G9WTn6nzJlw
y4zbFLrTfIitnZd6GWJVAGMPVEbDT1VyTScO3EqjVkX1EzjCJWQgA0YFaoLyPypz
FFLNoWwhKKl9jLUqDw7LNwQ6DuMkmBQSMCVJLqXEX+/NY+oP676EOhZr65VwKXX9
r6qSE88vX5awApaEC/I+C5SVvTVEvMWSBg8gHq+jdGt8VcrDJ5WtM1IMgySvR8P8
FlmvP9nDVQw1ICUsTyyIFj2mEu2X3VnbgtrFmvgLOaWhe0ByNcvKib3KVliCpK9y
H28aRLQLR3eoFyGgng8MfQD1veCFcwNXikgEU2ruF9FAHEMpjuqRlBaPCVc+pyg/
aFlT4JjymN/6CrWgIE9qJG7HNDVbWyheO/Vu845XgijVekQ2Fxz9QqGO92aJtgVa
SQdaOmXA
=Mhgr
-END PGP SIGNATURE End Message ---

Processed: Re: pylint: renaming broke reverse-dependencies

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #940012 {Done: Sandro Tosi } [src:pylint] pylint: 
renaming broke reverse-dependencies
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pylint/2.2.2-4.
> severity -1 serious
Bug #940012 [src:pylint] pylint: renaming broke reverse-dependencies
Severity set to 'serious' from 'normal'

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

Bug#942364: [patch] perl6-* (vendored) packages out of the reach of perl6 path

[Mo Zhou]

Hi Gregor,

Thanks for the feedback. What you encountered is an old hidden
but in rakudo-helper's reinstall-all function. When none of the
packages has a dependency, the dependency graph would be empty
hence reinstall-all triggers nothing.

The bug is fixed here:
https://salsa.debian.org/perl6-team/rakudo/commit/7b510778df1c10163eab07741d25099066efd80b

And I've also changed the usr/{lib->share} transition method
in the latest maintainer scripts. I will upload the -7 release
once implemented a graceful /usr/lib/perl6 purge in preinst.

/usr/lib/perl6 should not appear again after the transition.

On 2019-10-15 16:44, gregor herrmann wrote:
> On Tue, 15 Oct 2019 02:17:24 -0700, Mo Zhou wrote:
> 
>> Could you please double check the -6 revision? If it looks good,
>> I'll continue and upload it to unstable and close this bug.
> 
> After upgrading rakudo from 2019.07.1-4 to 2019.07.1-6:
> 
> % zef
> ===SORRY!===
> Could not find Zef::CLI at line 3 in:
> inst#/home/gregoa/.perl6
> inst#/usr/share/perl6/site
> inst#/usr/share/perl6/vendor
> inst#/usr/share/perl6/core
> ap#
> nqp#
> perl5#
> 
> (i.e. same as before)
> 
> /usr/lib/perl6 doesn't exist anymore; /usr/share/perl6 has lots of
> stuff with zef:
> 
> /usr/share/perl6/debian-sources/perl6-zef
> /usr/share/perl6/debian-sources/perl6-zef/resources
> /usr/share/perl6/debian-sources/perl6-zef/resources/scripts
> /usr/share/perl6/debian-sources/perl6-zef/resources/scripts/perl5tar.pl
> /usr/share/perl6/debian-sources/perl6-zef/resources/scripts/win32http.ps1
> /usr/share/perl6/debian-sources/perl6-zef/resources/scripts/win32unzip.ps1
> /usr/share/perl6/debian-sources/perl6-zef/resources/config.json
> /usr/share/perl6/debian-sources/perl6-zef/lib
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Extract.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/LocalCache.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/Ecosystems.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/MetaCPAN.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/URI.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/FileSystem.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/SystemInfo.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/SystemQuery.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Config.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Install.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Fetch.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/CLI.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Client.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Report.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/InstallPM6.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/P6CReporter.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/FetchPath.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/git.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/prove.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell/download.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell/unzip.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/LegacyBuild.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/curl.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/tar.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/p5tar.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/wget.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/DistributionBuilder.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/unzip.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/Test.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/TAP.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution/DependencySpecification.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution/Local.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Identity.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Test.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Build.pm6
> /usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution.pm6
> 

Bug#830726: closed by Chris Lamb (Bug#830726: fixed in xtrlock 2.12)

[Chris Lamb]

Hi Antoine,

> Looks great! There's a grammar problem "This fix does not the situation"
> but it doesn't matter.

Whoops, fixed in:

  
https://salsa.debian.org/debian/xtrlock/commit/e578040d4bedf81874cc2bf1c62d6643b36b527d


Regards,

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

Bug#940565: No problem here

[Diederik de Haas]

Control: tag -1 +moreinfo +unreproducible
Control: severity -1 important

I noticed you specified the source package and not the binary package to report 
the bug against. Normally not much of an issue, but it looks like you didn't 
use or didn't share the whole output of reportbug, because it's missing the 
list of installed packages, which can be rather crucial.

Note that there are 2 groups of binary packages: python-pyside2.* and python3-
pyside2.* whereas the former is for python2 and the latter for python3.

I didn't have any pyside2 packages installed, so I tried it with a clean 
slate:
# aptitude install python3-pyside2.qtcore
$ echo "import PySide2.QtCore as core" > test.py
$ python test.py
Traceback (most recent call last):
  File "test.py", line 1, in 
import PySide2.QtCore as core
ImportError: No module named PySide2.QtCore
$ python3 test.py
$

This output is exactly as expected.
If I install python-pyside2.qtcore, then the Traceback output disappears.

As I couldn't reproduce the issue, I set the tags accordingly and as the issue 
doesn't happen for everyone, I lowered the severity.

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

Processed: No problem here

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +moreinfo +unreproducible
Bug #940565 [pyside2] PySide2 segfaults with Python3. Message: "SystemError: 
could not initialize part 1" (shiboken)
Added tag(s) moreinfo.
Bug #940565 [pyside2] PySide2 segfaults with Python3. Message: "SystemError: 
could not initialize part 1" (shiboken)
Added tag(s) unreproducible.
> severity -1 important
Bug #940565 [pyside2] PySide2 segfaults with Python3. Message: "SystemError: 
could not initialize part 1" (shiboken)
Severity set to 'important' from 'grave'

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

Bug#942193: dwz: dh_dwz freecad build regression: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed.

[Tom de Vries]

On 15-10-2019 14:33, Matthias Klose wrote:
> On 14.10.19 10:10, Tom de Vries wrote:
>> On 13-10-2019 21:34, Kurt Kremitzki wrote:
>>> Hi Matthias,
>>>
>>> On Saturday, October 12, 2019 12:34:30 PM CDT Matthias Klose wrote:
 Control: tags -1 + moreinfo
 Control: severity -1 grave

 please could you attach the binary, or put it somewhere on the web?

>>>
>>> Sorry, which binary are you referring to?
>>>
>>
>> Hi,
>>
>> in order to reproduce a dwz problem, we need:
>> - the dwz command line that triggered the assertion, and
>> - the files that were used as arguments. [ And since dwz modifies files
>>    in place, we need the files as they were before dwz was run. ]
>>
>>> Here are a few links in the meantime that might help, buildd logs for
>>> the
>>> i386/s390x/mipsel failures:
>>>
>>> https://buildd.debian.org/status/fetch.php?
>>> pkg=freecad=i386=0.18.3%2Bdfsg1-3=1568751036=0
>>>
>>> https://buildd.debian.org/status/fetch.php?
>>> pkg=freecad=mipsel=0.18.3%2Bdfsg1-3=1568784049=0
>>>
>>> https://buildd.debian.org/status/fetch.php?
>>> pkg=freecad=s390x=0.18.3%2Bdfsg1-3=1569764936=0
>>>
>>
>> I think it would be the easiest for me to reproduce on i386, so if you
>> could provide the reproduction information for that one, that would be
>> great.
> 
> https://people.debian.org/~doko/tmp/dwz-freecad.tar.xz
> https://people.debian.org/~doko/tmp/dwz-freecad.sh

Reproduced it, thanks.

Filed as: https://sourceware.org/bugzilla/show_bug.cgi?id=25109

- Tom

Bug#942418: libmutter-5-0: Blank screen after upgrading to bullseye, caused by failing wayland

[Gert van de Kraats]

Package: libmutter-5-0
Version: 3.34.1-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

After upgrading from buster stable to bullseye testing and restarting, 
only a blank screen appears.
Problem caused by failing wayland, which is by default enabled since 
debian buster.
If wayland is disabled at /etc/gdm3/daemon.conf, the system started 
without problem,
but with newer  packages it only shows the logon-page, and after typing 
correct password it shows blank screen with working mouse pointer.
Problem occurs both at mutter 3.34.0-4 (testing) and mutter 3.34.1-1 
(unstable).


The log shows the next errors:

Oct 11 20:30:20 debian gnome-shell[970]: Failed to initialize 
accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs
Oct 11 20:30:20 debian gnome-shell[970]: Unable to initialize Clutter: 
Unable to initialize the Clutter backend: no available drivers found.

Oct 11 20:30:20 debian gnome-shell[970]: Unable to initialize Clutter.
Oct 11 20:30:21 debian systemd[857]: gnome-shell-wayland.service: Failed 
with result 'protocol'.

Oct 11 20:30:21 debian systemd[857]: Failed to start GNOME Shell on Wayland.
Oct 11 20:30:21 debian systemd[857]: Dependency failed for GNOME Shell 
on Wayland.
Oct 11 20:30:21 debian systemd[857]: Dependency failed for GNOME Wayland 
Session.
Oct 11 20:30:21 debian systemd[857]: Dependency failed for GNOME Wayland 
Session (session: gnome-login).
Oct 11 20:30:21 debian systemd[857]: 
gnome-session-wayland@gnome-login.target: Job 
gnome-session-wayland@gnome-login.target/start failed with result 
'dependency'.
Oct 11 20:30:21 debian systemd[857]: gnome-session-wayland.target: Job 
gnome-session-wayland.target/start failed with result 'dependency'.
Oct 11 20:30:21 debian systemd[857]: gnome-session-wayland.target: 
Triggering OnFailure= dependencies.


I am using a DELL D620:
Linux debian 5.2.0-3-686-pae #1 SMP Debian 5.2.17-1 (2019-09-26) i686 
GNU/Linux
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML 
and 945GT Express Memory Controller Hub (rev 03)
    Subsystem: Dell Mobile 945GM/PM/GMS, 943/940GML and 945GT Express 
Memory Controller Hub
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03)
    Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated 
Graphics Controller

    Kernel driver in use: i915
    Kernel modules: i915
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)
    Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 5.2.0-3-686-pae (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 libmutter-5-0 depends on:
ii  gsettings-desktop-schemas  3.34.0-2
ii  libatk1.0-0    2.34.1-1
ii  libc6  2.29-2
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libcanberra0   0.30-7
ii  libdrm2    2.4.99-1
ii  libegl1    1.1.0-1+b1
ii  libfontconfig1 2.13.1-2+b1
ii  libfribidi0    1.0.7-1
ii  libgbm1    19.1.6-1
ii  libgdk-pixbuf2.0-0 2.40.0+dfsg-1
ii  libgl1 1.1.0-1+b1
ii  libglib2.0-0   2.62.1-1
ii  libgnome-desktop-3-18  3.34.1-1
ii  libgtk-3-0 3.24.12-1
ii  libgudev-1.0-0 233-1
ii  libice6    2:1.0.9-2
ii  libinput10 1.14.1-2
ii  libjson-glib-1.0-0 1.4.4-2
ii  libpango-1.0-0 1.42.4-7
ii  libpangocairo-1.0-0    1.42.4-7
ii  libpangoft2-1.0-0  1.42.4-7
ii  libpipewire-0.2-1  0.2.5-1
ii  libsm6 2:1.2.3-1
ii  libstartup-notification0   0.12-6
ii  libsystemd0    242-7
ii  libudev1   242-7
ii  libwacom2  1.1-1
ii  libwayland-server0 1.17.0-1
ii  libx11-6   2:1.6.8-1
ii  libx11-xcb1    2:1.6.8-1
ii  libxau6    1:1.0.8-1+b2
ii  libxcb-randr0  1.13.1-2
ii  libxcb-res0    1.13.1-2
ii  libxcb1    1.13.1-2
ii  libxcomposite1 1:0.4.4-2
ii  libxcursor1    1:1.2.0-2
ii  libxdamage1    1:1.1.5-1
ii  libxext6   2:1.3.3-1+b2
ii  libxfixes3 1:5.0.3-1
ii  libxi6 2:1.7.9-1
ii  libxinerama1   2:1.1.4-2
ii  libxkbcommon-x11-0 0.8.4-1
ii  libxkbcommon0  0.8.4-1
ii  libxkbfile1    1:1.0.9-2+b12
ii  libxrandr2 

Bug#941888: marked as done (python-zbar: requires libzbar0 (= 0.22-1) but installed libzbar0 is 0.23-1.1+b1)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 21:00:14 +
with message-id 
and subject line Bug#941888: fixed in qr-tools 2.0~bzr33-1
has caused the Debian Bug report #941888,
regarding python-zbar: requires libzbar0 (= 0.22-1) but installed libzbar0 is 
0.23-1.1+b1
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.)


-- 
941888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-zbar
Version: 0.22-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When trying to install qtqr package, a dependency (which is the subject
of this report) cannot be installed therefore qtqr cannot be used.

Manually installing python-zbar et al makes qtqr work. I don't know if
anything will be broken if the dependency version is bumped, but I hope
it is updated to the latest available version so that both apt and qtqr become 
happier altogether.


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

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

Versions of packages python-zbar depends on:
ii  libc6   2.29-2
ii  libc6-udeb [libc6]  2.24-11+deb9u4
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  libzbar00.23-1.1+b1
ii  python  2.7.16-1

python-zbar recommends no packages.

python-zbar suggests no packages.
--- End Message ---
--- Begin Message ---
Source: qr-tools
Source-Version: 2.0~bzr33-1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated qr-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Oct 2019 10:21:01 +0200
Source: qr-tools
Binary: python3-qrtools qtqr
Architecture: source all
Version: 2.0~bzr33-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Gianfranco Costamagna 
Description:
 python3-qrtools - high level library for reading and generating QR codes
 qtqr   - Qt frontend for QR code generator and decoder
Closes: 932865 938317 941888
Changes:
 qr-tools (2.0~bzr33-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream release, Python3 ready
   * Migrate the package to Python3 (Closes: #941888, #932865, #938317)
   * Bump compat level to 12
   * Bump std-version to 4.4.1
   * Refresh patches
   * Set R^3 to no
   * Use pkg-info to avoid dpkg-parsechangelog calls
Checksums-Sha1:
 6c4f59682115058eabcdcb25792e454921faf166 1837 qr-tools_2.0~bzr33-1.dsc
 b9ba01cf67aba0ef447d23c0af7e21a68e14feec 53824 qr-tools_2.0~bzr33.orig.tar.xz
 1fde19de5446f0cb6177bfb9596e068fb577cb1a 4864 
qr-tools_2.0~bzr33-1.debian.tar.xz
 6c30ad337a0fec8cd19ee9b84a2398bdc4795116 6908 
python3-qrtools_2.0~bzr33-1_all.deb
 d2eea02a353c9b2400187b5bab4dae22a11a66a0 9964 
qr-tools_2.0~bzr33-1_amd64.buildinfo
 5c5efde75b6f0eecf986784d0c7bcac3d81c5931 39392 qtqr_2.0~bzr33-1_all.deb
Checksums-Sha256:
 a944109f392306013bdab89e68531b68f98ea3a996593e5c9008eeb0b4711a8d 1837 
qr-tools_2.0~bzr33-1.dsc
 32152c7fd22c2e572c953ad6790095fde5d1da87a4ece09b64e57b73d0cdcf73 53824 
qr-tools_2.0~bzr33.orig.tar.xz
 15a5e0f1bfc9d329458c79e11cea88e35d001c35ffd7807d1d3eaf54e380c673 4864 
qr-tools_2.0~bzr33-1.debian.tar.xz
 572c4c029ab9c380f3f1968f590c6d2242903f690cf06b8cc84e6f649775d2d5 6908 
python3-qrtools_2.0~bzr33-1_all.deb
 2b79e848487e3e55a8e77bdd6fbe28ecc84cf4b08b7874ee08a146d75cd2ac4e 9964 
qr-tools_2.0~bzr33-1_amd64.buildinfo
 7208225accc9557ae91e3f83a7602d8774fc2b36fcb8f245372d6d4fd1f88fb0 39392 
qtqr_2.0~bzr33-1_all.deb
Files:
 b1ee247587a96dcc86649b769281bb80 1837 python optional qr-tools_2.0~bzr33-1.dsc
 18ef1faf029ffd821c9d5ca0839b86dd 

Bug#932865: marked as done (python-qrtools: not installable: depends on python2 version of zbar)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 21:00:14 +
with message-id 
and subject line Bug#932865: fixed in qr-tools 2.0~bzr33-1
has caused the Debian Bug report #932865,
regarding python-qrtools: not installable: depends on python2 version of zbar
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.)


-- 
932865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-qrtools
Version: 1.4~bzr32-1
Severity: grave
Justification: renders package unusable

Hi!
This package depends on python-zbar, which has already been removed as part
of the python2-rm transition.  This obviously makes it non-installable.


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

Kernel: Linux 5.2.1-00036-gf2c1d208af28 (SMP w/64 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages python-qrtools depends on:
ii  python   2.7.16-1
pn  python-pil   
pn  python-zbar  
pn  qrencode 

python-qrtools recommends no packages.

python-qrtools suggests no packages.
--- End Message ---
--- Begin Message ---
Source: qr-tools
Source-Version: 2.0~bzr33-1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated qr-tools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Oct 2019 10:21:01 +0200
Source: qr-tools
Binary: python3-qrtools qtqr
Architecture: source all
Version: 2.0~bzr33-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Gianfranco Costamagna 
Description:
 python3-qrtools - high level library for reading and generating QR codes
 qtqr   - Qt frontend for QR code generator and decoder
Closes: 932865 938317 941888
Changes:
 qr-tools (2.0~bzr33-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream release, Python3 ready
   * Migrate the package to Python3 (Closes: #941888, #932865, #938317)
   * Bump compat level to 12
   * Bump std-version to 4.4.1
   * Refresh patches
   * Set R^3 to no
   * Use pkg-info to avoid dpkg-parsechangelog calls
Checksums-Sha1:
 6c4f59682115058eabcdcb25792e454921faf166 1837 qr-tools_2.0~bzr33-1.dsc
 b9ba01cf67aba0ef447d23c0af7e21a68e14feec 53824 qr-tools_2.0~bzr33.orig.tar.xz
 1fde19de5446f0cb6177bfb9596e068fb577cb1a 4864 
qr-tools_2.0~bzr33-1.debian.tar.xz
 6c30ad337a0fec8cd19ee9b84a2398bdc4795116 6908 
python3-qrtools_2.0~bzr33-1_all.deb
 d2eea02a353c9b2400187b5bab4dae22a11a66a0 9964 
qr-tools_2.0~bzr33-1_amd64.buildinfo
 5c5efde75b6f0eecf986784d0c7bcac3d81c5931 39392 qtqr_2.0~bzr33-1_all.deb
Checksums-Sha256:
 a944109f392306013bdab89e68531b68f98ea3a996593e5c9008eeb0b4711a8d 1837 
qr-tools_2.0~bzr33-1.dsc
 32152c7fd22c2e572c953ad6790095fde5d1da87a4ece09b64e57b73d0cdcf73 53824 
qr-tools_2.0~bzr33.orig.tar.xz
 15a5e0f1bfc9d329458c79e11cea88e35d001c35ffd7807d1d3eaf54e380c673 4864 
qr-tools_2.0~bzr33-1.debian.tar.xz
 572c4c029ab9c380f3f1968f590c6d2242903f690cf06b8cc84e6f649775d2d5 6908 
python3-qrtools_2.0~bzr33-1_all.deb
 2b79e848487e3e55a8e77bdd6fbe28ecc84cf4b08b7874ee08a146d75cd2ac4e 9964 
qr-tools_2.0~bzr33-1_amd64.buildinfo
 7208225accc9557ae91e3f83a7602d8774fc2b36fcb8f245372d6d4fd1f88fb0 39392 
qtqr_2.0~bzr33-1_all.deb
Files:
 b1ee247587a96dcc86649b769281bb80 1837 python optional qr-tools_2.0~bzr33-1.dsc
 18ef1faf029ffd821c9d5ca0839b86dd 53824 python optional 
qr-tools_2.0~bzr33.orig.tar.xz
 315f0107a9888901dbc7ba96a793f687 4864 python optional 
qr-tools_2.0~bzr33-1.debian.tar.xz
 369ea1a82a28f307eec4324f512d05ed 6908 python optional 
python3-qrtools_2.0~bzr33-1_all.deb
 acdb62699038966219111a225c6bd046 9964 python optional 
qr-tools_2.0~bzr33-1_amd64.buildinfo
 

Bug#940973: marked as done (strip-nondeterminism: broken zip file t/fixtures/zip/bug_803503.zip.in in test suite)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 20:48:59 +
with message-id 
and subject line Bug#940973: fixed in strip-nondeterminism 1.6.1-1
has caused the Debian Bug report #940973,
regarding strip-nondeterminism: broken zip file 
t/fixtures/zip/bug_803503.zip.in in test suite
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.)


-- 
940973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libarchive-zip-perl, strip-nondeterminism
Control: found -1 libarchive-zip-perl/1.66-1
Control: found -1 strip-nondeterminism/1.6.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of libarchive-zip-perl the autopkgtest of
strip-nondeterminism fails in testing when that autopkgtest is run with
the binary packages of libarchive-zip-perl from unstable. It passes when
run with only packages from testing. In tabular form:
   passfail
libarchive-zip-perlfrom testing1.66-1
strip-nondeterminism   from testing1.6.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of
libarchive-zip-perl to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package? If needed,
please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=libarchive-zip-perl

https://ci.debian.net/data/autopkgtest/testing/amd64/s/strip-nondeterminism/3013957/log.gz

ok 20 - t/fixtures/zip/bug_803503.zip.in
Reading ZIP archive failed: IO error: reading local extra field :

error: becoming Archive::Zip::DirectoryMember
# Looks like your test exited with 29 just after 20.
Tests failed



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: strip-nondeterminism
Source-Version: 1.6.1-1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated strip-nondeterminism package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Oct 2019 12:56:45 -0700
Source: strip-nondeterminism
Architecture: source
Version: 1.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Chris Lamb 
Closes: 940973
Changes:
 strip-nondeterminism (1.6.1-1) unstable; urgency=medium
 .
   * Drop the t/fixtures/zip/bug_803503.zip test fixtures as they are no longer
 compatible with Archive::Zip >= 1.66. Thanks to gregor herrmann for liasing
 on this issue with upstream. (Closes: #940973)
   * Bump debhelper compat level to 12.
   * Bump Standards-Version to 4.4.1.
Checksums-Sha1:
 a6c9aa81f9cf30d59af66f9acfc2c397e2e0874f 2555 strip-nondeterminism_1.6.1-1.dsc
 1e292a0030280779cae5a61dbefce7c187df98fc 276727 
strip-nondeterminism_1.6.1.orig.tar.bz2
 cd245d3f97f56e010037d3184d9c42f1a9822397 32428 
strip-nondeterminism_1.6.1-1.debian.tar.xz
 48a766e43ebd0dee506ab9640ce4ed0f5fec46a2 6404 
strip-nondeterminism_1.6.1-1_amd64.buildinfo
Checksums-Sha256:
 2f87d8fdfb07284e349e7c220c843feb0af4cd497eb4563cf4f6128a779245de 2555 
strip-nondeterminism_1.6.1-1.dsc
 e3efa1a41494303c88749e538fb7f9e751a6303654300f8e16a58e52978f6c67 276727 
strip-nondeterminism_1.6.1.orig.tar.bz2
 85b0140e5607f0b84543e996b1f1115e4a56e063fdf4f1ec92aa3c65cc8cfca3 32428 
strip-nondeterminism_1.6.1-1.debian.tar.xz
 58bf46e1dda0ebe4b7eaba4f729ca5c04a98149ed5bb700fd0baf067e535b0ad 6404 
strip-nondeterminism_1.6.1-1_amd64.buildinfo
Files:
 ddf5a00a51685bb614406555e73a9660 2555 devel optional 
strip-nondeterminism_1.6.1-1.dsc
 

Bug#940973: marked as pending in strip-nondeterminism

[Chris Lamb]

Control: tag -1 pending

Hello,

Bug #940973 in strip-nondeterminism 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/reproducible-builds/strip-nondeterminism/commit/4862c51ba2bf73687b1e17bb96f323175545f8fd


Drop the t/fixtures/zip/bug_803503.zip test fixtures as they are no longer 
compatible with Archive::Zip >= 1.66. Thanks to gregor herrmann for liasing on 
this issue with upstream. (Closes: #940973)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/940973

Bug#926549: direwolf: gpsd api compatibility

[Bernd Zeimetz]

Hi,

unfortunately the suggested and applied (thanks!) patch was in the
spirit of upstreams idea to check for the gpsd api version, but the gpsd
upstream is bumping api versions like other people change diapers on
their toddlers... so I've created a pull request to remove the check for
coming major api changes.

Please merge and upload
https://salsa.debian.org/debian-hamradio-team/direwolf/merge_requests/2

I'm happy to NMU if you don't have the time to do it.

Thanks & Sorry for the extra work,

Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Processed: Bug#940973 marked as pending in strip-nondeterminism

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #940973 [strip-nondeterminism] strip-nondeterminism: broken zip file 
t/fixtures/zip/bug_803503.zip.in in test suite
Added tag(s) pending.

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

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[gregor herrmann]

On Sat, 12 Oct 2019 19:10:35 +0200, gregor herrmann wrote:

> > #v+
> > Reading ZIP archive failed: IO error: reading local extra field :  
> > 
> > error: becoming Archive::Zip::DirectoryMember 
> > # Looks like your test exited with 29 just after 20.
> > #v-
> 
> Forwarded upstream as a new issue with a minimal reproducer.

Bug reassigned back to strip-nondeterminism after analysis in 
https://github.com/redhotpenguin/perl-Archive-Zip/issues/68

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Steppenwolf: Wild Thing


signature.asc
Description: Digital Signature

Processed: found 926549 in 1.5+dfsg-2

[Debian Bug Tracking System]

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

> found 926549 1.5+dfsg-2
Bug #926549 [direwolf] libgps changed API of gps_read
Marked as found in versions direwolf/1.5+dfsg-2.
> thanks
Stopping processing here.

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

Processed: severity of 926549 is serious

[Debian Bug Tracking System]

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

> severity 926549 serious
Bug #926549 [direwolf] libgps changed API of gps_read
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: block 931551 with 941780, block 931551 with 939687

[Debian Bug Tracking System]

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

> block 931551 with 941780
Bug #931551 [release.debian.org] transition: llvm-defaults to 8
931551 was not blocked by any bugs.
931551 was not blocking any bugs.
Added blocking bug(s) of 931551: 941780
> block 931551 with 939687
Bug #931551 [release.debian.org] transition: llvm-defaults to 8
931551 was blocked by: 941780
931551 was not blocking any bugs.
Added blocking bug(s) of 931551: 939687
> thanks
Stopping processing here.

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

Processed: reassign 940973 to strip-nondeterminism ..., bug 940973 is not forwarded

[Debian Bug Tracking System]

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

> reassign 940973 strip-nondeterminism 1.6.0-1
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Bug reassigned from package 'src:libarchive-zip-perl' to 'strip-nondeterminism'.
No longer marked as found in versions libarchive-zip-perl/1.66-1 and 
libarchive-zip-perl/1.66-2.
Ignoring request to alter fixed versions of bug #940973 to the same values 
previously set
Bug #940973 [strip-nondeterminism] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Marked as found in versions strip-nondeterminism/1.6.0-1.
> retitle 940973 strip-nondeterminism: broken zip file 
> t/fixtures/zip/bug_803503.zip.in in test suite
Bug #940973 [strip-nondeterminism] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Changed Bug title to 'strip-nondeterminism: broken zip file 
t/fixtures/zip/bug_803503.zip.in in test suite' from 'libarchive-zip-perl 
breaks strip-nondeterminism autopkgtest: error: becoming 
Archive::Zip::DirectoryMember'.
> notforwarded 940973
Bug #940973 [strip-nondeterminism] strip-nondeterminism: broken zip file 
t/fixtures/zip/bug_803503.zip.in in test suite
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

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

Bug#942404: discosnp: flaky autopkgtest: discoRes_k_31_c_auto_D_100_P_1_b_0_coherent.fa: No such file or directory

[Paul Gevers]

Source: discosnp
Version: 2.3.0-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

With a recent upload of python-defaults to unstable, the autopkgtest of
discosnp failed in testing when that autopkgtest was run with the binary
packages of python-defaults from unstable. However, as we check for
regression, the reference was retried and failed as well, without
further changes. I looked into the history of your autopkgtest and it
fails very often.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. Please either fix the test to be more robust, or or use the
"flaky" restriction for the offending test until a solution has been found.

I copied the output at the bottom of this report. All the failing tests
that I inspected look like it.

I'll have the migration software ignore the results of your autopkgtest
until this bug is fixed.

Paul

https://ci.debian.net/data/autopkgtest/unstable/amd64/d/discosnp/3153055/log.gz

autopkgtest [08:02:13]: test run-unit-test: [---
use read set: fof.txt
Running discoSnp++ 2.3.X, in directory /usr with following parameters:
 read_sets=fof.txt
 prefix=discoRes_k_31_c_auto
 c=auto
 C=2147483647
 k=31
 b=0
 d=1
 D=100
 starting date=Mon Oct 14 08:02:14 UTC 2019


 GRAPH CREATION  ###

/usr/bin/dbgh5 -in
fof.txt_discoRes_k_31_c_auto_D_100_P_1_b_0_removemeplease -out
discoRes_k_31_c_auto -kmer-size 31 -abundance-min auto -abundance-max
2147483647 -solidity-kind one -verbose 1 -skip-bcalm -skip-bglue -no-mphf

[DSK: counting kmers ]  0%   elapsed:   0 min 0
 sec   remaining:   0 min 0  sec   cpu:  -1.0 %   mem: [  14,   14,
36] MB
[DSK: Pass 1/1, Step 1: partitioning ]  0%   elapsed:   0 min 0
 sec   remaining:   0 min 0  sec   cpu:  -1.0 %   mem: [  46,   46,
46] MB
EXCEPTION: Pool allocation failed for 128 bytes (kmers alloc),
mainbuffer is null?. Current usage is 144 and capacity is 5242881056
Pool allocation failed for 1288 bytes (kmers alloc), mainbuffer is
null?. Current usage is 1448 and capacity is 5242881056

there was a problem with graph construction
diff: discoRes_k_31_c_auto_D_100_P_1_b_0_coherent.fa: No such file or
directory
*** Test: FAILURE on diff .fa
autopkgtest [08:02:15]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature

Bug#942403: golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership autopkgtest

[Paul Gevers]

Hi,

On 15-10-2019 21:00, Paul Gevers wrote:
> github.com/CanonicalLtd/raft-membership
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
> github.com/CanonicalLtd/raft-membership
> # github.com/CanonicalLtd/raft-test/internal/network
> src/github.com/CanonicalLtd/raft-test/internal/network/network.go:53:2: 
> cannot use transport (type *eventTransport) as type raft.Transport in return 
> argument:
>   *eventTransport does not implement raft.Transport (missing TimeoutNow 
> method)
> FAIL  github.com/CanonicalLtd/raft-membership [build failed]
> dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
> github.com/CanonicalLtd/raft-membership returned exit code 2
> make: *** [debian/rules:4: build] Error 255

By the way, this also looks very much like the error message in
golang-github-canonicalltd-raft-test

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-canonicalltd-raft-test/3142465/log.gz

github.com/CanonicalLtd/raft-test/internal/network
# github.com/CanonicalLtd/raft-test/internal/network
src/github.com/CanonicalLtd/raft-test/internal/network/network.go:53:2:
cannot use transport (type *eventTransport) as type raft.Transport in
return argument:
*eventTransport does not implement raft.Transport (missing TimeoutNow
method)
dh_auto_build: cd obj-x86_64-linux-gnu && go install
-gcflags=all=\"-trimpath=/tmp/autopkgtest-lxc.bqaeo2pm/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-asmflags=all=\"-trimpath=/tmp/autopkgtest-lxc.bqaeo2pm/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\"
-v -p 2 github.com/CanonicalLtd/raft-test
github.com/CanonicalLtd/raft-test/internal/election
github.com/CanonicalLtd/raft-test/internal/event
github.com/CanonicalLtd/raft-test/internal/fsms
github.com/CanonicalLtd/raft-test/internal/logging
github.com/CanonicalLtd/raft-test/internal/network returned exit code 2



signature.asc
Description: OpenPGP digital signature

Bug#942403: golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership autopkgtest

[Paul Gevers]

Source: golang-github-hashicorp-raft,golang-github-canonicalltd-raft-membership
Control: found -1 golang-github-hashicorp-raft/1.1.1-2
Control: found -1 
golang-github-canonicalltd-raft-membership/0.0~git20180413.3846634-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of golang-github-hashicorp-raft the autopkgtest of
golang-github-canonicalltd-raft-membership fails in testing when that
autopkgtest is run with the binary packages of
golang-github-hashicorp-raft from unstable. It passes when run with only
packages from testing. In tabular form:
pass fail
golang-github-hashicorp-raftfrom testing 1.1.1-2
golang-github-canonicalltd-raft-membership  from testing 
0.0~git20180413.3846634-1
all others  from testing from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of
golang-github-hashicorp-raft to testing [1]. Due to the nature of this
issue, I filed this bug report against both packages. Can you please
investigate the situation and reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=golang-github-hashicorp-raft

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-canonicalltd-raft-membership/3148902/log.gz

github.com/CanonicalLtd/raft-membership
   dh_auto_test -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
github.com/CanonicalLtd/raft-membership
# github.com/CanonicalLtd/raft-test/internal/network
src/github.com/CanonicalLtd/raft-test/internal/network/network.go:53:2: cannot 
use transport (type *eventTransport) as type raft.Transport in return argument:
*eventTransport does not implement raft.Transport (missing TimeoutNow 
method)
FAILgithub.com/CanonicalLtd/raft-membership [build failed]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
github.com/CanonicalLtd/raft-membership returned exit code 2
make: *** [debian/rules:4: build] Error 255



signature.asc
Description: OpenPGP digital signature

Processed: golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> found -1 golang-github-hashicorp-raft/1.1.1-2
Bug #942403 
[src:golang-github-hashicorp-raft,src:golang-github-canonicalltd-raft-membership]
 golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership 
autopkgtest
Marked as found in versions golang-github-hashicorp-raft/1.1.1-2.
> found -1 golang-github-canonicalltd-raft-membership/0.0~git20180413.3846634-1
Bug #942403 
[src:golang-github-hashicorp-raft,src:golang-github-canonicalltd-raft-membership]
 golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership 
autopkgtest
Marked as found in versions 
golang-github-canonicalltd-raft-membership/0.0~git20180413.3846634-1.

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

Bug#942334: marked as done (cluster-glue: flaky autopkgtest: test logd)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 18:05:55 +
with message-id 
and subject line Bug#942334: fixed in cluster-glue 1.0.12-14
has caused the Debian Bug report #942334,
regarding cluster-glue: flaky autopkgtest: test logd
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.)


-- 
942334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cluster-glue
Version: 1.0.12-13
Severity: serious
Tags: sid bullseye buster
X-Debbugs-CC: debian...@lists.debian.org sebast...@breakpoint.cc
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

With a recent upload of openssl to the security archive for stable the
autopkgtest of cluster-glue failed in stable when that autopkgtest was
run with the binary packages of openssl from proposed-updates. However,
when the test was retried, the test passed. I looked into the history of
your autopkgtest and it fails occasionally (albeit the latest one isn't
your packages fault).

Because uploads to proposed-updates are monitored for regressions (and
unstable-to-testing migration software now blocks on regressions in
testing), flaky tests, i.e. tests that flip between passing and failing
without changes to the list of installed packages, are causing people
unrelated to your package to spend time on these tests. Please either
fix the test to be more robust, or or use the "flaky" restriction for
the offending test until a solution has been found.

I copied the output at the bottom of this report.

I'll have the migration software ignore the results of your autopkgtest
until this bug is fixed.

Paul

https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cluster-glue/2927678/log.gz

https://ci.debian.net/data/autopkgtest/stable/amd64/c/cluster-glue/3161064/log.gz

autopkgtest [00:10:05]: test logd: [---
=== service ===
● logd.service - ha_logd logging daemon
   Loaded: loaded (/lib/systemd/system/logd.service; enabled; vendor
preset: enabled)
   Active: active (running) since Mon 2019-10-14 00:09:53 UTC; 12s ago
 Docs: man:ha_logd(8)
 Main PID: 1592 (ha_logd)
Tasks: 2 (limit: 4915)
   Memory: 1.1M
   CGroup: /system.slice/logd.service
   ├─1592 ha_logd: read process
   └─1594 ha_logd: write process

Oct 14 00:09:53 autopkgtest-stable-amd64 systemd[1]: Starting ha_logd
logging daemon...
Oct 14 00:09:53 autopkgtest-stable-amd64 systemd[1]: Started ha_logd
logging daemon.
Oct 14 00:09:53 autopkgtest-stable-amd64 logd[1592]: [1592]: info: logd
started with /etc/logd.cf.
Oct 14 00:09:53 autopkgtest-stable-amd64 logd[1592]: [1592]: WARN: Core
dumps could be lost if multiple dumps occur.
Oct 14 00:09:53 autopkgtest-stable-amd64 logd[1592]: [1592]: WARN:
Consider setting non-default value in /proc/sys/kernel/core_pattern (or
equivalent) for maximum supportability
Oct 14 00:09:53 autopkgtest-stable-amd64 logd[1592]: [1592]: WARN:
Consider setting /proc/sys/kernel/core_uses_pid (or equivalent) to 1 for
maximum supportability
=== ha_logger ===
autopkgtest [00:10:06]: test logd: ---]
autopkgtest [00:10:06]: test logd:  - - - - - - - - - - results - - - -
- - - - - -
logd FAIL non-zero exit status 1




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cluster-glue
Source-Version: 1.0.12-14

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

Debian distribution maintenance software
pp.
Valentin Vidic  (supplier of updated cluster-glue 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, 15 Oct 2019 19:22:27 +0200
Source: cluster-glue
Architecture: source
Version: 1.0.12-14
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Valentin Vidic 
Closes: 942334
Changes:
 cluster-glue (1.0.12-14) unstable; urgency=medium
 .
   * Try to fix flaky autopkgtest (Closes: #942334)
   * Use debhelper v12
   * Update Standards-Version to 4.4.1
   * Drop unused lintian 

Bug#939460: marked as done (libmojo-ioloop-readwriteprocess-perl: FTBFS and autopkgtest failures with mojo 8.23)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 17:34:28 +
with message-id 
and subject line Bug#939460: fixed in libmojo-ioloop-readwriteprocess-perl 
0.24-1
has caused the Debian Bug report #939460,
regarding libmojo-ioloop-readwriteprocess-perl: FTBFS and autopkgtest failures 
with mojo 8.23
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.)


-- 
939460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmojolicious-perl, libmojo-ioloop-readwriteprocess-perl
Control: found -1 libmojolicious-perl/8.23+dfsg-1
Control: found -1 libmojo-ioloop-readwriteprocess-perl/0.23-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of libmojolicious-perl the autopkgtest of
libmojo-ioloop-readwriteprocess-perl fails in testing when that
autopkgtest is run with the binary packages of libmojolicious-perl from
unstable. It passes when run with only packages from testing. In tabular
form:
 passfail
libmojolicious-perl  from testing8.23+dfsg-1
libmojo-ioloop-readwriteprocess-perl from testing0.23-1
all others   from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of
libmojolicious-perl to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package? If needed,
please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=libmojolicious-perl

https://ci.debian.net/data/autopkgtest/testing/amd64/libm/libmojo-ioloop-readwriteprocess-perl/2886679/log.gz

ok 1 - mock
Invalid path at
/usr/share/perl5/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 30.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 1.
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
t/10_cgroupv2.t ..

[...]

Test Summary Report
---
t/10_cgroupv1.t(Wstat: 65280 Tests: 1 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
t/10_cgroupv2.t(Wstat: 65280 Tests: 1 Failed: 0)
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=14, Tests=46, 217 wallclock secs ( 0.12 usr  0.01 sys +  8.17 cusr
 1.06 csys =  9.36 CPU)
Result: FAIL



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libmojo-ioloop-readwriteprocess-perl
Source-Version: 0.24-1

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated 
libmojo-ioloop-readwriteprocess-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 16 Oct 2019 02:03:38 +0900
Source: libmojo-ioloop-readwriteprocess-perl
Architecture: source
Version: 0.24-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Hideki Yamane 
Closes: 939460
Changes:
 libmojo-ioloop-readwriteprocess-perl (0.24-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #939460)
 .
   [ gregor herrmann ]
   * Set Maintainer to Debian Perl Group.
   * Annotate test-only build dependencies with .
   * Declare compliance with Debian Policy 4.4.0.
   * Drop unneeded version constraints from (build) dependencies.
   * debian/watch: use uscan version 4.
   * Remove obsolete fields Name, Contact from debian/upstream/metadata.
   * One debhelper.* is enough in Build-Depends.
 .
   [ Hideki Yamane ]
   * debian/control
 - set 

Bug#935562: ITP: google-auth-httplib2 -- Google Authentication Library: httplib2 transport

[Valentin Vidić]

Hi,

python3-google-auth-httplib2 is now in unstable, could you update
python3-googleapi to use it?

-- 
Valentin

Processed: transition blocks

[Debian Bug Tracking System]

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

> block 939580 by 941907
Bug #939580 [src:liquidsoap] liquidsoap: FTBFS with new ffmpeg ocaml library
939580 was not blocked by any bugs.
939580 was not blocking any bugs.
Added blocking bug(s) of 939580: 941907
>
End of message, stopping processing here.

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

Bug#942364: [patch] perl6-* (vendored) packages out of the reach of perl6 path

[gregor herrmann]

On Tue, 15 Oct 2019 02:17:24 -0700, Mo Zhou wrote:

> Could you please double check the -6 revision? If it looks good,
> I'll continue and upload it to unstable and close this bug.

After upgrading rakudo from 2019.07.1-4 to 2019.07.1-6:

% zef
===SORRY!===
Could not find Zef::CLI at line 3 in:
inst#/home/gregoa/.perl6
inst#/usr/share/perl6/site
inst#/usr/share/perl6/vendor
inst#/usr/share/perl6/core
ap#
nqp#
perl5#

(i.e. same as before)

/usr/lib/perl6 doesn't exist anymore; /usr/share/perl6 has lots of
stuff with zef:

/usr/share/perl6/debian-sources/perl6-zef
/usr/share/perl6/debian-sources/perl6-zef/resources
/usr/share/perl6/debian-sources/perl6-zef/resources/scripts
/usr/share/perl6/debian-sources/perl6-zef/resources/scripts/perl5tar.pl
/usr/share/perl6/debian-sources/perl6-zef/resources/scripts/win32http.ps1
/usr/share/perl6/debian-sources/perl6-zef/resources/scripts/win32unzip.ps1
/usr/share/perl6/debian-sources/perl6-zef/resources/config.json
/usr/share/perl6/debian-sources/perl6-zef/lib
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Extract.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/LocalCache.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/Ecosystems.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository/MetaCPAN.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/URI.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/FileSystem.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/SystemInfo.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Utils/SystemQuery.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Config.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Repository.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Install.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Fetch.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/CLI.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Client.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Report.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/InstallPM6.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/P6CReporter.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/FetchPath.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/git.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/prove.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell/download.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell/unzip.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/LegacyBuild.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/curl.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/tar.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/p5tar.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/PowerShell.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/wget.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/DistributionBuilder.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/unzip.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/Shell/Test.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Service/TAP.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution/DependencySpecification.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution/Local.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Identity.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Test.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Build.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef/Distribution.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/Zef.pm6
/usr/share/perl6/debian-sources/perl6-zef/lib/.precomp
/usr/share/perl6/debian-sources/perl6-zef/lib/.precomp/.lock
/usr/share/perl6/debian-sources/perl6-zef/lib/.precomp/1994AC47AA915F09C497C113636DA8687C32F278
/usr/share/perl6/debian-sources/perl6-zef/lib/.precomp/1994AC47AA915F09C497C113636DA8687C32F278/8B
/usr/share/perl6/debian-sources/perl6-zef/lib/.precomp/1994AC47AA915F09C497C113636DA8687C32F278/8B/8B6C7081E1781D3D2108051C82C1C3C66DFD29D6
/usr/share/perl6/debian-sources/perl6-zef/lib/.precomp/1994AC47AA915F09C497C113636DA8687C32F278/8B/8B6C7081E1781D3D2108051C82C1C3C66DFD29D6.repo-id
/usr/share/perl6/debian-sources/perl6-zef/lib/.precomp/1994AC47AA915F09C497C113636DA8687C32F278/89

Bug#925745: libgtextutils is marked for autoremoval from testing

[Andreas Tille]

Hi Olivier, any solution?

On Tue, Oct 15, 2019 at 04:39:04AM +, Debian testing autoremoval watch 
wrote:
> libgtextutils 0.7-6 is marked for autoremoval from testing on 2019-10-25
> 
> It is affected by these RC bugs:
> 925745: libgtextutils: ftbfs with GCC-9
> 
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Bug#940279: marked as done (wham-align: FTBFS with GCC 9: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 16:20:08 +
with message-id 
and subject line Bug#940279: fixed in wham-align 0.1.5-2
has caused the Debian Bug report #940279,
regarding wham-align: FTBFS with GCC 9: undefined reference to `pthread_create'
to be marked as done.

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

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


-- 
940279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wham-align
Version: 0.1.5-1
Severity: serious
Tags: bullseye sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Hi Maintainer

As can be seen on reproducible builds [1], wham-align FTBFS with GCC 9.


Regards
Graham


[1]



g++ -lpthread -o wham sequence.o hash.o embedhash.o main.o aligner.o
interval.o edit_distance.o error.o short.o hitset.o model.o
perfcounters.o writer.o
g++ -lpthread -o wham-build sequence.o hash.o embedhash.o builder.o
aligner.o interval.o edit_distance.o error.o short.o hitset.o model.o
perfcounters.o writer.o
/usr/bin/ld: main.o: in function `align(char*, AlignInfo*, char*, int)':
./main.cpp:466: undefined reference to `pthread_create'
/usr/bin/ld: ./main.cpp:466: undefined reference to `pthread_create'
/usr/bin/ld: ./main.cpp:475: undefined reference to `pthread_join'
collect2: error: ld returned 1 exit status
make[1]: *** [makefile:19: wham] Error 1
make[1]: Leaving directory '/build/1st/wham-align-0.1.5'
dh_auto_build: make -j16 "INSTALL=install --strip-program=true"
returned exit code 2
--- End Message ---
--- Begin Message ---
Source: wham-align
Source-Version: 0.1.5-2

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

Debian distribution maintenance software
pp.
Steffen Moeller  (supplier of updated wham-align package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Oct 2019 17:55:46 +0200
Source: wham-align
Architecture: source
Version: 0.1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Steffen Moeller 
Changed-By: Steffen Moeller 
Closes: 940279
Changes:
 wham-align (0.1.5-2) unstable; urgency=medium
 .
   * Fixed gcc-9 build failure (Closes: #940279)
   * d/u/metadata: Added ref to conda
Checksums-Sha1:
 ffaf32122ecde7135c6976ad34e15ed97ba41be9 1874 wham-align_0.1.5-2.dsc
 c5250f8721a991666ad55e9cd2c12c813dc9632a 2972 wham-align_0.1.5-2.debian.tar.xz
 95d51714e052439a3377c0d4645886210061c453 5572 
wham-align_0.1.5-2_source.buildinfo
Checksums-Sha256:
 74453696e4d62ba1b67414d18edddcc731097bd8f692156d0f4e45cd6241b63f 1874 
wham-align_0.1.5-2.dsc
 52452fa93d856b973abc143fcd59f4717c715933761b2ff268e0ba406d1322bf 2972 
wham-align_0.1.5-2.debian.tar.xz
 7dfa15b5d6019c5964fc92f93b75c53a1422a1d64b5b33493f8750b15679ca18 5572 
wham-align_0.1.5-2_source.buildinfo
Files:
 0327a8666a3418a90d73effe1d8bf160 1874 science optional wham-align_0.1.5-2.dsc
 3dee5a72c5d099f6eec9eae22cde43ac 2972 science optional 
wham-align_0.1.5-2.debian.tar.xz
 40538abe4e62e69dd9db9c5cbb4ad729 5572 science optional 
wham-align_0.1.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEhMGXeonn7+0+XKYuL9i+2sAg7tEFAl2l7TcTHG1vZWxsZXJA
ZGViaWFuLm9yZwAKCRAv2L7awCDu0TB5EACHZhs/IsrYq1QunVXrozsOpAn60X8L
vqBtphzw0aZeebt6jordjmoZvg7r4sPQfgoDVRTu1iGa9Uj1TfnXYWrdj4+w7hHG
OGwQL9ua1QOqtWfwjmVURXMq9qadw/yq9oikjv9uJsgjD3IR/ex473mkK942sHTS
oatYq/7CYHGJvN3yZC4HYx+Vx6c1U7og0ei265pSIFIIB3WK7PVnuf6wi9QhwQ3p
XGrOKTnJWIlb9RZqCPdwTn2JLA/tKlvS8H/SvX6jGfckxEgE5LS6Zxo2qtulwfnE
k2pi9OqedkWIST7vULjYO9fgdvRoNHOoRitQq1iY2dUhPc8eKuAlpv34yQ3i1a4J
3ol4EUp9LPGl1GlXu9yPkKcqiRieXYhWu3gtJ/z2bECybD9MYfPW0LEEgw6AxeeI
ttj/6j84Or/mi+MzVv1Qd9A0GTxSSv+1GPZHLogLyzChSJNesUf1Ajzlqos+fHI0
DDocxTFvVWnrbUK7G1mhMTnJFvV0GjVtpjm+3EzfRH+AR+Lk5UfI+wV4X5Y6lSKe
4fSwVKa7F+AzlnNFzr3jNx92ZQzXF8xZ2rshiY2CX6Dar4aQ+DeytXL7nTXYnCkR
pv5xpVHjXBRNz7hCNXWG9ECuKXEVqAxX6z2xoWuXarBwlKGbo1wCQmTzb6IIaIgS
jJiWl9JWeheGkg==
=qN2Y
-END PGP SIGNATURE End Message ---

Bug#942393: mlpack: downloads stuff from internet during build?

[Gianfranco Costamagna]

Source: mlpack
Version: 3.2.1-1
Severity: serious

Hello, according to the build log:
-- Found Armadillo: /usr/lib/libarmadillo.so (found suitable version "9.600.5", 
minimum required is "8.400.0") 
-- Armadillo libraries: /usr/lib/libarmadillo.so
-- Could NOT find STB_IMAGE (missing: STB_IMAGE_INCLUDE_DIR) 
-- [download 3% complete]
-- [download 5% complete]
-- [download 10% complete]
-- [download 16% complete]
-- [download 18% complete]
-- [download 20% complete]
-- [download 24% complete]
-- [download 30% complete]
-- [download 31% complete]
-- [download 36% complete]
-- [download 37% complete]
-- [download 39% complete]
-- [download 44% complete]
-- [download 50% complete]
-- [download 54% complete]
-- [download 60% complete]
-- [download 64% complete]
-- [download 65% complete]
-- [download 67% complete]
-- [download 70% complete]
-- [download 72% complete]
-- [download 75% complete]
-- [download 77% complete]
-- [download 78% complete]
-- [download 80% complete]
-- [download 83% complete]
-- [download 84% complete]
-- [download 90% complete]
-- [download 96% complete]
-- [download 98% complete]
-- [download 99% complete]
-- [download 100% complete]
-- [download 20% complete]
-- [download 30% complete]
-- [download 49% complete]
-- [download 53% complete]
-- [download 61% complete]
-- [download 74% complete]
-- [download 86% complete]
-- [download 90% complete]
-- [download 98% complete]
-- [download 100% complete]
-- Successfully downloaded stb into 
/<>/obj-x86_64-linux-gnu/deps/stb/
-- Found Ensmallen: /usr/include (found suitable version "2.10.3", minimum 
required is "2.10.0") 
-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   program_options
--   unit_test_framework
--   serialization
-- Found OpenMP_C: -fopenmp (found version "4.5") 
-- Found OpenMP_CXX: -fopenmp (found version "4.5") 
-- Found OpenMP: TRUE (found version "4.5")  


I discovered this in Ubuntu build logs, because there internet connection is 
more strictly forbidden, but this seems to be happening in Debian in the very 
same way, just not fatal for builders

Gianfranco

Processed: upstream

[Debian Bug Tracking System]

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

> forwarded 941960 
> https://gitlab.com/paddatrapper/log-out-button-gnome-extension/issues/6
Bug #941960 [gnome-shell-extension-log-out-button] 
gnome-shell-extension-log-out-button: fails to load under gnome-shell 3.34: 
TypeError: System._actionsItem is undefined
Set Bug forwarded-to-address to 
'https://gitlab.com/paddatrapper/log-out-button-gnome-extension/issues/6'.
>
End of message, stopping processing here.

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

Bug#942073: marked as done (marisa: perl bindings are broken when linked with gcc-9)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 14:50:33 +
with message-id 
and subject line Bug#942073: fixed in marisa 0.2.5-4
has caused the Debian Bug report #942073,
regarding marisa: perl bindings are broken when linked 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.)


-- 
942073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmarisa-perl
Version: 0.2.5-3
Severity: grave
Control: block 935737 with -1

As noticed by the autopkgtest checks, the marisa Perl bindings are
totally broken in sid after the recent Perl 5.30 rebuild:

  $ perl -e 'use marisa'
  Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/marisa/marisa.so' for 
module marisa: /usr/lib/x86_64-linux-gnu/perl5/5.30/auto/marisa/marisa.so: 
undefined symbol: _ZTVN10__cxxabiv120__si_class_type_infoE at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 193.
   at /usr/lib/x86_64-linux-gnu/perl5/5.30/marisa.pm line 11.
  Compilation failed in require at -e line 1.
  BEGIN failed--compilation aborted at -e line 1.
 
Rebuilding marisa in testing with Perl 5.28 triggers the same behaviour,
so it's not a change in Perl 5.30 that broke it. The previous sid build
in July is not broken.

It looks like this regressed with the gcc 8 -> 9 move. Linking the
DSO manually with gcc-8 makes it go away, as seen below.

I have no idea what goes wrong here, but I noticed that broken versions
of blib/arch/auto/marisa/marisa.so have no NEEDED entry for libmarisa.so.0
(as seen with 'objdump -p').

 reproduce the error 

  # apt build-dep libmarisa-perl
  $ ./debian/rules build
  $ cd bindings/perl
  $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I blib/lib -e 
'use marisa'
  Can't load 'blib/arch/auto/marisa/marisa.so' for module marisa: 
blib/arch/auto/marisa/marisa.so: undefined symbol: 
_ZTVN10__cxxabiv120__si_class_type_infoE at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 193.
   at blib/lib/marisa.pm line 11.
  Compilation failed in require at -e line 1.
  BEGIN failed--compilation aborted at -e line 1.

 explicitly link with gcc-8, no error ---

  # apt install gcc-8
  $ gcc-8 -shared -L/usr/local/lib -L../../lib/marisa/.libs -lmarisa 
-fstack-protector -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  marisa-swig.o 
marisa-swig_wrap.o  -o blib/arch/auto/marisa/marisa.so
  $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I blib/lib -e 
'use marisa'

 explicitly link with gcc-9, same error again ---

  $ gcc-9 -shared -L/usr/local/lib -L../../lib/marisa/.libs -lmarisa 
-fstack-protector -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  marisa-swig.o 
marisa-swig_wrap.o  -o blib/arch/auto/marisa/marisa.so
  $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I blib/lib -e 
'use marisa'
  Can't load 'blib/arch/auto/marisa/marisa.so' for module marisa: 
blib/arch/auto/marisa/marisa.so: undefined symbol: 
_ZTVN10__cxxabiv120__si_class_type_infoE at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 193.
   at blib/lib/marisa.pm line 11.
  Compilation failed in require at -e line 1.
  BEGIN failed--compilation aborted at -e line 1.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: marisa
Source-Version: 0.2.5-4

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated marisa 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, 15 Oct 2019 09:46:57 -0400
Source: marisa
Architecture: source
Version: 0.2.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Closes: 942073
Changes:
 marisa (0.2.5-4) unstable; urgency=medium
 .
   * debian/control:
 + Bump Standards-Version to 4.4.1.
   * debian/rules: Fix build around perl and gcc-9. Patch provided
 by Niko Tyni. (Closes: #942073)
   * Recover usage of dh_dwz again since the issue has been solved.
Checksums-Sha1:
 

Bug#936684: marked as done (h5py: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 13:21:19 +
with message-id 
and subject line Bug#936684: fixed in h5py 2.10.0-2
has caused the Debian Bug report #936684,
regarding h5py: 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.)


-- 
936684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:h5py
Version: 2.9.0-7
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:h5py

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: h5py
Source-Version: 2.10.0-2

We believe that the bug you reported is fixed in the latest version of
h5py, 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.
Ole Streicher  (supplier of updated h5py 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, 15 Oct 2019 14:41:14 +0200
Source: h5py
Architecture: source
Version: 2.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ole Streicher 
Closes: 936684
Changes:
 h5py (2.10.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop Python 2 package. Closes: #936684
Checksums-Sha1:
 a88fd0cd6015091923dedc8ac4308e349f5aaccf 2493 h5py_2.10.0-2.dsc
 db4fb805b4276276e23f0c34aef6c02b8cdbf592 10576 h5py_2.10.0-2.debian.tar.xz
Checksums-Sha256:
 500f0abfb489a74d552c6972ae1fb13e64fbb8db5fd5679163759aac9903798c 2493 
h5py_2.10.0-2.dsc
 6a6a93b8d33084fbf7be53a6af0dcbff75a8d5d85ec962da9ce62bf748246bdc 10576 
h5py_2.10.0-2.debian.tar.xz
Files:
 e2213e98643cde0db80321e996cfdbd1 2493 python optional h5py_2.10.0-2.dsc
 e416d6225ece332498d2dc74e4ff6d20 10576 python optional 
h5py_2.10.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl2lwgQACgkQcRWv0HcQ

Bug#942193: dwz: dh_dwz freecad build regression: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed.

[Matthias Klose]

On 14.10.19 10:10, Tom de Vries wrote:

On 13-10-2019 21:34, Kurt Kremitzki wrote:

Hi Matthias,

On Saturday, October 12, 2019 12:34:30 PM CDT Matthias Klose wrote:

Control: tags -1 + moreinfo
Control: severity -1 grave

please could you attach the binary, or put it somewhere on the web?



Sorry, which binary are you referring to?



Hi,

in order to reproduce a dwz problem, we need:
- the dwz command line that triggered the assertion, and
- the files that were used as arguments. [ And since dwz modifies files
   in place, we need the files as they were before dwz was run. ]


Here are a few links in the meantime that might help, buildd logs for the
i386/s390x/mipsel failures:

https://buildd.debian.org/status/fetch.php?
pkg=freecad=i386=0.18.3%2Bdfsg1-3=1568751036=0

https://buildd.debian.org/status/fetch.php?
pkg=freecad=mipsel=0.18.3%2Bdfsg1-3=1568784049=0

https://buildd.debian.org/status/fetch.php?
pkg=freecad=s390x=0.18.3%2Bdfsg1-3=1569764936=0



I think it would be the easiest for me to reproduce on i386, so if you
could provide the reproduction information for that one, that would be
great.


https://people.debian.org/~doko/tmp/dwz-freecad.tar.xz
https://people.debian.org/~doko/tmp/dwz-freecad.sh

Bug#942379: appstream-generator: FTBFS in sid

[Gianfranco Costamagna]

Source: appstream-generator
Version: 0.8.0-1
Severity: serious

http://debomatic-amd64.debian.net/distribution#unstable/appstream-generator/0.8.0-1/buildlog

   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --prefix=/usr --buildtype=plain -Ddownload-js=false
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu --prefix=/usr 
--buildtype=plain -Ddownload-js=false
The Meson build system
Version: 0.52.0
Source dir: /<>
Build dir: /<>/obj-x86_64-linux-gnu
Build type: native build
Project name: AppStream Generator
Project version: 0.8.0
Appending DFLAGS from environment: '-O -g -release -wi'
Appending LDFLAGS from environment: ['-Wl,-z,relro']
Appending DFLAGS from environment: '-O -g -release -wi'
Appending LDFLAGS from environment: ['-Wl,-z,relro']
D compiler for the host machine: ldc2 (llvm 1.17.0 "LDC - the LLVM D compiler 
(1.17.0):")
D linker for the host machine: GNU ld.gold 2.33
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (0.29)
Run-time dependency glibd-2.0 found: YES 2.1.0
Run-time dependency appstream found: YES 0.12.9
Run-time dependency lmdb found: YES 0.9.22
Run-time dependency libarchive found: YES 3.4.0
Run-time dependency cairo found: YES 1.16.0
Run-time dependency gdk-pixbuf-2.0 found: YES 2.40.0
Run-time dependency librsvg-2.0 found: YES 2.44.15
Run-time dependency libcurl found: YES 7.66.0
Run-time dependency freetype2 found: YES 22.1.16
Run-time dependency pango found: YES 1.42.3
Run-time dependency fontconfig found: YES 2.13.1
Program girtod found: YES (/usr/bin/girtod)
Message: Generating AppStream D interfaces from GIR...

meson.build:49:4: ERROR: Problem encountered: Unable to build D intefaces from 
GIR:
Error /usr/share/gir-1.0/GObject-2.0.gir(48): Unexpected tag: function-macro in 
GirPackage: gobject


A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
==> meson-logs/meson-log.txt <==


while in Ubuntu it fails with a slightly different problem:
Error /usr/share/gir-1.0/AppStream-1.0.gir(12722): Unexpected tag: 
function-macro in GirPackage: appstream
https://launchpad.net/ubuntu/+source/appstream-generator/0.8.0-1


Can you please have a look?

G.

Processed: Re: Bug#942365: libgtk2-perl: Package uninstallable

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 942135 -1
Bug #942135 [src:libgtk2-perl] libgtk2-perl: FTBFS with gdk-pixbuf 2.39+ and 
not built against perl 5.30
Bug #942365 [src:libgtk2-perl] libgtk2-perl: Package uninstallable
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/perl-gtk2/issues/3'.
Severity set to 'serious' from 'important'
Marked as found in versions libgtk2-perl/2:1.24993-1.
Added tag(s) a11y, upstream, and ftbfs.
Merged 942135 942365

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

Bug#939571: Fails to import

[Carlos Pascual]

Just adding that I checked and 0.10.0-1 is not affected.

Note this bug is affecting the to build the taurus-pyqtgraph package:

https://salsa.debian.org/science-team/taurus-pyqtgraph/-/jobs/362247

Bug#942284: [Pkg-net-snmp-devel] Bug#942284: libsnmp-perl: perl module SNMP broken

[Craig Small]

Hi All,
  Thanks again for the additional information.  The build system really
doesn't work with parallel builds.  I find random things changing
depending, I guess on many race conditions. While I rather not disable
parallel builds, it seems the only way to get a sensible repeatable outcome.

I suspect there is some strangeness of the standardall target, often some
libraries are built and others (eg netsnmpmib) are not.
So the fix is, no parallel builds :(

Yes I saw the upstream commit comment. It's not the Makefile, its parallel
builds!

 - Craig

Bug#924840: marked as done (highwayhash: FTBFS: dh_makeshlibs: failing due to earlier errors)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 03:14:15 -0700
with message-id <4281bd1cfc5f7b7fbe0c4ad24c4c0...@debian.org>
and subject line FTBFS already fixed in sid
has caused the Debian Bug report #924840,
regarding highwayhash: FTBFS: dh_makeshlibs: failing due to earlier errors
to be marked as done.

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

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


-- 
924840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: highwayhash
Version: 0~git20181002.c5ee50b-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64

Hi,

During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -Wall -O3 -fPIC -pthread 
> -Wl,-z,relro -Wl,-z,now -pthread -shared obj/sip_hash.o obj/sip_tree_hash.o 
> obj/scalar_sip_tree_hash.o obj/arch_specific.o obj/instruction_sets.o 
> obj/nanobenchmark.o obj/os_specific.o obj/hh_portable.o obj/hh_avx2.o 
> obj/hh_sse41.o obj/c_bindings.o -o lib/libhighwayhash.so.0 
> -Wl,-soname,libhighwayhash.so.0
> mkdir -p /<>/debian/tmp//usr/lib/x86_64-linux-gnu/
> mkdir -p /<>/debian/tmp//usr/include//highwayhash
> install -m0444 lib/libhighwayhash.a 
> /<>/debian/tmp//usr/lib/x86_64-linux-gnu/
> install -m0555 lib/libhighwayhash.so 
> /<>/debian/tmp//usr/lib/x86_64-linux-gnu/
> install -m0444 highwayhash/*.h 
> /<>/debian/tmp//usr/include//highwayhash/
> make[2]: Leaving directory '/<>'
> mkdir -p debian/libhighwayhash0/usr/lib/x86_64-linux-gnu
> rename 's/.so/.so.0/' debian/tmp/usr/lib/x86_64-linux-gnu/*.so
> install -m0755 debian/tmp/usr/lib/x86_64-linux-gnu/*.so.0 \
>   debian/libhighwayhash0/usr/lib/x86_64-linux-gnu/
> mkdir -p debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu
> install -m0755 debian/tmp/usr/lib/x86_64-linux-gnu/*.a \
>   debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu/
> set -e; cd debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu/; \
>   ln -s libhighwayhash.so.0 libhighwayhash.so
> make[1]: Leaving directory '/<>'
>dh_install
>dh_installdocs
>dh_installchangelogs
>dh_installman
>dh_lintian
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_strip
>dh_makeshlibs
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libhighwayhash0/DEBIAN/symbols doesn't match 
> completely debian/libhighwayhash0.symbols
> --- debian/libhighwayhash0.symbols 
> (libhighwayhash0_0~git20181002.c5ee50b-3_amd64)
> +++ dpkg-gensymbolsg8mdHJ 2019-03-16 04:54:58.805876282 +
> @@ -64,7 +64,7 @@
>   
> _ZNSt23mersenne_twister_engineImLm64ELm312ELm156ELm31ELm13043109905998158313ELm29ELm6148914691236517205ELm17ELm8202884508482404352ELm37ELm1873444759240704ELm43ELm6364136223846793005EEclEv@Base
>  0~20180209-g14dedec
>   
> _ZNSt24uniform_int_distributionImEclISt20discard_block_engineISt26subtract_with_carry_engineImLm48ELm5ELm12EELm389ELm11mRT_RKNS0_10param_typeE@Base
>  0~20170419-g1f4a24f
>   
> _ZNSt6vectorISt4pairIjiESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
>  0~20180103-geeea446
> - 
> _ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base
>  0~20180209-g14dedec
> +#MISSING: 0~git20181002.c5ee50b-3# 
> _ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base
>  0~20180209-g14dedec
>   _ZNSt6vectorImSaImEE17_M_default_appendEm@Base 0~20180209-g14dedec
>   
> _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIjSaIjEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base
>  0~20170419-g1f4a24f
>   
> _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIjSaIjEEESt10_Select1stIS5_ESt4lessImESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
>  0~20170419-g1f4a24f
> dh_makeshlibs: failing due to earlier errors
> make: *** [debian/rules:22: binary] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/2019/03/15/highwayhash_0~git20181002.c5ee50b-3_testing.log

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

About the archive rebuild: The rebuild was done on EC2 VM 

Bug#925713: marked as done (highwayhash: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 03:14:15 -0700
with message-id <4281bd1cfc5f7b7fbe0c4ad24c4c0...@debian.org>
and subject line FTBFS already fixed in sid
has caused the Debian Bug report #925713,
regarding highwayhash: 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.)


-- 
925713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:highwayhash
Version: 0~git20190222.276dd7b-1
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/highwayhash_0~git20190222.276dd7b-1_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.

[...]
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -std=c++11 -Wall -O3 -fPIC -pthread 
-Wl,-z,relro -Wl,-z,now -pthread -shared obj/sip_hash.o obj/sip_tree_hash.o 
obj/scalar_sip_tree_hash.o obj/arch_specific.o obj/instruction_sets.o 
obj/nanobenchmark.o obj/os_specific.o obj/hh_portable.o obj/hh_avx2.o 
obj/hh_sse41.o obj/c_bindings.o -o lib/libhighwayhash.so.0 
-Wl,-soname,libhighwayhash.so.0
mkdir -p /<>/debian/tmp//usr/lib/x86_64-linux-gnu/
mkdir -p /<>/debian/tmp//usr/include//highwayhash
install -m0444 lib/libhighwayhash.a 
/<>/debian/tmp//usr/lib/x86_64-linux-gnu/
install -m0555 lib/libhighwayhash.so 
/<>/debian/tmp//usr/lib/x86_64-linux-gnu/
install -m0444 highwayhash/*.h 
/<>/debian/tmp//usr/include//highwayhash/
make[2]: Leaving directory '/<>'
mkdir -p debian/libhighwayhash0/usr/lib/x86_64-linux-gnu
rename 's/.so/.so.0/' debian/tmp/usr/lib/x86_64-linux-gnu/*.so
install -m0755 debian/tmp/usr/lib/x86_64-linux-gnu/*.so.0 \
debian/libhighwayhash0/usr/lib/x86_64-linux-gnu/
mkdir -p debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu
install -m0755 debian/tmp/usr/lib/x86_64-linux-gnu/*.a \
debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu/
set -e; cd debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu/; \
ln -s libhighwayhash.so.0 libhighwayhash.so
make[1]: Leaving directory '/<>'
   dh_install -a
   dh_installdocs -a
   dh_installchangelogs -a
   dh_installman -a
   dh_lintian -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_strip -a
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libhighwayhash0/DEBIAN/symbols doesn't match 
completely debian/libhighwayhash0.symbols
--- debian/libhighwayhash0.symbols 
(libhighwayhash0_0~git20190222.276dd7b-1_amd64)
+++ dpkg-gensymbolsrf8P0s   2019-03-26 16:55:12.688604997 +
@@ -42,6 +42,7 @@
  _ZN11highwayhash5CpuidEjjPj@Base 0~20170419-g1f4a24f
  _ZN11highwayhash6ApicIdEv@Base 0~20170419-g1f4a24f
  _ZN11highwayhash6MedianIfEET_PSt6vectorIS1_SaIS1_EE@Base 0~20170419-g1f4a24f
+ _ZN11highwayhash8Portable15HHStatePortable6UpdateERA4_Km@Base 
0~git20190222.276dd7b-1
  _ZNK11highwayhash11HighwayHashILj1EEclERA4_KmPKcmPA2_m@Base 
0~20170419-g1f4a24f
  _ZNK11highwayhash11HighwayHashILj1EEclERA4_KmPKcmPA4_m@Base 
0~20170419-g1f4a24f
  _ZNK11highwayhash11HighwayHashILj1EEclERA4_KmPKcmPm@Base 0~20170419-g1f4a24f
@@ 

Bug#938550: marked as done (spyder: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 09:51:16 +
with message-id 
and subject line Bug#938550: fixed in spyder 3.3.6+dfsg1-3
has caused the Debian Bug report #938550,
regarding spyder: 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.)


-- 
938550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:spyder
Version: 3.3.6+dfsg1-1
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:spyder

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: spyder
Source-Version: 3.3.6+dfsg1-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Oct 2019 10:25:18 +0800
Source: spyder
Architecture: source
Version: 3.3.6+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 938550 940783 940784
Changes:
 spyder (3.3.6+dfsg1-3) unstable; urgency=medium
 .
   * Team upload.
   * Standards-Version: 4.4.1
   * drop python-spyder (remove Python2). Closes: #938550, #940783.
 - main spyder package is now Python3
 - keep /usr/bin/spyder3 as main binary, link spyder to it
 - spyder3 package is a transitional package depending on spyder
   * drop older python3-spyderlib transitional package. Closes: #940784.
Checksums-Sha1:
 908bf7ff3c9b2f7723230d86a702d5779d45e014 2564 spyder_3.3.6+dfsg1-3.dsc
 72ed6dbb69f3e0cd996d96cb8a08200bf8f54adb 29948 
spyder_3.3.6+dfsg1-3.debian.tar.xz
Checksums-Sha256:
 739e21dd1a14832cb8ffe6211aa105199a814a17a3a643016897a192f023ea36 2564 
spyder_3.3.6+dfsg1-3.dsc
 

Bug#942364: [patch] perl6-* (vendored) packages out of the reach of perl6 path

[Mo Zhou]

Package: rakudo
Version: 2019.07.1-4
Severity: serious
Clarification: causes FTBFS of rdeps, can causes usability issue
X-Debbugs-CC: rober...@semistable.com, d...@debian.org

Hi co-maintainers,

After installing 2019.07.1-4 and perl6-zef, user would confront
the following issue:

~/D/p/rakudo ❯❯❯ zef
===SORRY!===
Could not find Zef::CLI at line 3 in:
inst#/home/lumin/.perl6
inst#/usr/share/perl6/site
inst#/usr/share/perl6/vendor
inst#/usr/share/perl6/core
ap#
nqp#
perl5#

Because the required files are put to /usr/lib/perl6/vendor,
a path that is inconsistent with upstream.

I've fixed this bug in the -6 revision and just uploaded it to
experimental. The perl6-* package products will be moved from
/usr/lib/perl6/vendor to /usr/share/perl6/vendor following the
upstream default. I modified the maintainer scripts to smooth
the upgrading process.

Could you please double check the -6 revision? If it looks good,
I'll continue and upload it to unstable and close this bug.

Bug#936091: marked as done (aff4: please package new upstream release (needed by rekall), port to python3)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 09:00:11 +
with message-id 
and subject line Bug#936091: fixed in pyaff4 0.27-1
has caused the Debian Bug report #936091,
regarding aff4: please package new upstream release (needed by rekall), port to 
python3
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.)


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

Hello,
please package the new upstream release for aff4; according to
https://github.com/google/aff4 the project has been split in the Python and C
parts separately.

aff4 (specificly `'pyaff4 >= 0.26, < 0.30'`) is required by the new upstream
release of rekall.  Additionally, since we're trying to port rekall to python 3,
aff4 will need to provide python 3 bindings too.  Since rekall is the only
reverse-dependency of pyhton-aff4, you can as well drop the python2 bindings at
the same time, since we're trying to remove python 2 from bullseye,
https://wiki.debian.org/Python/2Removal .

The severity is set to serious because rekall requires this package to be
packaged, and it's already RC-buggy.

Regards,
Sandro

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: pyaff4
Source-Version: 0.27-1

We believe that the bug you reported is fixed in the latest version of
pyaff4, 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.
Sophie Brun  (supplier of updated pyaff4 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, 12 Sep 2019 14:33:15 +0200
Source: pyaff4
Binary: python3-pyaff4
Architecture: source all
Version: 0.27-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Sophie Brun 
Description:
 python3-pyaff4 - Python implementation of the AFF4 standard
Closes: 936091
Changes:
 pyaff4 (0.27-1) unstable; urgency=medium
 .
   * Initial release (Closes: #936091)
   * This package needs pybindgen and fastchunking also in NEW currently.
   * It is required to update rekall to a version supporting Python 3.
Checksums-Sha1:
 4fc9bfba0a80e72f1785d40622d4bd244d6d33c1 1879 pyaff4_0.27-1.dsc
 e74b915b71ae8ac7b9bfd180cedf98e8468044db 48703317 pyaff4_0.27.orig.tar.gz
 26fe464bad1cc3c105c1f7dde3a8b0692aacc030 3544 pyaff4_0.27-1.debian.tar.xz
 5f899ac40da57009dab9dc342f4d422d29c01ec5 6523 pyaff4_0.27-1_amd64.buildinfo
 b6b7e78df816ad052fb098a12cf48087e1ae7a25 58900 python3-pyaff4_0.27-1_all.deb
Checksums-Sha256:
 b498a433573b1450a3c186e54349dd0d8dedb51a6b756d2b3e41537529a12997 1879 
pyaff4_0.27-1.dsc
 35695f6e6101e57963406a37906663c6f3196bfe352d81b0f682297b3f16c7fb 48703317 
pyaff4_0.27.orig.tar.gz
 330a9292fdd5065c4a960b9dc8604516639efc8c8900f946ef9ef4b52bbfd37e 3544 
pyaff4_0.27-1.debian.tar.xz
 168f0dda9d76e46d47c3d12d9a48f04d42892b97573a66e79b21e9a72561a865 6523 
pyaff4_0.27-1_amd64.buildinfo
 3207214667598214aa49c6c63fa1482259167681c74c5b3d08e43170fa419d38 58900 
python3-pyaff4_0.27-1_all.deb
Files:
 64b75a54340b04d454b7a5f08064b785 1879 python optional pyaff4_0.27-1.dsc
 890ddd4f5c9be4a25b9a0f8717710712 48703317 python optional 
pyaff4_0.27.orig.tar.gz
 2096ac2dd67a8223061b3af1b7412d2e 3544 python optional 
pyaff4_0.27-1.debian.tar.xz
 0fac6a717bf0715e1714f37b31b70693 6523 python optional 
pyaff4_0.27-1_amd64.buildinfo
 83a418ae8eaa0b73def7897d870d9e2d 58900 python optional 
python3-pyaff4_0.27-1_all.deb

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAl2E6IQACgkQA4gdq+vC

Processed: tagging 931214, tagging 918446, tagging 934823, tagging 936590, tagging 936871, tagging 937704 ...

[Debian Bug Tracking System]

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

> tags 931214 + experimental
Bug #931214 {Done: Thomas Goirand } [python-os-collect-config] 
ImportError: No module named oslo.config
Added tag(s) experimental.
> tags 918446 + experimental
Bug #918446 {Done: Simon McVittie } [src:policykit-1] 
policykit-1: unsatisfiable dependency on consolekit on non-linux
Bug #927896 {Done: Simon McVittie } [src:policykit-1] 
policykit-1: Please drop consolekit dependency on !linux
Added tag(s) experimental.
Added tag(s) experimental.
> tags 934823 + experimental
Bug #934823 {Done: Aurelien Jarno } [src:glibc] glibc needs 
an update for linux-5.2 kernel headers (alpha)
Added tag(s) experimental.
> tags 936590 + experimental
Bug #936590 {Done: Bas Couwenberg } [src:gdal] gdal: 
Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 936871 + experimental
Bug #936871 {Done: Nicolas Boulenguez } [src:libgtkada] 
libgtkada: Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 937704 + experimental
Bug #937704 {Done: Sandro Tosi } [src:python-django] 
python-django: Python2 removal in sid/bullseye
Added tag(s) experimental.
> found 937704 1:1.11.23-1
Bug #937704 {Done: Sandro Tosi } [src:python-django] 
python-django: Python2 removal in sid/bullseye
The source 'python-django' and version '1:1.11.23-1' do not appear to match any 
binary packages
Marked as found in versions python-django/1:1.11.23-1.
> notfound 937704 2:2.2.4-1
Bug #937704 {Done: Sandro Tosi } [src:python-django] 
python-django: Python2 removal in sid/bullseye
No longer marked as found in versions python-django/2:2.2.4-1.
> tags 937747 + experimental
Bug #937747 {Done: Sandro Tosi } [src:python-fasteners] 
python-fasteners: Python2 removal in sid/bullseye
Added tag(s) experimental.
> notfound 937747 0.12.0-5
Bug #937747 {Done: Sandro Tosi } [src:python-fasteners] 
python-fasteners: Python2 removal in sid/bullseye
No longer marked as found in versions python-fasteners/0.12.0-5.
> found 937747 0.12.0-3
Bug #937747 {Done: Sandro Tosi } [src:python-fasteners] 
python-fasteners: Python2 removal in sid/bullseye
Marked as found in versions python-fasteners/0.12.0-3.
> tags 937957 + experimental
Bug #937957 {Done: Sandro Tosi } [src:python-novaclient] 
python-novaclient: Python2 removal in sid/bullseye
Added tag(s) experimental.
> notfound 937957 2:13.0.0-2
Bug #937957 {Done: Sandro Tosi } [src:python-novaclient] 
python-novaclient: Python2 removal in sid/bullseye
No longer marked as found in versions python-novaclient/2:13.0.0-2.
> found 937957 2:11.0.0-2
Bug #937957 {Done: Sandro Tosi } [src:python-novaclient] 
python-novaclient: Python2 removal in sid/bullseye
Marked as found in versions python-novaclient/2:11.0.0-2.
> tags 937980 + experimental
Bug #937980 {Done: Sandro Tosi } [src:python-oslo.context] 
python-oslo.context: Python2 removal in sid/bullseye
Added tag(s) experimental.
> notfound 937980 2.22.1-2
Bug #937980 {Done: Sandro Tosi } [src:python-oslo.context] 
python-oslo.context: Python2 removal in sid/bullseye
No longer marked as found in versions python-oslo.context/2.22.1-2.
> found 937980 2.21.0-2
Bug #937980 {Done: Sandro Tosi } [src:python-oslo.context] 
python-oslo.context: Python2 removal in sid/bullseye
Marked as found in versions python-oslo.context/2.21.0-2.
> tags 937693 + experimental
Bug #937693 {Done: Sandro Tosi } [src:python-debtcollector] 
python-debtcollector: Python2 removal in sid/bullseye
Added tag(s) experimental.
> notfound 937693 1.21.0-2
Bug #937693 {Done: Sandro Tosi } [src:python-debtcollector] 
python-debtcollector: Python2 removal in sid/bullseye
No longer marked as found in versions python-debtcollector/1.21.0-2.
> found 937693 1.20.0-2
Bug #937693 {Done: Sandro Tosi } [src:python-debtcollector] 
python-debtcollector: Python2 removal in sid/bullseye
Marked as found in versions python-debtcollector/1.20.0-2.
> tags 937991 + experimental
Bug #937991 {Done: Sandro Tosi } 
[src:python-os-service-types] python-os-service-types: Python2 removal in 
sid/bullseye
Added tag(s) experimental.
> notfound 937991 1.6.0-2
Bug #937991 {Done: Sandro Tosi } 
[src:python-os-service-types] python-os-service-types: Python2 removal in 
sid/bullseye
No longer marked as found in versions python-os-service-types/1.6.0-2.
> found 937991 1.3.0-2
Bug #937991 {Done: Sandro Tosi } 
[src:python-os-service-types] python-os-service-types: Python2 removal in 
sid/bullseye
Marked as found in versions python-os-service-types/1.3.0-2.
> tags 938201 + experimental
Bug #938201 {Done: Sandro Tosi } [src:python-stestr] 
python-stestr: Python2 removal in sid/bullseye
Added tag(s) experimental.
> notfound 938201 2.3.1-2
Bug #938201 {Done: Sandro Tosi } [src:python-stestr] 
python-stestr: Python2 removal in sid/bullseye
No longer marked as found in versions python-stestr/2.3.1-2.
> found 938201 2.1.0-2
Bug #938201 {Done: Sandro Tosi } [src:python-stestr] 
python-stestr: Python2 removal in sid/bullseye
Marked as found in versions 

Bug#935964: marked as done (django-setuptest: Remove wrong test for python2 support)

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2019 08:37:25 +
with message-id 
and subject line Bug#935964: fixed in django-setuptest 0.2.1-4
has caused the Debian Bug report #935964,
regarding django-setuptest: Remove wrong test for python2 support
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.)


-- 
935964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: django-setuptest
Version: 0.2.1-3
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

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

  * Remove invalid test for python 2 support

The python 2 support was removed in the previous upload, so testing it now
fails because the package cannot be found anymore.

Thanks for considering the patch.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
diff -Nru django-setuptest-0.2.1/debian/tests/control 
django-setuptest-0.2.1/debian/tests/control
--- django-setuptest-0.2.1/debian/tests/control 2019-07-26 14:53:37.0 
+0200
+++ django-setuptest-0.2.1/debian/tests/control 2019-08-28 14:48:24.0 
+0200
@@ -1,7 +1,3 @@
-Test-Command: cd "$AUTOPKGTEST_TMP" ; python -c "import setuptest; print 
setuptest"
-Depends:
- python-django-setuptest,
-
 Test-Command: cd "$AUTOPKGTEST_TMP" ; python3 -c "import setuptest; 
print(setuptest)"
 Depends:
  python3-django-setuptest,
--- End Message ---
--- Begin Message ---
Source: django-setuptest
Source-Version: 0.2.1-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Oct 2019 03:54:27 -0400
Source: django-setuptest
Architecture: source
Version: 0.2.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Closes: 935964
Changes:
 django-setuptest (0.2.1-4) unstable; urgency=medium
 .
   * Team upload.
   * Also remove autopkgtest for python2 (Closes: #935964)
   * Bump standards-version to 4.4.1 without further change
Checksums-Sha1:
 fdaf448860b11b638ef6633325902f29b7341fb4 2117 django-setuptest_0.2.1-4.dsc
 11e22a181aef62e9b493d9801ac6d857b58b4880 2944 
django-setuptest_0.2.1-4.debian.tar.xz
 83eca959c8f7de50af5a6ce7c397583df4b37a1d 6010 
django-setuptest_0.2.1-4_source.buildinfo
Checksums-Sha256:
 01a7cf1deaaa0294e1f32f661a895c169a1141bd6dbf3a1060330f7872ed43ef 2117 
django-setuptest_0.2.1-4.dsc
 8069322cd9b848c2ccff1081cb3fc9ca075e3a80f591c4dc08861612fc692145 2944 
django-setuptest_0.2.1-4.debian.tar.xz
 c6dde3487bd79e61b99a7e94e6e368872f654058ea4a7ec83b41e7bf9592d68f 6010 
django-setuptest_0.2.1-4_source.buildinfo
Files:
 05236bbfab588515e9e8a65f7f4a4240 2117 python optional 
django-setuptest_0.2.1-4.dsc
 70653720eceeb63f1e9c6b74fdc70167 2944 python optional 
django-setuptest_0.2.1-4.debian.tar.xz
 1634cedd9f0a2692068dc964163d9797 6010 python optional 
django-setuptest_0.2.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl2le3gACgkQeNfe+5rV
mvEvIhAAyjOnyOBaJkvOqKXrYcze+Z3EUH0h+lPDQImSbxK49bxwsFtoFEGZxKRF
11PjvVlarIJo2+175FgH9qTQadUdNEPhLK1xoup4xs6kFHIRITZuZ42LR4kZS6p1
LyaxGMTWzY5QHnQakrqeZfe1flsMqkHoW7qR5LGDLfdNIIjqOGwE4HCy8c7H1sJ7
iceXMaSxdmTHKIb1xLXRyC4xY5/fcdkBCF/gve5TtX6cbcQ7XRXqEy+ULrM+VQfT
7eAzZo2LL2L3rdSI3tzzuM57+X2KBlGHysShD+r5qyXM1AqQYNd4valqGC2NXiTH
J83CrAfIX/AXiySVG26Eicgm48ytsMkBvOBiEie6rcthqIj+kCcxyufuKHjvfHYj
AtIzFMeOLcI+O7tc5vAPurJgp4hUTgxMatwNRtiBbIYoCfGOEy/U21sVrnds6jF3
7/nClwK4PFbse/hHaXJjUP3nONGIQb9FbrNWWguOHRj8/QD48me4g/k98aeJvrSh
XveH+ryOAuPF4gjnQWLBxi5j8Fp7Sjp7fc/ZJa/dwQlWTu8Wfo36RtjrMo/K42Ua
F0/u1eU+JetaSEYlzKvxDCNEHYy1rp6x16LRgWYgttm2AG8tt4IklI1swXd9uWdf
NsgBRZ3Et8LYpZEGGbAzMuVgjMDfxyEqI5x+ZBssNgKTOFhnneQ=
=I7sr
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#942073: marisa: perl bindings are broken when linked with gcc-9

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #942073 [libmarisa-perl] marisa: perl bindings are broken when linked with 
gcc-9
Added tag(s) patch.

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

Bug#942073: marisa: perl bindings are broken when linked with gcc-9

[Niko Tyni]

Control: tag -1 patch

On Wed, Oct 09, 2019 at 11:45:39PM +0300, Niko Tyni wrote:
> Package: libmarisa-perl
> Version: 0.2.5-3
> Severity: grave
> Control: block 935737 with -1
> 
> As noticed by the autopkgtest checks, the marisa Perl bindings are
> totally broken in sid after the recent Perl 5.30 rebuild:

> It looks like this regressed with the gcc 8 -> 9 move. Linking the
> DSO manually with gcc-8 makes it go away, as seen below.
> 
> I have no idea what goes wrong here, but I noticed that broken versions
> of blib/arch/auto/marisa/marisa.so have no NEEDED entry for libmarisa.so.0
> (as seen with 'objdump -p').

There seem to be several conflated issues here:

- debian/rules overrids LIBS to '-L../../lib/marisa/.libs' but doesn't
  include '-lmarisa'

- debian/rules setting of LDDLFLAGS used to mask this by including
  '-L../../lib/marisa/.libs -lmarisa', but this ends up too early in
  the linking command, so gcc-9 ignores it for the objects later in
  the command

- the LDDFLAGS part of this would not be needed and ExtUtils::MakeMaker
  would do the right thing if the marisa library was already built when
  Makefile.PL was run

Proposed patch attached.
-- 
Niko Tyni   nt...@debian.org
>From f715c42ea44727eee6e7971bcc5270c409f01321 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Tue, 15 Oct 2019 08:36:22 +0100
Subject: [PATCH] Fix debian/rules for perl bindings

We need to run Makefile.PL only after the library is built.

Closes: 942073
---
 debian/rules | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/debian/rules b/debian/rules
index 4e2b6cf..01f9db9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -33,18 +33,18 @@ override_dh_auto_configure:
 	dh_auto_configure
 	make -C bindings
 	cd bindings/python; sed -i "s/__version__/$(DEB_VERSION_UPSTREAM)/" setup.py
+
+override_dh_auto_build:
+	dh_auto_build
 	cd bindings/perl; perl Makefile.PL \
 	INSTALL_BASE=$(CURDIR)/debian/libmarisa-perl/usr \
 	INSTALLARCHLIB=$(CURDIR)/debian/libmarisa-perl$(PERL_VENDOR_ARCH) \
 	INSTALLSITEARCH=$(CURDIR)/debian/libmarisa-perl$(PERL_VENDOR_ARCH) \
 	INSTALLVENDORARCH=$(CURDIR)/debian/libmarisa-perl$(PERL_VENDOR_ARCH) \
 	INC="-I../../include" \
-	LIBS="-L../../lib/marisa/.libs" \
+	LIBS="-L../../lib/marisa/.libs -lmarisa" \
 	CCFLAGS="$(shell dpkg-buildflags --get CFLAGS) $(shell dpkg-buildflags --get CPPFLAGS)" \
-	LDDLFLAGS="-shared -L/usr/local/lib -L../../lib/marisa/.libs -lmarisa -fstack-protector $(shell dpkg-buildflags --get LDFLAGS)"
-
-override_dh_auto_build:
-	dh_auto_build
+	LDDLFLAGS="-shared -L/usr/local/lib -fstack-protector $(shell dpkg-buildflags --get LDFLAGS)"
 	# Build for each Python 3 version
 	cd bindings/python; \
 	set -ex; for python in $(PYTHON3); do \
-- 
2.23.0.rc1

Bug#942284: [Pkg-net-snmp-devel] Bug#942284: libsnmp-perl: perl module SNMP broken

[Niko Tyni]

On Mon, Oct 14, 2019 at 09:07:36PM +0200, gregor herrmann wrote:
> On Mon, 14 Oct 2019 10:34:41 +1100, Craig Small wrote:
> 
> > > libsnmp-perl is broken.
> > Ouch, I don't use the module (or Perl much for that matter) but that's very
> > broken. No idea what's going on but it worries me that
> > netsnmp_ds_get_boolean is the first function in that module which means a
> > coincidence or all functions are not available.

> So it looks like the "whole" problem is that net-snmp is not
> parallel-build safe …

Indeed. I think what happens is that if the Perl extensions get
configured (as in 'perl Makefile.PL') before the main libraries are built,
ExtUtils::MakeMaker will drop -lnetsnmp from the linking phase because
that library doesn't exist (yet). This is indicated by the

  Warning (mostly harmless): No library found for -lnetsnmp

messages in the build log.

We already fixed this once with debian/patches/perl-parallel-build.patch
in #894626, but that patch needs to be updated to reflect upstream
Makefile.in changes.

Moving the 'standardall' dependency to to 'perl/Makefile' target seems
to do the trick. Below is the updated version of the patch.

Apparently upstream is struggling with this issue too,
given the related messages in the changelog that Gregor
mentioned (commits 347d4cf207b834744fc9215f7e4423530c67653f and
fb763ef6f390ac8dec4d7c0c0160f648464d587d). Craig: you might want to
bring this up upstream and/or stop building in parallel if upstream is
against it.

Also, given this is the second time broken packages enter the archive
due to this issue, please consider adding at least some kind of sanity
check to the build.


diff --git a/Makefile.in b/Makefile.in
index 60b8d76d9..670646cf8 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -180,7 +180,7 @@ perlmodules: perlmakefiles subdirs
 
 perlmakefiles: perl/Makefile net-snmp-config-x
 
-perl/Makefile: perl/Makefile.PL
+perl/Makefile: perl/Makefile.PL standardall
dir=`pwd` &&\
cd perl &&  \
if false; then  \


-- 
Niko Tyni   nt...@debian.org

Bug#935964: marked as pending in django-setuptest

[Scott Kitterman]

Control: tag -1 pending

Hello,

Bug #935964 in django-setuptest 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/python-team/modules/django-setuptest/commit/407338fd95e687a6994a806535f29c80f6b56360


* Also remove autopkgtest for python2 (Closes: #935964)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935964

Processed: tagging 942350, found 942352 in 1.0.9-2, tagging 942352, tagging 942339, tagging 942331

[Debian Bug Tracking System]

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

> tags 942350 + sid bullseye
Bug #942350 [repmgr] repmgr: autopkgtest fails with postgresql 12 libraries
Added tag(s) bullseye and sid.
> found 942352 1.0.9-2
Bug #942352 [python3-scales] python3-scales: wrong package name
Marked as found in versions python-scales/1.0.9-2.
> tags 942352 + sid bullseye
Bug #942352 [python3-scales] python3-scales: wrong package name
Added tag(s) bullseye and sid.
> tags 942339 + sid bullseye
Bug #942339 [src:peony-extensions] peony-extensions: FTBFS - local unused 
g_ptr_array_copy definition collides with glib
Added tag(s) bullseye and sid.
> tags 942331 + sid bullseye
Bug #942331 [src:google-cloud-print-connector] google-cloud-print-connector: 
FTBFS during rebuild with libsnmp35
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: Bug#935964 marked as pending in django-setuptest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #935964 [django-setuptest] django-setuptest: Remove wrong test for python2 
support
Added tag(s) pending.

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

Bug#934905: libaqbanking35: libaqbanking not ready for PSD2, will not work after 14 September 2019

[Joachim Breitner]

Hi,


On Fri, 4 Oct 2019 22:46:14 +0200 Micha Lenk  wrote:
> But before we get there, I need to update the packages. The current 
> state is always available in Git on 
> https://salsa.debian.org/aqbanking-team in the respective experimental 
> branch.
> 
> As soon as I have the packaging fixed locally, I will make an APT 
> repository available with all the packages I created so far. So, this 
> isn't blocked by ftp-master, but I need to find the time to work on it.

I am checking that space regularly, and am very much looking forward to
these packages :-)

Cheers,
Joachim
 
-- 
Joachim “nomeata” Breitner • nome...@debian.org • https://j.oach.im/
  


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

Bug#830726: closed by Chris Lamb (Bug#830726: fixed in xtrlock 2.12)

[Antoine Amarilli]

Looks great! There's a grammar problem "This fix does not the situation"
but it doesn't matter.

Best,

-- 
Antoine Amarilli


On Mon, Oct 14, 2019 at 07:13:05PM -, Chris Lamb wrote:
> Hi Antoine,
> 
> ?
> > I see nothing, unless you mean the source code comment?
> 
> Yes, the source code comment. I've expanded the (released) changelog
> entry here:
> 
>   
> https://salsa.debian.org/debian/xtrlock/commit/34e6c7c6c33ce6b7510172a2e05e710a99fdc146
> 
> … so this visibility will be in subsequent releases at the very least.
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org  chris-lamb.co.uk
>`-


signature.asc
Description: PGP signature

Bug#938550: spyder: Python2 removal in sid/bullseye

[Drew Parsons]

On 2019-10-15 13:57, PICCA Frederic-Emmanuel wrote:

I didn't notice it, so wasn't planning to add it.  spyder_kernels
imports without complaining, and spyder seems to start fine anyway.
Where does it come to notice?


I do not know, but on wndows it is optional.
So maybe this is not a big issue.



Perhaps it makes things work more smoothly with jupyter.  I don't use 
jupyter myself as such.


Drew

Bug#938550: spyder: Python2 removal in sid/bullseye

[PICCA Frederic-Emmanuel]

> I didn't notice it, so wasn't planning to add it.  spyder_kernels
> imports without complaining, and spyder seems to start fine anyway.
> Where does it come to notice?

I do not know, but on wndows it is optional.
So maybe this is not a big issue.


Fred