Bug#943608: tests segfault when run with Python 3.8

[Matthias Klose]

confirmed in unstable as well:
https://buildd.debian.org/status/fetch.php?pkg=beancount=amd64=2.2.3-1%2Bb1=1574207855=0

Bug#945096: metview: FTBFS in sid

[Gianfranco Costamagna]

This diff made it build successfully

diff -Nru metview-5.7.0/debian/control metview-5.7.0/debian/control
--- metview-5.7.0/debian/control2019-10-08 10:31:19.0 +0200
+++ metview-5.7.0/debian/control2019-11-19 22:56:58.0 +0100
@@ -14,6 +14,10 @@
   liblapack-dev,
   libpango1.0-dev,
   libfftw3-dev,
+  libxxhash-dev,
+  libsnappy-dev,
+  liblz4-dev,
+  libbz2-dev,
   libeigen3-dev,
   chrpath,
   mksh,
@@ -96,7 +100,7 @@
 Package: libmetview-dev
 Architecture: any
 Multi-Arch: same
-Depends: ${misc:Depends}, libmetview0d (=${binary:Version}), libodb-api-dev
+Depends: ${misc:Depends}, libmetview0d (=${binary:Version}), libodb-api-dev, 
libxxhash-dev, libsnappy-dev, liblz4-dev, libbz2-dev
 Section: libdevel
 Description: Development files for MetView
  Metview has been designed as a flexible, modular and extendible system

Bug#939193: marked as done (Incompatible to new symfony 4.x)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 02:57:04 +
with message-id 
and subject line Bug#939193: fixed in ratchetphp 0.4.1-3
has caused the Debian Bug report #939193,
regarding Incompatible to new symfony 4.x
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.)


-- 
939193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-nesbot-carbon
Version: 1.27.0-1
Severity: serious
Tags: sid

Hi,
I was debugging issues in Ubuntu with dependencies of symfony that are
broken with symfony 4.x
Those are essentially unusable/uninstallable.

Initially reported to Ubuntu in [1] but applying to both Distributions
just as much. The bug [1] contains a much more detailed overview of
the cross-relations and the most likely options to resolve. Please
take look there avoiding to re-post the same (huge) text over and over
again.

Reporting in Debian against the direct dependencies to symfony so that
you are aware (thanks Steve for the reminder to do so). Overall that
means movim, ratchetphp, php-nesbot-carbon, php-robmorgan-phinx

Here the snippet for this package from there copy:

3. php-nesbot-carbon
- Debian/Ubuntu 1.27.0-1
- Upstream 2.23.1

Symfony support is in actually since 1.23.0
=> 
https://github.com/briannesbitt/Carbon/commit/23d299fdc24e8e7ff7f239846a9f8398ffb5a263
And it should be in 1.27 that we have:
$ git show 1.27.0:composer.json | grep symfony
"symfony/translation": "~2.6 || ~3.0 || ~4.0"
Note: 1.26 would have been a stable release with much more updates

What is in the Archive clearly isn't 1.27
=> https://github.com/briannesbitt/Carbon/archive/1.27.0.zip
$ grep symfony composer.json
"symfony/translation": "~2.6 || ~3.0 || ~4.0"

There never was an upstream tarball for 1.27 (d/watch finds nothing,
only a zip file).
And the used content of the tarball never really existed, upstream went
"symfony/translation": "~2.6"
"symfony/translation": "~2.6|~3.0"
"symfony/translation": "~2.6 || ~3.0 || ~4.0"
"symfony/translation": "^4.0"
"symfony/translation": "^3.4 || ^4.0"

Solution:
a) replace with real upstream source of 1.27, maybe something much newer.
b) removal along movim


[1]: https://bugs.launchpad.net/ubuntu/+bug/1842019

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: ratchetphp
Source-Version: 0.4.1-3

We believe that the bug you reported is fixed in the latest version of
ratchetphp, 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.
Thorsten Glaser  (supplier of updated ratchetphp 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: SHA384

Format: 1.8
Date: Wed, 20 Nov 2019 00:58:01 +0100
Source: ratchetphp
Architecture: source
Version: 0.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force 
Changed-By: Thorsten Glaser 
Closes: 939193
Changes:
 ratchetphp (0.4.1-3) unstable; urgency=medium
 .
   * debian/patches/fix_deps.patch:
 switch over to requiring symfony 4.x (Closes: #939193), cf. #765899
   * modernise packaging
   * add UMEGAYA metadata, update lintian overrides
Checksums-Sha1:
 ac576371840f4700a1a9fba2fd944812032a6c51 2030 ratchetphp_0.4.1-3.dsc
 56401837ea392fcbb440a0f9b795cf46cc9cd545 3044 ratchetphp_0.4.1-3.debian.tar.xz
Checksums-Sha256:
 318b7bedf46ddc439111c9a73fbf7dfe12c1a6b3006b009c886f6a74c15e3ae0 2030 
ratchetphp_0.4.1-3.dsc
 5de07aaee1c218ba259b1b3a56ab0f3e7e1e84f4fb6bb52e85a0c61aea6fe1b3 3044 
ratchetphp_0.4.1-3.debian.tar.xz
Files:
 7ef01283a3602cb352fd2355a4cb8fa2 2030 php optional ratchetphp_0.4.1-3.dsc
 008a107d239c07162b4167d369985587 3044 php optional 
ratchetphp_0.4.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８　☕☂☄

iQIcBAEBCQAGBQJd1JuxAAoJEHa1NLLpkAfgp2MQAMXd/CVnKF/XZ2mTdUSqeyKA
IYdYGwlhhdO/NmwhAc5VU1AR/GH5CvwhG2S4iTOvWbgcwqdpfEqn8XGFlw7pFcWa
9DjmCDRIUWkeU+tyg3I87F+RXBoniyTlZ3IFI85rNJX6N9DWix5BKUQDtcj0aF9B
3a3wJ7jy9UqVncKiKjpTqfjxlWh6mPbe+/ZqiarTzVfvxUcZTzHXIlGsEsm+Pzl0

Bug#939193: marked as done (Incompatible to new symfony 4.x)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 02:55:42 +
with message-id 
and subject line Bug#939193: fixed in php-nesbot-carbon 1.27.0-2
has caused the Debian Bug report #939193,
regarding Incompatible to new symfony 4.x
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.)


-- 
939193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-nesbot-carbon
Version: 1.27.0-1
Severity: serious
Tags: sid

Hi,
I was debugging issues in Ubuntu with dependencies of symfony that are
broken with symfony 4.x
Those are essentially unusable/uninstallable.

Initially reported to Ubuntu in [1] but applying to both Distributions
just as much. The bug [1] contains a much more detailed overview of
the cross-relations and the most likely options to resolve. Please
take look there avoiding to re-post the same (huge) text over and over
again.

Reporting in Debian against the direct dependencies to symfony so that
you are aware (thanks Steve for the reminder to do so). Overall that
means movim, ratchetphp, php-nesbot-carbon, php-robmorgan-phinx

Here the snippet for this package from there copy:

3. php-nesbot-carbon
- Debian/Ubuntu 1.27.0-1
- Upstream 2.23.1

Symfony support is in actually since 1.23.0
=> 
https://github.com/briannesbitt/Carbon/commit/23d299fdc24e8e7ff7f239846a9f8398ffb5a263
And it should be in 1.27 that we have:
$ git show 1.27.0:composer.json | grep symfony
"symfony/translation": "~2.6 || ~3.0 || ~4.0"
Note: 1.26 would have been a stable release with much more updates

What is in the Archive clearly isn't 1.27
=> https://github.com/briannesbitt/Carbon/archive/1.27.0.zip
$ grep symfony composer.json
"symfony/translation": "~2.6 || ~3.0 || ~4.0"

There never was an upstream tarball for 1.27 (d/watch finds nothing,
only a zip file).
And the used content of the tarball never really existed, upstream went
"symfony/translation": "~2.6"
"symfony/translation": "~2.6|~3.0"
"symfony/translation": "~2.6 || ~3.0 || ~4.0"
"symfony/translation": "^4.0"
"symfony/translation": "^3.4 || ^4.0"

Solution:
a) replace with real upstream source of 1.27, maybe something much newer.
b) removal along movim


[1]: https://bugs.launchpad.net/ubuntu/+bug/1842019

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: php-nesbot-carbon
Source-Version: 1.27.0-2

We believe that the bug you reported is fixed in the latest version of
php-nesbot-carbon, 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.
Thorsten Glaser  (supplier of updated php-nesbot-carbon 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: SHA384

Format: 1.8
Date: Wed, 20 Nov 2019 00:39:56 +0100
Source: php-nesbot-carbon
Architecture: source
Version: 1.27.0-2
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force 
Changed-By: Thorsten Glaser 
Closes: 939193
Changes:
 php-nesbot-carbon (1.27.0-2) unstable; urgency=medium
 .
   * debian/patches/pkg-php-tools-deficiency-workaround.diff:
 switch over to requiring symfony 4.x (Closes: #939193), cf. #765899
   * modernise packaging
Checksums-Sha1:
 de2eef13923a80f3b14e19d6d2d3f023beb1 2073 php-nesbot-carbon_1.27.0-2.dsc
 66592acd87ed546a94ee0a00eb6a64ba2e5cb705 2528 
php-nesbot-carbon_1.27.0-2.debian.tar.xz
Checksums-Sha256:
 47bf12277612ca1753bf0c0c51e3c15c86afe3a3bb080e048455fc3ab0174cab 2073 
php-nesbot-carbon_1.27.0-2.dsc
 0831b51a4073dd2d943c37e38958b9974ddbcad317650d09cb6aceffa2508457 2528 
php-nesbot-carbon_1.27.0-2.debian.tar.xz
Files:
 e8e740ce4a9357b61b5952bad2ed6a89 2073 php optional 
php-nesbot-carbon_1.27.0-2.dsc
 62de09ce963b45b7bb731226f0a51a4e 2528 php optional 
php-nesbot-carbon_1.27.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８　☕☂☄

iQIcBAEBCQAGBQJd1JufAAoJEHa1NLLpkAfgii4P/2xXsjqtSEGnC0yqMH/Vgld0
9MMdOKfVukyGz5JC6RmxePEV4mlqD7a6wDQTS/nJX/vGl7Dv+xsf2mjN0Acev2GY
O3DapbnwEuG7o2KojibshP6NP9ceWwHL7nnBX5vRjyaBMCDTKrFeQ1T48+Fu3NeB

Bug#939190: marked as done (Incompatible to new symfony 4.x)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 02:52:23 +
with message-id 
and subject line Bug#939190: fixed in movim 0.14.1-6
has caused the Debian Bug report #939190,
regarding Incompatible to new symfony 4.x
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.)


-- 
939190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: movim
Version: 0.14.1-5
Severity: serious
Tags: sid

Hi,
I was debugging issues in Ubuntu with dependencies of symfony that are
broken with symfony 4.x
Those are essentially unusable/uninstallable.

Initially reported to Ubuntu in [1] but applying to both Distributions
just as much. The bug [1] contains a much more detailed overview of
the cross-relations and the most likely options to resolve. Please
take look there avoiding to re-post the same (huge) text over and over
again.

Reporting in Debian against the direct dependencies to symfony so that
you are aware (thanks Steve for the reminder to do so). Overall that
means movim, ratchetphp, php-nesbot-carbon, php-robmorgan-phinx

Here the snippet for this package from there copy:

1. movim
- Debian/Ubuntu 0.14.1-5
- Upstream v0.15 (July 28)
- Symfony dependency fixes:
  => 
https://github.com/movim/movim/commit/a80bba27fa2983afd702fabcb91a3f11e85df58d
  => 
https://github.com/movim/movim/commit/98e4825ad20296af531106bb1d5697408924d5a6

The latter already is part of 0.14.1 but not in the tarball used by Debian.
It seems "their build" used the new components already in 0.14.1 (=>
composer.lock)
But the composer.json wasn't updated yet hence it is outdated and things like
  debian/control:30: ${phpcomposer:Debian-require},
pull in the too old dependencies.

Note: it seems no actual changes were needed, but just patching
composer.json still seems to dangerous.
Solution:
a) update to 0.15 (FFE)
b) remove from Eoan
Removal would already make all other non-needed as well
c) update composer.json to accept v4
(might be ok - as it seems upstream 0.14.1 was built with symfony 4)
Rebuild then will pick up versions through ${phpcomposer:Debian-require}


[1]: https://bugs.launchpad.net/ubuntu/+bug/1842019

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: movim
Source-Version: 0.14.1-6

We believe that the bug you reported is fixed in the latest version of
movim, 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.
Thorsten Glaser  (supplier of updated movim 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: SHA384

Format: 1.8
Date: Wed, 20 Nov 2019 02:03:04 +0100
Source: movim
Architecture: source
Version: 0.14.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian XMPP Maintainers 
Changed-By: Thorsten Glaser 
Closes: 939190
Changes:
 movim (0.14.1-6) unstable; urgency=medium
 .
   * Team upload.
   * Update composer.json to allow symfony 4.x (Closes: #939190)
   * Modernise packaging (bump debhelper and Policy versions)
Checksums-Sha1:
 f5322b491080072121d6bca0fbaf725dcabf5505 1972 movim_0.14.1-6.dsc
 5111c7484879633c6fe91f9fac8550f1d066b86f 25512 movim_0.14.1-6.debian.tar.xz
Checksums-Sha256:
 38c809dd6ad61c9a3037b5c187262a5c859d338b7f092118d0a82ca5340ffc09 1972 
movim_0.14.1-6.dsc
 2ef1388465395716ef2ea36d02066539774e8848b99fd4b9b3ca51a151e07978 25512 
movim_0.14.1-6.debian.tar.xz
Files:
 a39c2853de4267a2f4258c73bb31c439 1972 php optional movim_0.14.1-6.dsc
 ca70850fa3299554dcb9da6d411e4137 25512 php optional 
movim_0.14.1-6.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８　☕☂☄

iQIcBAEBCQAGBQJd1Js7AAoJEHa1NLLpkAfgNm4QALr9MEH4Drbbj5ARSQWiRfOJ
Wf09+BXM7NdJ17kZPqWZ3oV31o2SklUaCwVuQtlUM/K+x9jRWGNLmjPW0j6w6L4w
VqGUgOnDGOue2HmFDWuGEmYkwmUsnNMwBgo7MjaSH+URv7T7gldc+KQtTg5VJ47d
Mst5p9fYSA5kuG1jkajFKwlaRqGQaNkrYtN7cCIR/9QBaboOMQaRFytizMFsVQv1
DYAmKMakG6l7nl37ihZCI3tGaftuNYt0cnlIHdIWDtwhIoNyyJEGqITZEYbIde7y
UYoUB91gw9lMTkYUR9mILUpI2pZaVo8PSICI5AQnzdsheJp9AIEfiLtudC/yJbcw
2GTeQBjpFHv231kjyUVvZZvvFdWZvUW62jecsm6ObftISJTPHUqgweQjT3tOjX0J

Bug#939191: marked as done (Incompatible to new symfony 4.x)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 02:55:50 +
with message-id 
and subject line Bug#939191: fixed in php-robmorgan-phinx 0.9.2-2
has caused the Debian Bug report #939191,
regarding Incompatible to new symfony 4.x
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.)


-- 
939191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-robmorgan-phinx
Version: 0.9.2-1
Severity: serious
Tags: sid

Hi,
I was debugging issues in Ubuntu with dependencies of symfony that are
broken with symfony 4.x
Those are essentially unusable/uninstallable.

Initially reported to Ubuntu in [1] but applying to both Distributions
just as much. The bug [1] contains a much more detailed overview of
the cross-relations and the most likely options to resolve. Please
take look there avoiding to re-post the same (huge) text over and over
again.

Reporting in Debian against the direct dependencies to symfony so that
you are aware (thanks Steve for the reminder to do so). Overall that
means movim, ratchetphp, php-nesbot-carbon, php-robmorgan-phinx

Here the snippet for this package from there copy:

4. php-robmorgan-phinx
- Debian/Ubuntu 0.9.2-1
- Upstream 0.11.0

Symfony support exists since
=> 
https://github.com/cakephp/phinx/commit/02e1888765ecfcd2760e484e1b8fe95f938b34a2
But again:
$ git tag --contains 02e1888765ecfcd2760e484e1b8fe95f938b34a2
[...]
v0.9.2

As with ratchedphp this is reverted in Debian.
debian/patches/pkg-php-tools-deficiency-workaround.diff:10:-
"symfony/console": "^2.8|^3.0|^4.0",
debian/patches/pkg-php-tools-deficiency-workaround.diff:11:-
"symfony/config": "^2.8|^3.0|^4.0",
debian/patches/pkg-php-tools-deficiency-workaround.diff:12:-
"symfony/yaml": "^2.8|^3.0|^4.0"
debian/patches/pkg-php-tools-deficiency-workaround.diff:13:+
"symfony/console": "^3.0",
debian/patches/pkg-php-tools-deficiency-workaround.diff:14:+
"symfony/config": "^3.0",
debian/patches/pkg-php-tools-deficiency-workaround.diff:15:+
"symfony/yaml": "^3.0"

Here at least the filename gives an indication what might have
happened "pkg-php-tools-deficiency-workaround".
I'd hope that this is resolved and could be reverted+rebuilt.
Otherwise at least make it "only 4.0" instead of "only 3.0"

Solution:
a) drop the patch and rebuild - ${phpcomposer:Debian-require} will
pick new things up.
b) removal along movim

[1]: https://bugs.launchpad.net/ubuntu/+bug/1842019

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--- End Message ---
--- Begin Message ---
Source: php-robmorgan-phinx
Source-Version: 0.9.2-2

We believe that the bug you reported is fixed in the latest version of
php-robmorgan-phinx, 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.
Thorsten Glaser  (supplier of updated php-robmorgan-phinx 
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: SHA384

Format: 1.8
Date: Wed, 20 Nov 2019 00:48:29 +0100
Source: php-robmorgan-phinx
Architecture: source
Version: 0.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Teckids Debian Task Force 
Changed-By: Thorsten Glaser 
Closes: 939191
Changes:
 php-robmorgan-phinx (0.9.2-2) unstable; urgency=medium
 .
   * debian/patches/pkg-php-tools-deficiency-workaround.diff:
 switch over to requiring symfony 4.x (Closes: #939191), cf. #765899
   * modernise packaging
Checksums-Sha1:
 19067882a9c9b309cebd392cc4264532e903b169 2093 php-robmorgan-phinx_0.9.2-2.dsc
 bc134612b17fa9bbc99da8a65777cba388f1271f 4344 
php-robmorgan-phinx_0.9.2-2.debian.tar.xz
Checksums-Sha256:
 bb82436d5377355620643d6501a4daea40716ef8a28de2b8ef3da3e5582f20e6 2093 
php-robmorgan-phinx_0.9.2-2.dsc
 b9ec9ab76157190cc9858ea686f9dc87a4233dd7e78bb2b366c3577c8895ccad 4344 
php-robmorgan-phinx_0.9.2-2.debian.tar.xz
Files:
 c1fcd9c1fda518f578cb18b40dbfb1ec 2093 php optional 
php-robmorgan-phinx_0.9.2-2.dsc
 2a4a01be2ccf3bd9b8dccadcc55090c9 4344 php optional 
php-robmorgan-phinx_0.9.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８　☕☂☄

Bug#945064: marked as done (unrardll needs a sourceful upload to support python3.8?)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 10:37:59 +0900
with message-id <20191120013759.h34a62imvzemq...@bulldog.preining.info>
and subject line Re: Bug#945064: unrardll needs a sourceful upload to support 
python3.8?
has caused the Debian Bug report #945064,
regarding unrardll needs a sourceful upload to support python3.8?
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.)


-- 
945064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:unrardll
Version: 0.1.3-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

unrardll shows up in
https://release.debian.org/transitions/html/python3.8.html

but cannot be binNMUed because it's a contrib package b-d on a non-free package.
 Please do a sourceful upload to add support for Python 3.8.
--- End Message ---
--- Begin Message ---
Version: 0.1.3-4

Hi Matthias

> but cannot be binNMUed because it's a contrib package b-d on a non-free 
> package.
>  Please do a sourceful upload to add support for Python 3.8.

Checked that it builds properly with 3.7 and 3.8 support, uploaded a new
source only package, closing this bug now (forgot the changelog closing)

Thanks

Norbert

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

Bug#944935: marked as done (deltarpm: needs an explicit build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 01:34:35 +
with message-id 
and subject line Bug#944935: fixed in deltarpm 3.6+dfsg-1.1
has caused the Debian Bug report #944935,
regarding deltarpm: needs an explicit build dependency on dh-python
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.)


-- 
944935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:deltarpm
Version: 3.6+dfsg-1
Severity: serious
Tags: sid bullseye

python3-all and python3-dev now dropped the dependency on
dh-python:

[ Piotr Ożarowski ]
   * Remove dh-python dependency from python3-all and python3-dev packages.
 Packages should build depend on dh-python or dh-sequence-python3 instead.

Please add an explicit build dependency on dh-python.
--- End Message ---
--- Begin Message ---
Source: deltarpm
Source-Version: 3.6+dfsg-1.1

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated deltarpm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Nov 2019 19:59:25 -0500
Source: deltarpm
Architecture: source
Version: 3.6+dfsg-1.1
Distribution: unstable
Urgency: high
Maintainer: RPM packaging team 
Changed-By: Boyuan Yang 
Closes: 944935
Changes:
 deltarpm (3.6+dfsg-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
 .
   [ Boyuan Yang ]
   * debian/control: Add explicit build-dependency on dh-python.
 (Closes: #944935)
 .
   [ Mike Miller ]
   * Add DEP-3 headers and refresh all patches.
   * Set maintainer to RPM packaging team, add myself as uploader.
   * Update debian/copyright for 2019.
   * d/control: Update Vcs-* to salsa.debian.org.
Checksums-Sha1:
 d2698521d2c03ec411861bece598e427f3a534dd 2159 deltarpm_3.6+dfsg-1.1.dsc
 634edd9f778a346eb1154dd155a73d94c8852ed5 4408 
deltarpm_3.6+dfsg-1.1.debian.tar.xz
 ab9a0164e7ac3ffcbf36fa150c7c20732827af97 8508 
deltarpm_3.6+dfsg-1.1_amd64.buildinfo
Checksums-Sha256:
 f2b868f49746ca4cadac2b820dae6cd8f8e561ae5f20e2017e0a8dfc33e6858f 2159 
deltarpm_3.6+dfsg-1.1.dsc
 ad41a1a1c1c010d1e7550e5b071dbdd6793b23d1aafd9db16867ff51b1f560bc 4408 
deltarpm_3.6+dfsg-1.1.debian.tar.xz
 438ba1fd78b4cbc14dcf6a9dc39119bd1f6574c31b19a9e1f3eb5fe9addcc4db 8508 
deltarpm_3.6+dfsg-1.1_amd64.buildinfo
Files:
 5baa125dfb36a97cd5c3a3b3b82d2345 2159 admin extra deltarpm_3.6+dfsg-1.1.dsc
 298d86c6b47c47246bb74ed580509cb6 4408 admin extra 
deltarpm_3.6+dfsg-1.1.debian.tar.xz
 43cac1f9f6e4266460248b2b694eaecc 8508 admin extra 
deltarpm_3.6+dfsg-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl3TP4AACgkQwpPntGGC
Ws6RfhAAh1TF3KfwCsolwzm484LrvOSmYGkbggGyQmkqnOWZQ4hdNXq7gwvLwya0
uZgUPLkAfrqxnjNtkWTn2ryWvotXjVhML55GbISSFG1J/v2dVkYPknVQzNply4TB
PufKQHSH1bwgPRUbkzcx5g80t+7hcFpCU7Fm+HNNzk2ZEZBAFNPRAnM9x4U06FYi
cmFK0f+XnQ5xV1B3VYvVO4frtxuufDPaBHr7xNLBoxxJOyTnBEQpdyYqwOzS2o3f
1GPq+hF6IT8WborcnP9dZy9M26FlzdqEA6GvovR6UWs8kIJfOmTlve7k3sJGWO23
Qrgu5CmrXsr+BL5yzMvcK9u0yx+BqdygGmyh0KJ2LdhlXyGMv2QPR3jIztFjP2gI
6PoMHyzd2kpqb8AURZhmLiH3eYatRNWPMYrmJhl+BND80fWcLHyeviWQD23864G/
Gijqt8hEs7inXfNeMh1+OS4UPXOgBeMMNJAbE9eE7U0qB7yspk1QomvUaj6Ws/+5
R6jyn1m3rlx21cNbZ8AWritbbvuCSRto/NJpZPqHLZF6xCUVDCeFfOaWNnBqGD+j
dKNPXlOsx1ZXIDoyNdLva6wT1FNWbSoUm4E3jtR2htsJ2OF13G8uzVqUSougU864
+nhjC22spCsIkcRBFK8y1++AFtNy5GNJjQtJwkl8ibPs+pu69vI=
=Jz4C
-END PGP SIGNATURE End Message ---

Bug#945064: unrardll needs a sourceful upload to support python3.8?

[Norbert Preining]

Hi Matthias,

On Tue, 19 Nov 2019, Matthias Klose wrote:
> unrardll shows up in
> https://release.debian.org/transitions/html/python3.8.html
> 
> but cannot be binNMUed because it's a contrib package b-d on a non-free 
> package.
>  Please do a sourceful upload to add support for Python 3.8.

No problem. Are there any changes besides a new upload that need to go
in?

debian/rules:
dh $@ --with python2,python3 --buildsystem=pybuild

debian/control:
Build-Depends: ... python3-all-dev ...

?

Best

Norbert

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

Bug#875038: marked as done ([lmms] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 01:06:49 +
with message-id 
and subject line Bug#875038: fixed in lmms 1.2.1+dfsg1-1
has caused the Debian Bug report #875038,
regarding [lmms] Future Qt4 removal from Buster
to be marked as done.

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

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


-- 
875038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lmms
Version: 1.1.3-7
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


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

[announced] 


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

[OpenSSL 1.1 support] 

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

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

= Porting =

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

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

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

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

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

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: lmms
Source-Version: 1.2.1+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
lmms, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated lmms 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, 20 Nov 2019 01:39:58 +0100
Source: lmms
Architecture: source
Version: 1.2.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 870473 875038 893852 925771 945099
Changes:
 lmms (1.2.1+dfsg1-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Salsa Pipeline ]
   * Update salsa CI pipeline
 .
   [ Dennis Braun ]
   * Remove non-free projects/songs to meet the dfsg
   * debian/copyright: Merge with upstream & update
   * Sort and refresh Build-Depends to support more features
 See https://github.com/LMMS/lmms/wiki/Dependencies-Debian
   * Update lmms.install & lmms-common.install
 + Add new icons, remove old ones
 + Add bash-completion
 + Add usr/share/lmms/projects/tutorials/
 + Remove "Cool Songs", not anymore in upstream
   * debian/lmms-vst.install: Add & replace lmms-vst-server
 + Add all the lmms vst related plugins to the package
   * debian/rules: Add -DWANT_QT5=1 to CMAKE_OPTS
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
   * d/changelog: Remove trailing whitespaces
 .
   [ Ross Gammon ]
   * Incorporate Ubuntu changes to avoid FTBFS on ppc64el there
   * Drop calf-ladspa package, keep internal to lmms (Closes: #870473)
   * New upstream release (Closes: #893852)
   * Update build dependencies for new version including QT5
 (Closes: #875038) (LP: #1757751)
   * Drop patches applied upstream
 

Bug#945118: marked as done (asymptote: FTBFS because of grffile)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 10:07:16 +0900
with message-id <20191120010716.m36ygueyb2u2u...@bulldog.preining.info>
and subject line Re: Bug#945118: asymptote: FTBFS because of grffile
has caused the Debian Bug report #945118,
regarding asymptote: FTBFS because of grffile
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.)


-- 
945118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asymptote
Version: 2.60-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hello!

The fix for bug [#944916] seems to be somehow incomplete and
prevents the package from [building].

[#944916]: 
[building]: 


I thought that file doc/asymptote.sty was generated from
doc/asy-latex.dtx ...
However, for reasons I am not sure I understand, I see that
doc/asymptote.sty is also committed to the git repository.
And it still [includes] the line:

  \RequirePackage[space]{grffile}

[includes]: 


I don't fully understand why the invocations of ../asy do not
use the just re-generated doc/asymptote.sty ...

Oh well, I am sure you have already figured out what's wrong!
Please fix it.

Bye and thanks for your time and dedication!   :-)
--- End Message ---
--- Begin Message ---
Version: 2.61-1

closing this bug now, the release is already tagged, so I don't rewrite
the tag and changelog. WIll add the closing to the changelog later.

Best.

Norbert

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

Bug#925771: marked as done (lmms: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 01:06:49 +
with message-id 
and subject line Bug#925771: fixed in lmms 1.2.1+dfsg1-1
has caused the Debian Bug report #925771,
regarding lmms: 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.)


-- 
925771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lmms
Version: 1.1.3-8.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/lmms_1.1.3-8.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.

[...]
[ 71%] Building CXX object 
plugins/LadspaEffect/cmt/CMakeFiles/cmt.dir/src/peak.o
cd /<>/obj-x86_64-linux-gnu/plugins/LadspaEffect/cmt && 
/usr/bin/c++  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_XML_LIB 
-Dcmt_EXPORTS -I/<>/include -isystem /usr/include/qt4 -isystem 
/usr/include/qt4/QtGui -isystem /usr/include/qt4/QtXml -isystem 
/usr/include/qt4/QtCore  -O2 -g -fno-exceptions -Wall -Werror=unused-function 
-Wno-sign-compare -Wno-strict-overflow -Werror -Wno-array-bounds -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -Wno-error=format-truncation -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -DPIC -fPIC   
-D'QT_TRANSLATIONS_DIR="/usr/share/qt4/translations"'  -fPIC -o 
CMakeFiles/cmt.dir/src/peak.o -c 
/<>/plugins/LadspaEffect/cmt/src/peak.cpp
[ 71%] Building CXX object 
plugins/LadspaEffect/cmt/CMakeFiles/cmt.dir/src/phasemod.o
cd /<>/obj-x86_64-linux-gnu/plugins/LadspaEffect/cmt && 
/usr/bin/c++  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_XML_LIB 
-Dcmt_EXPORTS -I/<>/include -isystem /usr/include/qt4 -isystem 
/usr/include/qt4/QtGui -isystem /usr/include/qt4/QtXml -isystem 
/usr/include/qt4/QtCore  -O2 -g -fno-exceptions -Wall -Werror=unused-function 
-Wno-sign-compare -Wno-strict-overflow -Werror -Wno-array-bounds -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -Wno-error=format-truncation -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -DPIC -fPIC   
-D'QT_TRANSLATIONS_DIR="/usr/share/qt4/translations"'  -fPIC -o 
CMakeFiles/cmt.dir/src/phasemod.o -c 
/<>/plugins/LadspaEffect/cmt/src/phasemod.cpp
[ 71%] Building CXX object 
plugins/LadspaEffect/cmt/CMakeFiles/cmt.dir/src/pink.o
cd /<>/obj-x86_64-linux-gnu/plugins/LadspaEffect/cmt && 
/usr/bin/c++  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_XML_LIB 
-Dcmt_EXPORTS -I/<>/include -isystem /usr/include/qt4 -isystem 
/usr/include/qt4/QtGui -isystem /usr/include/qt4/QtXml -isystem 
/usr/include/qt4/QtCore  -O2 -g -fno-exceptions -Wall -Werror=unused-function 
-Wno-sign-compare -Wno-strict-overflow -Werror -Wno-array-bounds -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -Wno-error=format-truncation -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -DPIC -fPIC   
-D'QT_TRANSLATIONS_DIR="/usr/share/qt4/translations"'  -fPIC -o 
CMakeFiles/cmt.dir/src/pink.o -c 
/<>/plugins/LadspaEffect/cmt/src/pink.cpp
[ 71%] Building CXX object 
plugins/LadspaEffect/cmt/CMakeFiles/cmt.dir/src/pink_full.o
cd /<>/obj-x86_64-linux-gnu/plugins/LadspaEffect/cmt && 
/usr/bin/c++  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_XML_LIB 
-Dcmt_EXPORTS -I/<>/include -isystem /usr/include/qt4 -isystem 

Bug#945118: asymptote: FTBFS because of grffile

[Norbert Preining]

On Wed, 20 Nov 2019, Francesco Poli (wintermute) wrote:
> The fix for bug [#944916] seems to be somehow incomplete and
> prevents the package from [building].

Indeed, already fixed for 2.61-1 to be uploaded in a minute ... ;-)
Didn't have WIFI in the airplane yesterday night.

> I don't fully understand why the invocations of ../asy do not
> use the just re-generated doc/asymptote.sty ...

The source code (asy) generated tex code also includes grffile.
I removed all of that, it is already in the git repo.

Best

Norbert

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

Processed: tagging 943609, tagging 942794, tagging 942804

[Debian Bug Tracking System]

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

> tags 943609 + experimental
Bug #943609 [src:breezy] breezy ftbfs with python 3.8
Added tag(s) experimental.
> tags 942794 + experimental
Bug #942794 {Done: Drew Parsons } [src:python-scipy] scipy 
ftbfs trying to build the docs with python3.8
Added tag(s) experimental.
> tags 942804 + experimental
Bug #942804 {Done: Drew Parsons } [src:petsc4py] fix build 
with python3.8
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Processed: limit source to lmms, tagging 893852, tagging 945099, tagging 875038, tagging 925771

[Debian Bug Tracking System]

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

> limit source lmms
Limiting to bugs with field 'source' containing at least one of 'lmms'
Limit currently set to 'source':'lmms'

> tags 893852 + pending
Bug #893852 [src:lmms] lmms: Please package new version and migrate to Qt5
Added tag(s) pending.
> tags 945099 + pending
Bug #945099 [lmms] lmms: Bump to version 1.2.1
Added tag(s) pending.
> tags 875038 + pending
Bug #875038 [src:lmms] [lmms] Future Qt4 removal from Buster
Added tag(s) pending.
> tags 925771 + pending
Bug #925771 [src:lmms] lmms: ftbfs with GCC-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#945118: asymptote: FTBFS because of grffile

[Francesco Poli (wintermute)]

Package: asymptote
Version: 2.60-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hello!

The fix for bug [#944916] seems to be somehow incomplete and
prevents the package from [building].

[#944916]: 
[building]: 


I thought that file doc/asymptote.sty was generated from
doc/asy-latex.dtx ...
However, for reasons I am not sure I understand, I see that
doc/asymptote.sty is also committed to the git repository.
And it still [includes] the line:

  \RequirePackage[space]{grffile}

[includes]: 


I don't fully understand why the invocations of ../asy do not
use the just re-generated doc/asymptote.sty ...

Oh well, I am sure you have already figured out what's wrong!
Please fix it.

Bye and thanks for your time and dedication!   :-)

Bug#945088: prewikka: depends on unexisting package

[Thomas Andrejak]

Hello

I'm waiting for this ITP :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941657

Regards

Thomas

Le mar. 19 nov. 2019 à 14:15, Gianfranco Costamagna <
locutusofb...@debian.org> a écrit :

> Source: prewikka
> Version: 5.1.1-1
> Severity: serious
>
> Hello,
> prewikka/amd64 unsatisfiable Depends: python3-lark-parser
> prewikka/i386 unsatisfiable Depends: python3-lark-parser
>
> Does this package depend on something that is not yet in the archive?
>
> Can you please have a look? Testing migration is stalled by this
>
>
> Gianfranco
>
>

Bug#944242: Test issues with BioPython 1.75

[Andreas Tille]

On Tue, Nov 19, 2019 at 10:03:25AM +, Peter Cock wrote:
> 
> Do you have a list of things still depending on Biopython & Python 2.7
> handy? We're discussing when exactly to drop Python 2.7 support -
> with a final compatible release in December 2019 or January 2020
> looking most likely.

Speaking about droping Python2 and just running tests with Python3
I was running into other errors:

==
FAIL: kmedoids (Bio.Cluster._cluster)
Doctest: Bio.Cluster._cluster.kmedoids
--
Traceback (most recent call last):
  File "/usr/lib/python3.8/doctest.py", line 2196, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for Bio.Cluster._cluster.kmedoids
  File 
"/build/python-biopython-1.75+dfsg/.pybuild/cpython3_3.8/build/Bio/Cluster/_cluster.cpython-38-x86_64-linux-gnu.so",
 line unknown line number, in kmedoids

--
File 
"/build/python-biopython-1.75+dfsg/.pybuild/cpython3_3.8/build/Bio/Cluster/_cluster.cpython-38-x86_64-linux-gnu.so",
 line ?, in Bio.Cluster._cluster.kmedoids
Failed example:
distance = array([[0.0, 1.1, 2.3],
  [1.1, 0.0, 4.5],
  [2.3, 4.5, 0.0]])
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.8/doctest.py", line 1328, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
distance = array([[0.0, 1.1, 2.3],
NameError: name 'array' is not defined
--
File 
"/build/python-biopython-1.75+dfsg/.pybuild/cpython3_3.8/build/Bio/Cluster/_cluster.cpython-38-x86_64-linux-gnu.so",
 line ?, in Bio.Cluster._cluster.kmedoids
Failed example:
distance = array([1.1, 2.3, 4.5])
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.8/doctest.py", line 1328, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
distance = array([1.1, 2.3, 4.5])
NameError: name 'array' is not defined
--
File 
"/build/python-biopython-1.75+dfsg/.pybuild/cpython3_3.8/build/Bio/Cluster/_cluster.cpython-38-x86_64-linux-gnu.so",
 line ?, in Bio.Cluster._cluster.kmedoids
Failed example:
distance = [array([]),
array([1.1]),
array([2.3, 4.5])]
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.8/doctest.py", line 1328, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
distance = [array([]),
NameError: name 'array' is not defined


==
FAIL: pca (Bio.Cluster._cluster)
Doctest: Bio.Cluster._cluster.pca
--
Traceback (most recent call last):
  File "/usr/lib/python3.8/doctest.py", line 2196, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for Bio.Cluster._cluster.pca
  File 
"/build/python-biopython-1.75+dfsg/.pybuild/cpython3_3.8/build/Bio/Cluster/_cluster.cpython-38-x86_64-linux-gnu.so",
 line unknown line number, in pca

--
File 
"/build/python-biopython-1.75+dfsg/.pybuild/cpython3_3.8/build/Bio/Cluster/_cluster.cpython-38-x86_64-linux-gnu.so",
 line ?, in Bio.Cluster._cluster.pca
Failed example:
columnmean + dot(coordinates, pc)
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.8/doctest.py", line 1328, in __run
exec(compile(example.source, filename, "single",
  File "", line 1, in 
columnmean + dot(coordinates, pc)
NameError: name 'columnmean' is not defined


==
FAIL: treecluster (Bio.Cluster._cluster)
Doctest: Bio.Cluster._cluster.treecluster
--
Traceback (most recent call last):
  File "/usr/lib/python3.8/doctest.py", line 2196, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for Bio.Cluster._cluster.treecluster
  File 
"/build/python-biopython-1.75+dfsg/.pybuild/cpython3_3.8/build/Bio/Cluster/_cluster.cpython-38-x86_64-linux-gnu.so",
 line unknown line number, in treecluster

--
File 
"/build/python-biopython-1.75+dfsg/.pybuild/cpython3_3.8/build/Bio/Cluster/_cluster.cpython-38-x86_64-linux-gnu.so",
 line ?, in Bio.Cluster._cluster.treecluster
Failed example:
distance = array([[0.0, 1.1, 2.3],
 

Bug#875065: [odin] Future Qt4 removal from Buster -> odin is ready for Qt5

[Moritz Mühlenhoff]

> On Fri, Oct 11, 2019 at 11:08:02PM +0200, Moritz Mühlenhoff wrote:
> > On Wed, Jan 23, 2019 at 09:46:28AM +0100, thies wrote:
> > > Dear all,
> > > 
> > > odin should compile on Buster without changes using the packages 
> > > qt5-default
> > > and libqwt-qt5-dev.
> > 
> > This bug hasn't seen any maintainer followup since two years, are the 
> > maintainers
> > planning to make this change?
> > 
> > We're now moving forward with the Qt4 removal, if there no immediate plans 
> > to
> > switch port odin to Qt5, we'll request to remove it from the archive.

On Sat, Oct 12, 2019 at 08:09:09AM +0200, Andreas Tille wrote:
> I can do so not before November 4th, Andreas.

What's the status?

Cheers,
Moritz

Bug#933019: Adjust for GlusterFS API change

[Moritz Mühlenhoff]

On Fri, Nov 08, 2019 at 05:23:30PM +0100, Jakob Haufe wrote:
> Dear Bareos maintainers,
> 
> this FTBFS can be fixed rather easily.
> 
> Based on [1] I created [2].
> 
> An upcoming 18.2 upstream release will contain a fallback for GlusterFS
> 5 as well, but I don't see a point in backporting this logic to the
> autotools stuff in 17.2 as GlusterFS 6 is available even in buster via
> backports.
> 
> I could do an NMU as well if you want.

Given the lack of feedback, go ahead I'd say...

Cheers,
Moritz

Bug#875137: [qjoypad] Future Qt4 removal from Buster

[Moritz Mühlenhoff]

On Thu, Oct 31, 2019 at 11:56:13PM +0100, Moritz Mühlenhoff wrote:
> On Sat, Sep 09, 2017 at 11:06:18PM +0200, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > Source: qjoypad
> > Version: 4.1.0-2.1
> > Severity: wishlist
> > User: debian-qt-...@lists.debian.org
> > Usertags: qt4-removal
> > 
> > 
> > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> > as [announced] in:
> > 
> > [announced] 
> > 
> > 
> > Currently Qt4 has been dead upstream and we are starting to have problems
> > maintaining it, like for example in the [OpenSSL 1.1 support] case.
> > 
> > [OpenSSL 1.1 support] 
> > 
> > 
> > In order to make this move, all packages directly or indirectly depending on
> > the Qt4 libraries have to either get ported to Qt5 or eventually get
> > removed from the Debian repositories.
> > 
> > Therefore, please take the time and:
> > - contact your upstream (if existing) and ask about the state of a Qt5
> > port of your application
> > - if there are no activities regarding porting, investigate whether there 
> > are
> > suitable alternatives for your users
> > - if there is a Qt5 port that is not yet packaged, consider packaging it
> > - if both the Qt4 and the Qt5 versions already coexist in the Debian
> > archives, consider removing the Qt4 version
> 
> qjoypad seems dead upstream, but there's a fork at 
> https://github.com/panzi/qjoypad
> which supports Qt5. Does anyone plan to switch the package to the port? 
> Otherwise
> let's remove it as we're moving forward with the Qt4 removal.

I've filed a removal bug now.

Cheers,
Moritz

Bug#944948: marked as done (tnetstring: needs an explicit build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 21:37:07 +
with message-id 
and subject line Bug#944948: fixed in tnetstring3 0.3.1-3
has caused the Debian Bug report #944948,
regarding tnetstring: needs an explicit build dependency on dh-python
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.)


-- 
944948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tnetstring
Version: 0.3.1-2
Severity: serious
Tags: sid bullseye

python3-all and python3-dev now dropped the dependency on
dh-python:

[ Piotr Ożarowski ]
   * Remove dh-python dependency from python3-all and python3-dev packages.
 Packages should build depend on dh-python or dh-sequence-python3 instead.

Please add an explicit build dependency on dh-python.
--- End Message ---
--- Begin Message ---
Source: tnetstring3
Source-Version: 0.3.1-3

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

Debian distribution maintenance software
pp.
Jan Niehusmann  (supplier of updated tnetstring3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Nov 2019 21:02:05 +0100
Source: tnetstring3
Architecture: source
Version: 0.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Jan Niehusmann 
Changed-By: Jan Niehusmann 
Closes: 944948
Changes:
 tnetstring3 (0.3.1-3) unstable; urgency=medium
 .
   * Build-depend on dh-python (Closes: #944948)
Checksums-Sha1:
 dec0539e7664e015cfe005eb8c14f42cd2c01aff 1785 tnetstring3_0.3.1-3.dsc
 59f96f8f6244ee4e61fae6b91b73c9be3df6b301 4152 tnetstring3_0.3.1-3.debian.tar.xz
 a4b825c513dc56901aea6a33cd54428d7e670e54 6673 
tnetstring3_0.3.1-3_amd64.buildinfo
Checksums-Sha256:
 06bb24f9e8b2ac0206d01c7517dcc9e86b64da686643dec22145c4a8acd3cd78 1785 
tnetstring3_0.3.1-3.dsc
 ccc1c758ce8a626f775d5c3778169899507c3110e6ce9470518dcba16d2036c1 4152 
tnetstring3_0.3.1-3.debian.tar.xz
 7600693657ffea3f16674154f417ce963a0512d08cb351b7dfafedc9fe1f6e5b 6673 
tnetstring3_0.3.1-3_amd64.buildinfo
Files:
 49aef963cde11d73bd8f15c595f92933 1785 python optional tnetstring3_0.3.1-3.dsc
 47b9d71f3195aa285ebd23ebaa17a457 4152 python optional 
tnetstring3_0.3.1-3.debian.tar.xz
 205166ee8492ab394140f77d9d493846 6673 python optional 
tnetstring3_0.3.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQHDBAEBCgAtFiEE+20yASySVog94MmzwkDOmV0CaxEFAl3UXVAPHGphbkBkZWJp
YW4ub3JnAAoJEMJAzpldAmsRYH8L/35FYIOnkgWOTsoa9TiB9h2IejQFLtnwrH0g
gE9RzlZTk/2GJQXvFeNH+fsUHbsCQhNOPTsCpRqgzmBa2D96qZTjhZgvV/DakPkL
qYfbY3+3XSekY+HEDr2aYjScuQ4QLJ18pAcLH7OdQvTF87WTgz1xW0cJ4BiN/MQ1
LFb++3LGfUOUtwdtwssDK/HXroKtluxHfaqThTnZrqy0tY/BC5Y790FAZP4RDdf3
2PMzrHp1ZYfhEHsMQJOVNPFHEHohmOYBR7vy5sjtzHSBVeYVw/uX2apB/xOna5QQ
hFRTIZwZn+9ddJ5wHPoYV9xwMuNlq/Wb8amlCfLSKwa6gpNbdGDO9TDxXmqkHLA7
rn+Jr//V9iHvebLCCtyRbbCwX9fad7JBV1bdJblNaTl9rJaJOnYtWC4oz8qQ0JY8
86nl2MtjoJWtpDP4Vatohf8KKvK6ALmUYgaBvq2qHAWQGpAKkpHf4IWga6Jk+Yhu
UgxFf1jb1a7bL2j8QpwTB9pTlpMDfA==
=BIRF
-END PGP SIGNATURE End Message ---

Bug#944911: libfiu: FBTFS: Found too many matching python3 bindings

[Chris Lamb]

tags 944911 + upstream
thanks

Aurelien Jarno wrote:

> libfiu fails to build from source:
> | ./wrap-python 3 ./test-manyfps.py
> | Found too many matching python3 bindings

This happens because we build for all Python versions, eg:

cd bindings/python && \
set -e && for i in $(PYTHON_VERSIONS); do \
python$$i ./setup.py build; \
done

… which leaves us with:

  bindings
  └── python
  └── build
  ├── lib.linux-x86_64-3.7
  ├── lib.linux-x86_64-3.8
  ├── temp.linux-x86_64-3.7
  └── temp.linux-x86_64-3.8


… and then when we call "./wrap-python 3" this finds both the
lib.linux-x86_64-3.7 and lib.linux-x86_64-3.8 directories.

I'm not sure about the best solution here and have vaguely considered
manually deleting all but the default version of Python from
bindings/python/build but it would be preferable if we could run the
tests against all (or "all built") versions of Python. Alberto, would
this be possible?


Regards,

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

Processed: Re: Bug#944911: libfiu: FBTFS: Found too many matching python3 bindings

[Debian Bug Tracking System]

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

> tags 944911 + upstream
Bug #944911 [src:libfiu] libfiu: FBTFS: Found too many matching python3 bindings
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#944242: Test issues with BioPython 1.75

[Andreas Tille]

Hi Peter,

On Tue, Nov 19, 2019 at 10:03:25AM +, Peter Cock wrote:
> > I'd like to give you credit as the fastest upstream answering a
> > question. ;-)  Thanks a lot for it!
> 
> Lucky timing.

Anyway:  Thanks a lot.
 
> > On Tue, Nov 19, 2019 at 09:17:17AM +, Peter Cock wrote:
> > > Curious - do you have the Python 2.7 version and build details?
> >
> > I've attached the full build log.
> 
> Thanks - I'v had a quick look. There must be something different to
> how the build or installed directories are setup - our TravisCI tests
> do not pick up the C modules at all.

Hmmm, I'd love to re-implement this for the Debian package.
 
> > Hmmm, you say its harmless but its breaking the build of the Debian
> > package anyway.  So it would be good to have some means against it.
> 
> I mean I would not worry about this particular test failing - and would
> consider whitelisting this test acceptable.
> 
> Without yet being able to reproduce this and test it, does this work?:
> 
> https://github.com/peterjc/biopython/commit/5af680b5043c9f160a19e4bb0deab0ccc271280d

Unfortunately this does not work. :-(  I tried it in the packaging commit

   
https://salsa.debian.org/med-team/python-biopython/commit/bb94263daca0cd51968305805e444d0254c01c48

> If not, we could explicitly exclude the C modules from testing, maybe here:
> 
> https://github.com/biopython/biopython/blob/biopython-175/Tests/run_tests.py#L151

Neither works this

   
https://salsa.debian.org/med-team/python-biopython/commit/e22d86592d4c29c723297d3d5eb9cc63aa6f8fb8

> i.e. Add "Bio/KDTree/_CKDTree" etc to EXCLUDE_DOCTEST_MODULES
> (with the proviso that to date I've only used this with Python modules,
> you might need to include the .so extension?)

I'm not sure what you want to tell me with the last phrase in brackets.
 
> > Since you are asking about the 2.7 version:  We need to get rid of
> > Python2 as soon as all reverse depends of biopython are ported to
> > Python3 (or removed from Debian).  This might take some time but if
> > we could move this kind of doc string generation to be done by Python3
> > this would be some step in the right direction.
> 
> Do you have a list of things still depending on Biopython & Python 2.7
> handy?

As far as I interpret

apt-cache rdepends python-biopython

it is

   srst2
   seqsero
   prime-phylo
   nanopolish

nothing that I would mind to crash for some time span.  If it can not be
ported it will be removed anyway.  So if you decide to drop Python2
support that would set a clear signal.  If it is the safest means to
get rid of the above trouble I'm all for it.

> We're discussing when exactly to drop Python 2.7 support -
> with a final compatible release in December 2019 or January 2020
> looking most likely.

Sounds sensible.

Kind regards

Andreas. 

-- 
http://fam-tille.de

Bug#907231: Ping - ktp-contact-list FTBFS

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

El vie., 15 nov. 2019 10:45, John Scott  escribió:

> ktp-contact-list has been kept out of testing for over a year, though this
> issue is fixed by the patch and new upstream version. If help is wanted
> with this, please let it be known.
>


I'll be happy to sponsor a fix, feel free to send a merge request to
salsa.debian.org's repo and then ping me.

>

Processed: reopening 936015

[Debian Bug Tracking System]

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

> reopen 936015
Bug #936015 {Done: Bernd Zeimetz } [src:ceph] ceph: 
CVE-2019-10222
'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 14.2.4-1.
> thanks
Stopping processing here.

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

Bug#944342: marked as done (wheel calls python instead of python2 in the autopkg tests)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 18:38:12 +
with message-id 
and subject line Bug#944342: fixed in wheel 0.33.6-2
has caused the Debian Bug report #944342,
regarding wheel calls python instead of python2 in the autopkg tests
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.)


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

Package: src:wheel
Version: 0.33.6-1
Severity: serious
Tags: sid bullseye patch

wheel calls python instead of python2 in the autopkg tests, patch at
http://launchpadlibrarian.net/450438712/wheel_0.33.6-1_0.33.6-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: wheel
Source-Version: 0.33.6-2

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

Debian distribution maintenance software
pp.
Nicolas Dandrimont  (supplier of updated wheel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Nov 2019 18:57:35 +0100
Source: wheel
Architecture: source
Version: 0.33.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Nicolas Dandrimont 
Closes: 944342
Changes:
 wheel (0.33.6-2) unstable; urgency=medium
 .
   * Team upload.
   * Use /usr/bin/python2 for autopkgtests (Closes: #944342)
Checksums-Sha1:
 ee95b426ba278a2616d4014ee16e08b852af1125 2252 wheel_0.33.6-2.dsc
 53a28dff4d028e5b82969fd02ea959b816893a5f 9508 wheel_0.33.6-2.debian.tar.xz
 25ad679dafca146d127449756a9ba994532b3c99 8030 wheel_0.33.6-2_amd64.buildinfo
Checksums-Sha256:
 bccef4b4b44e82d7dae40e01cea24330442ae5f2eaee746c007b5ef0b6dfacb0 2252 
wheel_0.33.6-2.dsc
 eec48d4ea280305585221d1d4e818129fa36408401d267695059ede7314cc70b 9508 
wheel_0.33.6-2.debian.tar.xz
 7262926cb026eb3128e6f16c5692233ce442a228f7c3aa975c5e0e55ed71ac0e 8030 
wheel_0.33.6-2_amd64.buildinfo
Files:
 474509a39364c36ff2b9adc195bbd048 2252 python optional wheel_0.33.6-2.dsc
 4c059d9751ca7a9bd90152164f1ef041 9508 python optional 
wheel_0.33.6-2.debian.tar.xz
 db07c01e6404424b1dfaf4c979b30756 8030 python optional 
wheel_0.33.6-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEMpGQCo4g4u9D+PnY3K6QUi5xIr8FAl3ULzkRHG9sYXNkQGRl
Ymlhbi5vcmcACgkQ3K6QUi5xIr8meQ//V/KtEJya9BVHYrKfVL3EVNqC9xYHGZr3
V6fNTeNKJRALvdDQXA/ehqtC53ZZW38wedXtUxxEAUOnAH4cFaMIXrn5X3JU2C7c
GyLhHXpbm+pSvIrcXGG7hYg/n+jcNS/2Rbp+2nIU1k+dxvobDYzx5eh7yA0lBQOj
+CCJkNQtfXUU1HICXlPpPTWfBGICex6gcyNhXhkvgUxXgvaGV7QhAOeUjx3ZZSkh
NuFFYOF4Hs1BbWoaKB+EBfXDkykg/S+1bb65IBhQSE6FcVZiG53W1WvJySlqh6t+
OQsyLkpSr6ETgAjPwcMMiJ3ecVBv4NpBCaf3cWxr6JQwYpfdHQo2sJTl1uDCuTjc
KrjDVLyVXx/SF5Puh2Ba38yo8k7xyrN1hA1E117t6M4cdk0P+1z+TZudBnHzpZze
E8PxkKNFodPID4qqF4JfqKXSxVrVlQtsIh8Ou+Cuz5OpMXz1WVk++1RmTdo76IGR
KiUpPgwPxS2Ytz6U5TAhqDxsODBlmP+lIK4Npkzu5DaaAdY+CVkTL7NOyboVXf8D
aI1+xYKz7351TRUXwg/ewjdBzmQQVmQmSXi6zUnoM5GuYuPWq+M0nbREFCsVDRtt
/inmDxKOdTR57acO6jBIJTDCTDsz5EaXA6fRoSJ6MKkjj+FoJPzf3Y/kB7iUlEQ5
aTH+srb50IM=
=Ug/m
-END PGP SIGNATURE End Message ---

Bug#944715: marked as done (thunderbird ftbfs on mips64el during rebuild for libevent 2.1.7)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 19:01:55 +0100
with message-id <0dbba1e6-6688-41ba-bdaa-4bb9a2700...@t-online.de>
and subject line Re: Bug#944715: thunderbird ftbfs on mips64el during rebuild 
for libevent 2.1.7
has caused the Debian Bug report #944715,
regarding thunderbird ftbfs on mips64el during rebuild for libevent 2.1.7
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.)


-- 
944715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thunderbird
Version: 1:68.2.2-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the libevent transition. I binNMU'ed your package but
if fails to build on mips64el. Can you please investigate the situation?

Paul

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

Tail of log for thunderbird on mips64el:

 3:26.57 js/src> checking whether the C++ compiler supports 
-Wno-gnu-zero-variadic-macro-arguments... yes
 3:27.08 js/src> checking whether the C++ compiler supports 
-Wno-noexcept-type... yes
 3:27.60 js/src> checking whether the C++ compiler supports 
-fno-sized-deallocation... yes
 3:27.63 js/src> checking for rustc... /usr/bin/rustc
 3:27.63 js/src> checking for cargo... /usr/bin/cargo
 3:30.11 js/src> checking rustc version... 1.37.0
 3:30.30 js/src> checking cargo version... 1.36.0
 3:30.45 js/src> ERROR: Command `/usr/bin/rustc --print target-list` failed 
with exit status -10.
 3:30.83 *** Fix above errors and then restart with\
 3:30.83"./mach build"
 3:30.83 make[2]: *** [client.mk:115: configure] Error 1
 3:30.83 make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:112: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:83: build-arch] Error 2


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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 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=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NFsUACgkQnFyZ6wW9
dQqERgf8CToWmH4I9o+2089pjBxzIeMbJbR/GNNb0or5K76g+JGHb9Y10MSEANVu
7fw9qa/V67YH72NWyOTNsQ5NCLpVP0jFEGaTyiDQBFJbZaNse+QtkBvy26LfOwth
wyrRIN9+5RLPbRok8k/gbLa9PCf6/gLW/mLmcPz6u0eSZMzSSd0EH/zwxTjTJID8
FDlnMo1mymjtE9U9QB5BkSLICmdxPPy11vXo7NghHR3m73Tl26nkSGYdycJp/s29
IHvseEo0pwGQo6CUvl6cGgFp0WvT88KX4suFXS5uqkGUnH72ZsR1D0bnvxJ8Thjf
ekFQudmPd5xvoHAHPWJRMmsrqZ+3wQ==
=vRBw
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hello Paul,

Am 14.11.19 um 09:56 schrieb Paul Gevers:
> Dear maintainers,
> 
> Your package is part of the libevent transition. I binNMU'ed your package but
> if fails to build on mips64el. Can you please investigate the situation?

I've rebuild Thunderbird on eller to see if there was something
suspicious happen between the two Thunderbird releases. But the build on
the Porterbox went well (as expected) and I've used the new give-back
possibility to trigger a rebuild of Thunderbird on the mips64el buildd.

It build successful and so I'm closing this issue here.

-- 
Regards
Carsten Schoenert--- End Message ---

Bug#942101: marked as done (python-msrest build accesses the network during the build)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 18:08:40 +
with message-id 
and subject line Bug#942101: fixed in python-msrest 0.6.10-1
has caused the Debian Bug report #942101,
regarding python-msrest build accesses the network during the build
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.)


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

Package: src:python-msrest
Version: 0.6.1-1
Severity: serious
Tags: sid bullseye

according to
https://launchpadlibrarian.net/441507516/buildlog_ubuntu-eoan-amd64.python-msrest_0.6.1-1_BUILDING.txt.gz

the tests access some infrastructure.  The build must not rely on the network, 
the autopkg tests can.  Usually the Debian buildds don't check for network access.
--- End Message ---
--- Begin Message ---
Source: python-msrest
Source-Version: 0.6.10-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Nov 2019 18:46:55 +0100
Source: python-msrest
Architecture: source
Version: 0.6.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Nicolas Dandrimont 
Closes: 942101
Changes:
 python-msrest (0.6.10-1) unstable; urgency=medium
 .
   [ Luca Boccassi ]
   * Do not run tests that require internet connection at build time
 (Closes: #942101)
 .
   [ Nicolas Dandrimont ]
   * New upstream release
   * Drop python3-trio (Build-)Dependency
Checksums-Sha1:
 f93f5edbecce523c41c33628b8203073a546c8c8 2520 python-msrest_0.6.10-1.dsc
 cfa5b92117742d95afe4fa67e6d75c9a9d8b724d 97754 python-msrest_0.6.10.orig.tar.gz
 53cf9e7245930288b9f7e12130fec32d0bfffebd 2980 
python-msrest_0.6.10-1.debian.tar.xz
 9b87d8c19038ca7b0692b069ef820dc4cc730ec4 7353 
python-msrest_0.6.10-1_amd64.buildinfo
Checksums-Sha256:
 b1504feefd1701f59837fc6f012eec2147dcbd54b8316942bd49e55605dd75e5 2520 
python-msrest_0.6.10-1.dsc
 0aec73f6fa60294173e42779de52da75d8eadad146fc8043cb49d2e3bbb7cdc3 97754 
python-msrest_0.6.10.orig.tar.gz
 58f3fc8bc70160bdddf2bb4ffe2f85a43020f033cd30880420708db1d30518e1 2980 
python-msrest_0.6.10-1.debian.tar.xz
 44724839af1027f77e22150c4db49228075bb45eb5d5ed93f4c02e20184f7320 7353 
python-msrest_0.6.10-1_amd64.buildinfo
Files:
 4cda448f34cc30a8201dde69a84ccac5 2520 python optional 
python-msrest_0.6.10-1.dsc
 8008f119a4a55416086d9890dd57c780 97754 python optional 
python-msrest_0.6.10.orig.tar.gz
 7b12606f3b496858a124a2bed1e4d95c 2980 python optional 
python-msrest_0.6.10-1.debian.tar.xz
 e5962fbe8bf275f7affa7798b80624a0 7353 python optional 
python-msrest_0.6.10-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEMpGQCo4g4u9D+PnY3K6QUi5xIr8FAl3UKt8RHG9sYXNkQGRl
Ymlhbi5vcmcACgkQ3K6QUi5xIr9RDhAApGlHryhZgnyVuDL84ci4F4apulopDV9J
ElldVcOYYnD+ZAc/86c5bpL/7KFU8NBwu11D+fc7UEKESj+RIiHS0c0S9AFvX0Pi
QDe0qIiAtA3CMbH7p25Fp3RC/C6WFFAGn/rM+FHz71LDjs12j+H4imJuJE1RBMyS
v5krsiswVDEuaRrEkGdD7lXZmespDD6aTlGmmtSjPFeLrSE+7l08ai9oOEvxCRP5
Y1Z3s0cKbQFHE/xtEOwALU2uyTSsZXvtn2JNfjLa7tQqBXUPNEfOezCzLIEDCqxN
RA+QMHX6A6M4/q+Z9hNReP2FKRxrvKczoHUqci+pWXKSSvNpmYhCZzWvyD3JaONc
CNPxyKy5o9lC7y4BSIDpLx3X1VsMgWn84qtib76ycREiZD+1PZ7opTipSLWIcNUN
7xGnK4PII0qjC/vGKDMDbj3O8HW4aO+BCsjlbn2P2GBRJY7twgzs54Tmfd9oTbkw
0yINA13bZgQPP1VOEbcIUFQy4EavRvmW//VEeye8maUdoM5cN0DpfK2iiLBwDpfi
nI5dF79FTMWXxQ2OHHl5zU14uR7bWkrzlAQZcnO4KNLoQQbmKFHx1fZu25OYEvsJ
2SayEMrDA3/OID0L9TuWlliWN24ak70aV/IliNRRqHOCSi3vB5G8G0rQyKC5qsSA
6kdNh87JpxU=
=0CaD
-END PGP SIGNATURE End Message ---

Processed: Bug#944342 marked as pending in wheel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #944342 [src:wheel] wheel calls python instead of python2 in the autopkg 
tests
Added tag(s) pending.

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

Bug#944342: marked as pending in wheel

[Nicolas Dandrimont]

Control: tag -1 pending

Hello,

Bug #944342 in wheel 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/wheel/commit/a06ca8962ad7ca92a7442548b0c69c5387858920


Use /usr/bin/python2 for autopkgtests (Closes: #944342)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/944342

Bug#945061: uninstallable due to Thunderbird security update to version 68

[Carsten Schoenert]

Hello Philipp,

Am 19.11.19 um 08:43 schrieb Philipp Huebner:
> Hi,
> 
> due to the security update introducing Thunderbird 68,
> xul-ext-sogo-connector has become uninstallable and thus unusable in all
> suites from oldstable to unstable.
> 
> Could you please package sogo-connector 68?
> 
> (old-)stable updates would also be greatly appreciated.
> I'd be happy to help test updated packages.

I'd like to do so but unfortunately my time for doing so is really
limited right now. The free time I have is mainly focused on working n
Thunderbird itself.
Also upstream has released a fixed version just a few weeks ago.

For now I just can suggest to use the upstream version of this AddOn.

-- 
Regards
Carsten Schoenert

Bug#945102: marked as done (thunderbird can not be upgraded because it breaks enigmail)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 18:20:51 +0100
with message-id <4be73dad-6ebf-8d12-02d8-339459eaf...@t-online.de>
and subject line Re: Bug#945102: thunderbird can not be upgraded because it 
breaks enigmail
has caused the Debian Bug report #945102,
regarding thunderbird can not be upgraded because it breaks enigmail
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.)


-- 
945102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:60.9.0-1~deb10u1
Severity: serious
Tags: security
Justification: Policy 7.3

the upgrade to 68.2.2-1 includes security fixes but it can not be installed 
without deinstallation of enigmail
(The following packages have unmet dependencies: thunderbird : Breaks: enigmail 
(< 2:2.1.2~) but 2:2.0.12+ds1-1~deb10u1 is installed)

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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.6.1
ii  fontconfig2.13.1-2
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-10
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libdbus-1-3   1.12.16-1
ii  libdbus-glib-1-2  0.110-4
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3+deb10u1
ii  libgcc1   1:8.3.0-6
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-2+deb10u2
ii  libgtk-3-03.24.5-1
ii  libgtk2.0-0   2.24.32-3
ii  libhunspell-1.7-0 1.7.0-2
ii  libicu63  63.1-6
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.42.1-1+deb10u1
ii  libpango-1.0-01.42.4-7~deb10u1
ii  libsqlite3-0  3.27.2-3
ii  libstartup-notification0  0.12-6
ii  libstdc++68.3.0-6
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.7-1
ii  libx11-xcb1   2:1.6.7-1
ii  libxcb-shm0   1.13.1-2
ii  libxcb1   1.13.1-2
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1+b3
ii  psmisc23.2-1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-de-at [hunspell-dictionary]  20161207-7
ii  hunspell-de-ch [hunspell-dictionary]  20161207-7
ii  hunspell-de-de [hunspell-dictionary]  20161207-7
ii  hunspell-en-us [hunspell-dictionary]  1:2018.04.16-1
ii  lightning 1:60.9.0-1~deb10u1

Versions of packages thunderbird suggests:
ii  apparmor  2.13.2-10
ii  fonts-lyx 2.3.2-1
ii  libgssapi-krb5-2  1.17-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Michael,

Am 19.11.19 um 17:28 schrieb Michael Becker:
> Package: thunderbird
> Version: 1:60.9.0-1~deb10u1
> Severity: serious
> Tags: security
> Justification: Policy 7.3
> 
> the upgrade to 68.2.2-1 includes security fixes but it can not be
> installed without deinstallation of enigmail> (The following packages have 
> unmet dependencies: thunderbird :
> Breaks: enigmail (< 2:2.1.2~) but 2:2.0.12+ds1-1~deb10u1 is
> installed)

And that"s the wanted behavior. Enigmail is needed at least on version
2.1, otherwise it's simply not working. It's documented in the changelog
for 1:68.1.1-1~exp1 and introduced by this commit.

https://salsa.debian.org/mozilla-team/thunderbird/commit/3d1d27d58c6722a6ca360724f2a85a4e452e6024

Thunderbird isn't breaking Enigmail. But the package enigmail wasn't
updated in time so we need to ensure that no cruft we now about is
keeping installed. There are for sure more packaged addons out there
that would need a Breaks.

And btw. your report isn't a severity serious.

https://www.debian.org/Bugs/Developer#severities

An not added a Breaks on Enigmail would be more a case for important but
not even serious.

I see no further base for this report and will close your report now.

-- 
Regards
Carsten Schoenert--- End Message ---

Bug#945102: thunderbird can not be upgraded because it breaks enigmail

[Michael Becker]

Package: thunderbird
Version: 1:60.9.0-1~deb10u1
Severity: serious
Tags: security
Justification: Policy 7.3

the upgrade to 68.2.2-1 includes security fixes but it can not be installed 
without deinstallation of enigmail
(The following packages have unmet dependencies: thunderbird : Breaks: enigmail 
(< 2:2.1.2~) but 2:2.0.12+ds1-1~deb10u1 is installed)

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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.6.1
ii  fontconfig2.13.1-2
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-10
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libdbus-1-3   1.12.16-1
ii  libdbus-glib-1-2  0.110-4
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3+deb10u1
ii  libgcc1   1:8.3.0-6
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-2+deb10u2
ii  libgtk-3-03.24.5-1
ii  libgtk2.0-0   2.24.32-3
ii  libhunspell-1.7-0 1.7.0-2
ii  libicu63  63.1-6
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.42.1-1+deb10u1
ii  libpango-1.0-01.42.4-7~deb10u1
ii  libsqlite3-0  3.27.2-3
ii  libstartup-notification0  0.12-6
ii  libstdc++68.3.0-6
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.7-1
ii  libx11-xcb1   2:1.6.7-1
ii  libxcb-shm0   1.13.1-2
ii  libxcb1   1.13.1-2
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1+b3
ii  psmisc23.2-1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-de-at [hunspell-dictionary]  20161207-7
ii  hunspell-de-ch [hunspell-dictionary]  20161207-7
ii  hunspell-de-de [hunspell-dictionary]  20161207-7
ii  hunspell-en-us [hunspell-dictionary]  1:2018.04.16-1
ii  lightning 1:60.9.0-1~deb10u1

Versions of packages thunderbird suggests:
ii  apparmor  2.13.2-10
ii  fonts-lyx 2.3.2-1
ii  libgssapi-krb5-2  1.17-3

-- no debconf information

Bug#944993: marked as done (gnome-shell-extension-show-ip: primary-interface patch broke loading the extension)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 15:49:42 +
with message-id 
and subject line Bug#944993: fixed in gnome-shell-extension-show-ip 8-5
has caused the Debian Bug report #944993,
regarding gnome-shell-extension-show-ip: primary-interface patch broke loading 
the extension
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.)


-- 
944993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-show-ip
Version: 8-4
Severity: serious
Tags: patch

The primary-interface patch I proposed had a serious issue:

JS ERROR: Extension show...@sgaraud.github.com: ReferenceError: device is not 
defined

I've fixed the issue upstream and in the attached patch.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-shell-extension-show-ip depends on:
ii  gnome-shell  3.34.1+git20191024-1

gnome-shell-extension-show-ip recommends no packages.

gnome-shell-extension-show-ip suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
From 626ff48b7e29cf4178a2f439b85340e7b1e25774 Mon Sep 17 00:00:00 2001
From: Paul Wise 
Date: Thu, 2 Mar 2017 18:07:14 +0800
Subject: [PATCH] Show the primary IP address when no interface was chosen

Makes it easier to see all IP addresses at a glance.

Uses NM to get which interface(s) are in the default route.
---
 README.md|  1 +
 extension.js | 53 +---
 2 files changed, 43 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index 0fafb7a..eec47e3 100644
--- a/README.md
+++ b/README.md
@@ -83,6 +83,7 @@ issues](https://github.com/sgaraud/gnome-extension-show-ip/issues).
 ### License
 
 Copyright (C) 2015 Sylvain Garaud
+Copyright 2017 Paul Wise
 
 This program is free software: you can redistribute it and/or modify
 it under the terms of the GNU General Public License as published by
diff --git a/extension.js b/extension.js
index d9a7940..5dc7d9a 100644
--- a/extension.js
+++ b/extension.js
@@ -3,6 +3,7 @@
  * https://github.com/sgaraud/gnome-extension-show-ip
  * 
  * Copyright (C) 2015 Sylvain Garaud
+ * Copyright 2017 Paul Wise
  *
  * This file is part of Show-IP GNOME extension.
  * Show IP GNOME extension is free software: you can redistribute it and/or modify
@@ -170,17 +171,30 @@ const IpMenuBase = new Lang.Class({
 }
 });
 
+this._getPrimaryDevices(this.client);
+let selectedIp = '';
+let primaryIp = '';
+let firstIp = '';
 for (let device of this._devices) {
-if (device.ifc == this.selectedDevice) {
-if (Schema.get_boolean("menu")) {
-this.label.set_text(_("IP: %s").format(device.ip));
-} else {
-this.label.set_text(device.ip);
-}
-break;
+if (!selectedIp && device.ifc == this.selectedDevice) {
+selectedIp = device.ip;
+}
+if (!primaryIp && device.primary) {
+primaryIp = device.ip;
+}
+if (!firstIp) {
+firstIp = device.ip;
 }
 }
-if ('' == this.selectedDevice) {
+let ip = selectedIp ? selectedIp : primaryIp ? primaryIp : firstIp;
+if (ip) {
+if (Schema.get_boolean("menu")) {
+this.label.set_text(_("IP: %s").format(ip));
+} else {
+this.label.set_text(ip);
+}
+this.label.set_text(ip);
+} else {
 this.label.set_text(NOT_CONNECTED);
 }
 },
@@ -207,6 +221,26 @@ const IpMenuBase = new Lang.Class({
 this._createPopupMenu();
 },
 
+_getPrimaryDevices: function (nmc) {
+let primary_conn = nmc.get_primary_connection();
+let primary_devices = primary_conn.get_devices();
+let primary_ifcs = [];
+let 

Bug#944934: cracklib2: diff for NMU version 2.9.6-3.1

[Boyuan Yang]

Control: tags 944934 + patch
Control: tags 944934 + pending

Dear maintainer,

I've prepared an NMU for cracklib2 (versioned as 2.9.6-3.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Regards,
Boyuan Yang

diff -Nru cracklib2-2.9.6/debian/changelog cracklib2-2.9.6/debian/changelog
--- cracklib2-2.9.6/debian/changelog2019-10-23 07:02:23.0 -0400
+++ cracklib2-2.9.6/debian/changelog2019-11-19 10:14:51.0 -0500
@@ -1,3 +1,13 @@
+cracklib2 (2.9.6-3.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * debian/control: Add Build-dependency on dh-python to fix
+FTBFS when building with python support. A 
+mark was also included.
+(Closes: #944934)
+
+ -- Boyuan Yang   Tue, 19 Nov 2019 10:14:51 -0500
+
 cracklib2 (2.9.6-3) unstable; urgency=medium
 
   * Fix "fails to build Python 3.8 extensions" by removing the
diff -Nru cracklib2-2.9.6/debian/control cracklib2-2.9.6/debian/control
--- cracklib2-2.9.6/debian/control  2019-10-23 07:02:23.0 -0400
+++ cracklib2-2.9.6/debian/control  2019-11-19 10:14:51.0 -0500
@@ -9,6 +9,7 @@
chrpath,
cracklib-runtime ,
debhelper (>= 10),
+   dh-python ,
docbook-utils,
docbook-xml,
dpkg-dev (>= 1.16.1~),

Processed: cracklib2: diff for NMU version 2.9.6-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 944934 + patch
Bug #944934 [src:cracklib2] cracklib2: needs an explicit build dependency on 
dh-python
Added tag(s) patch.
> tags 944934 + pending
Bug #944934 [src:cracklib2] cracklib2: needs an explicit build dependency on 
dh-python
Added tag(s) pending.

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

Bug#945096: metview: FTBFS in sid

[Gianfranco Costamagna]

Source: metview
Version: 5.7.0-1
Severity: serious

Hello, looks like something added a libxxhash0 dependency on b-deps, and now it 
is FTBFS because of missing dev package

cd /<>/debian/build/metview/src/MacroEditor && /usr/bin/c++  
-DGRIB_HANDLING_PACKAGE=ecCodes -DH_INCLUDES_CC -DLITTLE_END -DMETVIEW 
-DMETVIEW_ODB -DMETVIEW_ODB_NEW -DMETVIEW_ODB_OLD -DMETVIEW_ODB_PLOT 
-DMETVIEW_QT5 -DODB_ECKIT -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB 
-DQT_WIDGETS_LIB -DQT_XMLPATTERNS_LIB -DQT_XML_LIB -DR64 -DUSE_NEW_IO 
-I/<>/debian/build/metview/module 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport 
-I/usr/include/x86_64-linux-gnu/qt5/QtSvg 
-I/<>/debian/build/metview/src/MacroEditor 
-I/<>/metview/src/MacroEditor 
-I/<>/metview/src/libMetview 
-I/<>/metview/src/libMars 
-I/<>/debian/build/metview/src/libMars 
-I/<>/metview/src -I/<>/metview/src/libFTimeUtil 
-I/<>/metview/src/Odb -I/usr/lib/include 
-I/build/odb-api/metkit/src -I/build/odb-api/debian/build/python3.8/metkit/src 
-I/usr/include/python3.8/../eclib -I/usr/include/terralib/kernel 
-I/usr/include/hdf5/serial -I/<>/metview/src/libMvQtUtil 
-I/<>/metview/src/libMvQtGui 
-I/<>/debian/build/metview/src/libMvQtGui 
-I/<>/metview/src/libMvQtGui/../uPlot 
-I/<>/mars-client/src 
-I/<>/debian/build/mars-client/src -I/usr/include/python3.8 
-I/usr/include/python3.8/.. -I/usr/include/python3.8/../eclib/eclib 
-I/usr/include/python3.8/odblib  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DACCEPT_USE_OF_DEPRECATED_PROJ_API_H -std=gnu++14 
-Wdate-time -D_FORTIFY_SOURCE=2 -pipe -fpermissive -Wno-write-strings 
-Wno-deprecated -Werror=return-type -O3 -DNDEBUG -fPIE   -fPIC -std=gnu++14 -o 
CMakeFiles/MacroEditor.dir/moc_mvplaintextedit.cpp.o -c 
/<>/debian/build/metview/src/MacroEditor/moc_mvplaintextedit.cpp
make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libxxhash.so', 
needed by 'lib/libatlas_ecmwf.so.0.17'.  Stop.
make[3]: *** Waiting for unfinished jobs
[ 53%] Building CXX object 
atlas/src/atlas/CMakeFiles/atlas_ecmwf.dir/util/Allocate.cc.o
cd /<>/debian/build/atlas/src/atlas && /usr/bin/c++  
-Datlas_ecmwf_EXPORTS -I/<>/atlas/src/atlas 
-I/<>/atlas/src -I/<>/debian/build/atlas/src 
-I/usr/include/eigen3 -I/usr/include/x86_64-linux-gnu/eckit 
-I/usr/include/x86_64-linux-gnu/eckit/geometry 
-I/usr/include/x86_64-linux-gnu/eckit/linalg 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include 
-I/usr/include/x86_64-linux-gnu/eckit/mpi 
-I/usr/include/x86_64-linux-gnu/eckit/option  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-DACCEPT_USE_OF_DEPRECATED_PROJ_API_H -std=gnu++14 -Wdate-time 
-D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -fPIC   -fopenmp -std=gnu++14 -o 
CMakeFiles/atlas_ecmwf.dir/util/Allocate.cc.o -c 
/<>/atlas/src/atlas/util/Allocate.cc


http://debomatic-amd64.debian.net/distribution#unstable/metview/5.7.0-1/buildlog

probably adding libxxhash-dev to build-deps and runtime deps fixes the issue,

I'm uploading a test fix here
https://launchpad.net/ubuntu/+source/metview/5.7.0-1ubuntu1

G.

Bug#941996: marked as done (openmpi-bin: segfaults with the 'verbs' OFI provider)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 15:08:40 +
with message-id 
and subject line Bug#941996: fixed in openmpi 4.0.2-2
has caused the Debian Bug report #941996,
regarding openmpi-bin: segfaults with the 'verbs' OFI provider
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.)


-- 
941996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openmpi-bin
Version: 3.1.3-11
Severity: serious

Hi,

This is tracked upstream as https://github.com/open-mpi/ompi/issues/7035 .

mpirun segfaults during MTL OFI provider section when run on a machine
with an InfiniBand network. This happens for the following reason: Until
version 3.1.2, OFI used an opt-in mechanism to include providers.
'verbs' wasn't included by default. This was changed by
https://github.com/open-mpi/ompi/commit/d00c387284b6197946452a0938e76615a17fa689

The discussion is still ongoing upstream, but it looks like this might
be related to the libfabric version in Debian.  The chosen solution
upstream might be to disable the 'verbs' provider.

Also, v4.x is not affected.

I believe this should be fixed in stable. Infiniband is common in HPC
clusters, so a broken OpenMPI is of limited use without its support.

Lucas


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

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

Versions of packages openmpi-bin depends on:
ii  libc62.28-10
ii  libevent-2.1-6   2.1.8-stable-4
ii  libevent-pthreads-2.1-6  2.1.8-stable-4
ii  libhwloc51.11.12-3
ii  libopenmpi3  3.1.3-11
ii  openmpi-common   3.1.3-11
ii  openssh-client [ssh-client]  1:7.9p1-10
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages openmpi-bin recommends:
ii  libopenmpi-dev  3.1.3-11

Versions of packages openmpi-bin suggests:
ii  gfortran [fortran-compiler]  4:8.3.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 4.0.2-2

We believe that the bug you reported is fixed in the latest version of
openmpi, 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.
Alastair McKinstry  (supplier of updated openmpi 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, 19 Nov 2019 11:55:49 +
Source: openmpi
Architecture: source
Version: 4.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 941996
Changes:
 openmpi (4.0.2-2) unstable; urgency=medium
 .
   * Move to unstable. Closes: #941996
   * Set OMPI_MCA_btl_base_warn_component_unused=0 by default to silence
 warnings. Add README.Debian to say so.
Checksums-Sha1:
 b46635811c162f911dd9b93d0e65bf977a1058a3 2635 openmpi_4.0.2-2.dsc
 5f3923acf4d9966d1355bab88bce972b8c73c240 63408 openmpi_4.0.2-2.debian.tar.xz
Checksums-Sha256:
 8575635c8cb8bb2d8df91a03172af2c589503d6e68a2c2e1ac17348592aa6b69 2635 
openmpi_4.0.2-2.dsc
 8cd798332d59e7d6027278c3998554a6cfdfd09e2e209771600577babcdde5cf 63408 
openmpi_4.0.2-2.debian.tar.xz
Files:
 b702a148c1b584c8aeac796f695e2c76 2635 net optional openmpi_4.0.2-2.dsc
 0d242e533c8a085bdbbe92f4d155bbcd 63408 net optional 
openmpi_4.0.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl3T/vMACgkQy+a7Tl2a
06VksA//dW5z5aRrPpz1HUlIr67tMfF7eutSx++AXgjiedkjCP6CYLnuqJxpekur
s/20nt8YEsuLEtexpk3Pk756blEUWiQtUUEecHTV5Mg4YwXt6nQpM9qCvhzTeYpb
Ov1HTZS7U3KUS50r1GePtdXetUGUsnBQAi7muP2+NG8lzsVCZtUxmV3alnRRDSu1
0FN9HFL7/9PgsGtrkGJ7muEJCRFeUj8Ixc4na7ss8g18RWTVT45BYsdOmfZVssn8
UVVDnc5My90+9ZdP6FomXXK/RRBfMUr8bl8fnZsqtQhfzaDDglmBGMNMDe0TGdwy

Processed: Re: libopencv-imgcodecs-dev depends on cruft package.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #944341 [libopencv-imgcodecs-dev] libopencv-imgcodecs-dev depends on cruft 
package.
Added tag(s) patch.
> affects -1 src:otb
Bug #944341 [libopencv-imgcodecs-dev] libopencv-imgcodecs-dev depends on cruft 
package.
Added indication that 944341 affects src:otb

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

Bug#944341: libopencv-imgcodecs-dev depends on cruft package.

[Bas Couwenberg]

Source: opencv
Version: 4.1.2+dfsg-4+b1
Followup-For: Bug #944341
Control: tags -1 patch
Control: affects -1 src:otb

Dear Maintainer,

The attached patch fixes the issue.

Note that this issue also makes the otb build dependencies uninstallable.

Kind Regards,

Bas
>From ebfc61e5d3e658f472af0f10887ed2859e8cd1b2 Mon Sep 17 00:00:00 2001
From: Bas Couwenberg 
Date: Tue, 19 Nov 2019 12:30:42 +0100
Subject: Replace libgdbm2-dev with libgdbm-dev. (closes: #944341)


diff --git a/debian/changelog b/debian/changelog
index 61d213b81..5d33e82ef 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+opencv (4.1.2+dfsg-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace libgdbm2-dev with libgdbm-dev,
+and libvtkgdcm2-dev with libvtkgdcm-dev.
+(closes: #944341)
+
+ -- Bas Couwenberg   Tue, 19 Nov 2019 12:30:06 +0100
+
 opencv (4.1.2+dfsg-4) unstable; urgency=medium
 
   * Disable MSA (MIPS* arch) to avoid ISA violation. (Closes: #942561)
diff --git a/debian/control b/debian/control
index 83abbc308..02f3c1fd7 100644
--- a/debian/control
+++ b/debian/control
@@ -21,7 +21,7 @@ Build-Depends:
  libdc1394-22-dev [linux-any],
  libeigen3-dev,
  libgdal-dev,
- libgdcm2-dev [!hppa !m68k !powerpcspe !riscv64 !sh4 !sparc64 !x32],
+ libgdcm-dev [!hppa !m68k !powerpcspe !riscv64 !sh4 !sparc64 !x32],
  libgl1-mesa-dev,
  libglu1-mesa-dev,
  libgoogle-glog-dev,
@@ -40,7 +40,7 @@ Build-Depends:
  libtiff-dev,
  libv4l-dev [linux-any],
  libvtk6-dev,
- libvtkgdcm2-dev [!alpha !ppc64 !riscv64 !x32],
+ libvtkgdcm-dev [!alpha !ppc64 !riscv64 !x32],
  libgdcm-tools,
  maven-repo-helper,
  ocl-icd-opencl-dev,
@@ -297,7 +297,7 @@ Section: libdevel
 Architecture: any
 Multi-Arch: same
 Depends:
- libgdcm2-dev [!hppa !m68k !powerpcspe !riscv64 !sh4],
+ libgdcm-dev [!hppa !m68k !powerpcspe !riscv64 !sh4],
  libopencv-imgcodecs4.1 (= ${binary:Version}),
  libopencv-imgproc-dev (= ${binary:Version}),
  ${misc:Depends},
-- 
2.20.1

Bug#943655: marked as done (pgmodeler FTBFS: src/databasemodel.cpp:768:53: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 13:20:07 +
with message-id 
and subject line Bug#943655: fixed in pgmodeler 0.9.2~beta2-1
has caused the Debian Bug report #943655,
regarding pgmodeler FTBFS: src/databasemodel.cpp:768:53: error: format not a 
string literal and no format arguments [-Werror=format-security]
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.)


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

pgmodeler fails to build from source everywhere (in particular on
buildds):

src/databasemodel.cpp:768:53: error: format not a string literal and no format 
arguments [-Werror=format-security]

I need a bug number for tracking this.

Helmut
--- End Message ---
--- Begin Message ---
Source: pgmodeler
Source-Version: 0.9.2~beta2-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pgmodeler 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, 19 Nov 2019 13:23:16 +0100
Source: pgmodeler
Architecture: source
Version: 0.9.2~beta2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
Changed-By: Christoph Berg 
Closes: 943655
Changes:
 pgmodeler (0.9.2~beta2-1) unstable; urgency=medium
 .
   * New upstream release, fixes FTBFS. (Closes: #943655)
Checksums-Sha1:
 f434c1caa2909dd47fbcd473e3ef8780763b6f3b 2131 pgmodeler_0.9.2~beta2-1.dsc
 96f05d6abc5ece2292c7c96be39ce7bec190e10a 3929398 
pgmodeler_0.9.2~beta2.orig.tar.gz
 47c129427456ab86dc862dce7db458dec680fab1 3200 
pgmodeler_0.9.2~beta2-1.debian.tar.xz
Checksums-Sha256:
 fcea51684ec5fbeeb6f7febd25d16ccaf1bf9a916ddc917ff76a867ffdca37e3 2131 
pgmodeler_0.9.2~beta2-1.dsc
 78dd7c16e52bd46d318ae50e49862e8f1fea45bf4bdecf84886e1aca7ca30312 3929398 
pgmodeler_0.9.2~beta2.orig.tar.gz
 0fd8cf61e3f150944f453a94efc141057e4a61a0d8f5669ee23bfb8fcae42ec0 3200 
pgmodeler_0.9.2~beta2-1.debian.tar.xz
Files:
 75d95efaddc318bfb71995e0be3b2461 2131 database optional 
pgmodeler_0.9.2~beta2-1.dsc
 8c4663ebcbfe5ce5631c939afdf281f8 3929398 database optional 
pgmodeler_0.9.2~beta2.orig.tar.gz
 bcccfd821a1f0ca17eb40e1e365ac315 3200 database optional 
pgmodeler_0.9.2~beta2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl3T6McACgkQTFprqxLS
p67aJhAAgzFABhEK7vYcOjGszvlhMTp/ui7Rv9vYTgA1Yq8b63vDc48Ce6WlieFs
WYsrJ8OC75IjMWxss18EwbMX3P0Qv+NGO+lhHWskguW2jyrU9RODhcUExleovy9l
Vmt7d66WJY0owvGPvIg1h+2vTnjcmtb7iSkxVlj3jmCimgTJ2K/6kavK8CmUr79Q
FP54tH4m+ahwYDAvZrMd9YM19JqKIYiLZ51q5AGcGQzLLXOO4K0+zuqXK7qfognq
jgpSoLG/+fTrlLvfD9XYlmxYP7YHXW0Wg1gSMRX9iO41ET4ha4sziVcyDbP2Pt+N
9mcgJCkEXvzM7mAZ384/Ey8eTzQnQw2ij/l6FPoJuBIpmrbl+T4acTUW3Wwxu84l
qfngSEa/HuxTT4wKG1IJ5GCu2eZl1nbg7lVC1jmgbR3aCVpJu0oJXnJdIjRN3FOS
Yw+aHS2Brvp9Hqim3pGh2lwL+M6v6j57Ka39NYUhaVefxVjHkvgDc2wx+oXC6apc
DWIjrT/uQtYwnsNqzgXPUA5PxIr25064TJGQikwbAogZEjLOJr/prOrVhl0mqO6x
Q3FY+POBfkSQJGHxOU8YH5EkO1sNkzHqIAw+ZbPkkSYcgXJ7sESCfnC5ZpqG22DI
lxyOxYkBk31a+VAaWaZeNi8F63hCfizVEePqoS4Hrv2Vnl1n8jc=
=461p
-END PGP SIGNATURE End Message ---

Bug#945088: prewikka: depends on unexisting package

[Gianfranco Costamagna]

Source: prewikka
Version: 5.1.1-1
Severity: serious

Hello,
prewikka/amd64 unsatisfiable Depends: python3-lark-parser
prewikka/i386 unsatisfiable Depends: python3-lark-parser

Does this package depend on something that is not yet in the archive?

Can you please have a look? Testing migration is stalled by this


Gianfranco

Bug#944714: moonshot-trust-router ftbfs during rebuilds for libevent 2.1.7

[Sam Hartman]

control: tags -1 patch

> "peter" == peter green  writes:

peter> Tags 944714 +patch Thanks.

peter> The easy fix here is to remove -Werror, in the long term of
peter> course migration to a non-deprecated type should be
peter> considered but that is IMO an issue for upstream not Debian.

I'm associated enough with upstream that I'll just fix correctly.
Thanks though.

Processed: Re: Bug#944714: moonshot-trust-router ftbfs during rebuilds for libevent 2.1.7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #944714 [src:moonshot-trust-router] moonshot-trust-router ftbfs during 
rebuilds for libevent 2.1.7
Ignoring request to alter tags of bug #944714 to the same tags previously set

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

Bug#944242: Test issues with BioPython 1.75

[Peter Cock]

On Tue, Nov 19, 2019 at 10:03 AM Peter Cock  wrote:
>
> I mean I would not worry about this particular test failing - and would
> consider whitelisting this test acceptable.
>
> Without yet being able to reproduce this and test it, does this work?:
>
> https://github.com/peterjc/biopython/commit/5af680b5043c9f160a19e4bb0deab0ccc271280d
>

If that works, this pull request will apply the change upstream to Biopython:

https://github.com/biopython/biopython/pull/2347

Peter

Processed: Bug#943655 marked as pending in pgmodeler

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #943655 [src:pgmodeler] pgmodeler FTBFS: src/databasemodel.cpp:768:53: 
error: format not a string literal and no format arguments 
[-Werror=format-security]
Added tag(s) pending.

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

Bug#943655: marked as pending in pgmodeler

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #943655 in pgmodeler 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/postgresql/pgmodeler/commit/eb851da0846cf0fce2bb808257db6b5a75702af8


New upstream release, fixes FTBFS. (Closes: #943655)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943655

Bug#942708: marked as done (update pynacl for recent hypothesis version)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 12:21:17 +
with message-id 
and subject line Bug#942708: fixed in python-nacl 1.3.0-3
has caused the Debian Bug report #942708,
regarding update pynacl for recent hypothesis version
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.)


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

Package: src:python-nacl
Version: 1.3.0-2
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

update pynacl for recent hypothesis version 4.36, which from my point of view is 
needed for python3.8


patch at
http://launchpadlibrarian.net/447703567/python-nacl_1.3.0-2build1_1.3.0-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: python-nacl
Source-Version: 1.3.0-3

We believe that the bug you reported is fixed in the latest version of
python-nacl, 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.
Scott Kitterman  (supplier of updated python-nacl 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, 19 Nov 2019 06:57:57 -0500
Source: python-nacl
Architecture: source
Version: 1.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Closes: 942708
Changes:
 python-nacl (1.3.0-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * d/control: Fix wrong Vcs-*.
 .
   [ Scott Kitterman ]
   * Fix build with new hypothesis version (add d/p/480.patch from upstream)
 (Closes: #942708) - Thanks to Matthias Klose for providing the patch
   * Bump minimum hypothesis build-dep versions since after the patch, the old
 versions no longer work
   * Bump standards-version to 4.4.1 without further change
Checksums-Sha1:
 14de9d786ee0b15a90a83e51a3c5e36ec9f110de 2520 python-nacl_1.3.0-3.dsc
 51ff56b5ce9c4c61d60f78efb67e28ac648a0ba2 40912 
python-nacl_1.3.0-3.debian.tar.xz
 85b23e7744391f37f27b1cdb6b338f43284a0609 7361 
python-nacl_1.3.0-3_source.buildinfo
Checksums-Sha256:
 f4f478859a44e09c6f57b1be045c5a5503bb513ce6782c6319f28e52a8f91ba0 2520 
python-nacl_1.3.0-3.dsc
 74c2883adb7a07ae5dc2942b857a44f5670e63479a756c660a59c086b2bc2487 40912 
python-nacl_1.3.0-3.debian.tar.xz
 8765a462cb36fc915d385ad0d89281055ce672b609c691f587ea9bf700f601e1 7361 
python-nacl_1.3.0-3_source.buildinfo
Files:
 ac42d6d3213d2ff5e73fecd12106d9d0 2520 python optional python-nacl_1.3.0-3.dsc
 df1b828f8664d8e09a62bedfaeccd8c1 40912 python optional 
python-nacl_1.3.0-3.debian.tar.xz
 75c51b8f2fd45af9c8ed0f4d217fc6ea 7361 python optional 
python-nacl_1.3.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl3T2fgACgkQeNfe+5rV
mvHLZA/+Izu8mHd8CQqp+AvHgIA2lVEsbWO9QOS1dXhyicjzmRiVTC+hC1MVwtty
MySCl+SAl7nZQpZuJ3Cr1X74NeuIntaLwvNggC0JxB8lgw0ZDLLHas9++2p+rLv7
C2nyTx6miyBlkX/nFfNeEYdz0oKlrUSYVqBM0KvUHUwWBXYEY01lMd9PJbMWVHJT
iuSWQcGCfOdBGBbRZzgqYLuQtG1gSlz5/vrubRukL9PNxO9+JT254E9pnj7N9Pbt
HI+Pl2J83gnHDLhw18MVplMa4Lz+QGfl7DRO3c4veyVeRjJWVMA4m0uw8V/l9PRQ
ktuyCShlmtWpNnKradyLJDEL3xLRI3jBP0u0SNcH3ykNCQIgAemSF8T0lVVdKlD3
AtHyH5VKmVNGJmM5AYR4rItNVOrO2fljYE4/VCjSOejzchOj7OXZMw5LdBFnIJ/P
fxhSnzY64nMhPd6orjnJ8fYUn0XGdTB50CZ0miby/7SKo4PELZusT2ZyPPRlUSHF
RcAUUlgOdpospKJxqiYyICxCKlteRaUDDayKLKNsVPPNhlC4ev62PmuMAtjFlxiH
AtNQ+uw1pqhc7JOMxW/MTq2upP0tw5OsfV2tlTrMcsHmZpeFfhknPwy89zPtV7f+
1nKWVZ0W72DWK2QMilas4X/Of/xzzQAUaG7rb390ha9IoT44SVg=
=sooZ
-END PGP SIGNATURE End Message ---

Bug#942693: marked as done (new upstream version needed to support python 3.8)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 11:52:04 +
with message-id 
and subject line Bug#942693: fixed in python-hypothesis 4.36.2-1
has caused the Debian Bug report #942693,
regarding new upstream version needed to support python 3.8
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.)


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

Package: src:python-hypothesis
Version: 3.71.11-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

python-hypothesis, python-pluggy and python-importlib-metadata need new upstream 
versions to support python 3.8.  I checked that a combination of


  python-hypothesis 4.36.2
  python-pluggy 0.13.0
  python-importlib-metadata 0.23

works together.  the most recent python-hypothesis 4.41.x requires a new 
python-attrs, that's why I went with 4.36.2.  Please update to these new versions.
--- End Message ---
--- Begin Message ---
Source: python-hypothesis
Source-Version: 4.36.2-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Nov 2019 11:54:08 +0100
Source: python-hypothesis
Architecture: source
Version: 4.36.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Nicolas Dandrimont 
Closes: 942693
Changes:
 python-hypothesis (4.36.2-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Nicolas Dandrimont ]
   * New upstream release (Closes: #942693)
   * Drop remote reference to image in documentation
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
Checksums-Sha1:
 6fe5edd5a07865ad2448bf8dcf6184afcf2cf90a 2776 python-hypothesis_4.36.2-1.dsc
 9cd231a6253d2dad00f0dc6ae9c789914906e0df 1318229 
python-hypothesis_4.36.2.orig.tar.gz
 8b4a38bb8a49bf159af23bebb176c145e190e192 9948 
python-hypothesis_4.36.2-1.debian.tar.xz
 3840e11b35977925d3ac4e4b0bfc450649cf3f51 8995 
python-hypothesis_4.36.2-1_amd64.buildinfo
Checksums-Sha256:
 e48db44ea1a4e1e40e2735a31fe3a5766259e29d193b31a69651e3b7b2ee2744 2776 
python-hypothesis_4.36.2-1.dsc
 8c044d415391745c5e3fc1483395d398ec263ddea20b283ca6ff3fddc222e026 1318229 
python-hypothesis_4.36.2.orig.tar.gz
 07b5006a84c8c0666d4ae6605829ba2f638b94a6ab3f5d33dab896767c9fb92e 9948 
python-hypothesis_4.36.2-1.debian.tar.xz
 36f5e34240526a8717c197aed822604f1bc3b2f00a5e3a7d2aed2d1644be7d17 8995 
python-hypothesis_4.36.2-1_amd64.buildinfo
Files:
 95bb8c09340fd44bc1b10eff4c79eef5 2776 python optional 
python-hypothesis_4.36.2-1.dsc
 7774efa69d77bf8f033a7542072646b5 1318229 python optional 
python-hypothesis_4.36.2.orig.tar.gz
 3c08acb81f61009a3c9ff34da132cf23 9948 python optional 
python-hypothesis_4.36.2-1.debian.tar.xz
 12e15155f42ad609752ab364385cde07 8995 python optional 
python-hypothesis_4.36.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEMpGQCo4g4u9D+PnY3K6QUi5xIr8FAl3T0iwRHG9sYXNkQGRl
Ymlhbi5vcmcACgkQ3K6QUi5xIr/Rng//Y30TPNDQ+SxQSgXBEwWPv5tTi1bfCYP9
iAO4GjJ8Z+tWyqfqNlXsDjBMuaRBI3saFryCLqbWf8b8b0F2QfuZSO7enzeOxlj2
DA9M04pIcmZnEfG49HLJ+rkQ5BDOr8+lssd/aMZ4dAblgkRNgT13p0lnzEwhJaf2
X0zupvMMvmnrAXmWZmzjtevimcEgRFZX9juP2gsJBPA6/AjRHpGJ+IuF0eEVqkrO
cnLnDngheLl6XjBDzSh3x5pHiujPDYBeoOiV9oOznTQ6FW4bY09o4xQ5hOvCADZ/
cl5dAW1sqUVwjZZi+ResrDloX/5LXW7u09+ATp4JiMauejRA+MzVyQmYlpnff619
lEo4TwHiWlBmgX08yan6IVOuC3SI/E+xGV5/qWHGgGk/H8PnfJX3T1sBqWPoo1Yv
/OXth+ZJ2dkQqmSkRoadxRqRqvk7e225WiWGxh3EaPyGIurywICRmPKlaqjy6G8Z
Lh0/hQR1sidbC3njHfSa94xWSBmEDsH8NeuFb6amVFNhzRSgc4I6EJVRMYNW7p/y
NxIBy744lTWGDPdOeDK3nTj7xDA7JPrvFErwq1OC7uvUiOscs/D8rCxw6hUy4cC5
opZc8w+C5ua3EsCxZ9/Aijb3YwOjvhtA7OOE/Z7nQ1358y/S40ooyB1tVyNgZZUX
ZPbE4aFapsQ=
=fK90
-END PGP SIGNATURE End Message ---

Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26

[David Bremner]

Agustin Martin  writes:

>
> I have been thinking about this and I see a problem with the elpa way of
> handling prefix auto-mode-alist associations. They go to a file that is not
> a conffile. So, if that kind of conflicts appear it is not as easy to
> handle as just editing one of the conffiles and commenting the undesired
> association.
>

I guess it should still be possible to override these settings,
definitely for an individual user, or probably also system-wide. But
Debian should really not ship packages with conflicts, whatever
mechanism of setting variables is used.

d

Bug#943386: marked as done (libxml2: please update tests for python->python2 move)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 11:34:54 +
with message-id 
and subject line Bug#943386: fixed in libxml2 2.9.4+dfsg1-8
has caused the Debian Bug report #943386,
regarding libxml2: please update tests for python->python2 move
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.)


-- 
943386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxml2
Version: 2.9.4+dfsg1-7
tags: patch

Hello, in this commit [1] python stop being a thing, while python2 becomes 
reality

Please update the tests to run python2 interpreter directly

--- libxml2-2.9.4+dfsg1/debian/tests/python 2018-01-02 08:59:03.0 
+0100
+++ libxml2-2.9.4+dfsg1/debian/tests/python 2019-10-24 11:06:13.0 
+0200
@@ -1,6 +1,6 @@
 #!/bin/sh
 
-python 

Bug#942693: marked as pending in python-hypothesis

[Nicolas Dandrimont]

Control: tag -1 pending

Hello,

Bug #942693 in python-hypothesis 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/python-hypothesis/commit/08097371a21187d3b12b95cadbd526885c458d0c


New upstream release (Closes: #942693)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/942693

Processed: Bug#942693 marked as pending in python-hypothesis

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #942693 [src:python-hypothesis] new upstream version needed to support 
python 3.8
Added tag(s) pending.

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

Bug#943386: marked as pending in libxml2

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

Bug #943386 in libxml2 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/xml-sgml-team/libxml2/commit/46442f7d4f9084197e84f6b240139e55b0adcdfe


Fix autopkgtest: use `python2` instead of `python` and actually run the 
`python3` test.  Closes: #943386

Signed-off-by: Mattia Rizzolo 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943386

Processed: Bug#943386 marked as pending in libxml2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #943386 [src:libxml2] libxml2: please update tests for python->python2 move
Ignoring request to alter tags of bug #943386 to the same tags previously set

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

Bug#943386: marked as pending in libxml2

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

Bug #943386 in libxml2 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/xml-sgml-team/libxml2/commit/46442f7d4f9084197e84f6b240139e55b0adcdfe


Fix autopkgtest: use `python2` instead of `python` and actually run the 
`python3` test.  Closes: #943386

Signed-off-by: Mattia Rizzolo 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943386

Processed: Bug#943386 marked as pending in libxml2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #943386 [src:libxml2] libxml2: please update tests for python->python2 move
Added tag(s) pending.

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

Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26

[Agustin Martin]

On Mon, Nov 18, 2019 at 07:28:45AM -0400, David Bremner wrote:
> Dima Kogan  writes:
> 
> > Thanks for the patches, Agustin. I just tried it out. Works for the most
> > part. One thing that doesn't work for me is (gnuplot-mode) being
> > executed when opening a .gp file. You added this to the package, and the
> > dh-elpa machinery is creating the appropriate file:
> >
> >   /etc/emacs/site-start.d/50elpa-gnuplot-mode.el
> >
> > I don't think this is being evaluated, however. Is it working for you?
> 
> That's not loaded by elpa packages.
> 
> The general approach is to add an autoload cookie to set
> auto-mode-alist. See "HINTS" in dh_elpa(1). Of course the usual cautions
> about auto-mode-alist apply, in particular there's no nice way to resolve
> conflicts with other packages (e.g. pari-gp) that might want to use the
> same suffix.

Hi,

I have been thinking about this and I see a problem with the elpa way of
handling prefix auto-mode-alist associations. They go to a file that is not
a conffile. So, if that kind of conflicts appear it is not as easy to
handle as just editing one of the conffiles and commenting the undesired
association.

Regards,

-- 
Agustin

Bug#935759: marked as done (postgresql-9.4: fails to purge: RET=10 postgresql-9.4/postrm_purge_data doesn't exist)

[Debian Bug Tracking System]

Your message dated Tue, 19 Nov 2019 11:59:34 +0100
with message-id <20191119105934.ga22...@msg.df7cb.de>
and subject line Re: Bug#935759: postgresql-9.4: fails to purge: RET=10 
postgresql-9.4/postrm_purge_data doesn't exist
has caused the Debian Bug report #935759,
regarding postgresql-9.4: fails to purge: RET=10 
postgresql-9.4/postrm_purge_data doesn't exist
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.)


-- 
935759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-9.4
Version: 9.4.24-0+deb8u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to purge.
According to policy 7.2 you cannot rely on the depends being available
during purge, only the essential packages are available for sure.

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

  Removing postgresql-9.4 (9.4.24-0+deb8u1) ...
  Purging configuration files for postgresql-9.4 (9.4.24-0+deb8u1) ...
  + set -e
  + VERSION=9.4
  + [ purge = purge ]
  + [ -d /etc/postgresql/9.4 ]
  + ls /etc/postgresql/9.4
  + [ main ]
  + [ -e /usr/share/debconf/confmodule ]
  + . /usr/share/debconf/confmodule
  + [ !  ]
  + PERL_DL_NONLAZY=1
  + export PERL_DL_NONLAZY
  + [  ]
  + exec /usr/share/debconf/frontend /var/lib/dpkg/info/postgresql-9.4.postrm 
purge
  + set -e
  + VERSION=9.4
  + [ purge = purge ]
  + [ -d /etc/postgresql/9.4 ]
  + ls /etc/postgresql/9.4
  + [ main ]
  + [ -e /usr/share/debconf/confmodule ]
  + . /usr/share/debconf/confmodule
  + [ ! 1 ]
  + [ -z  ]
  + exec
  + [  ]
  + exec
  + DEBCONF_REDIR=1
  + export DEBCONF_REDIR
  + purge_package
  + [ -e /usr/share/debconf/confmodule ]
  + db_set postgresql-9.4/postrm_purge_data true
  + _db_cmd SET postgresql-9.4/postrm_purge_data true
  + _db_internal_IFS=

  + IFS=
  + printf %s\n SET postgresql-9.4/postrm_purge_data true
  + IFS=

  + IFS=
   read -r _db_internal_line
  + RET=10 postgresql-9.4/postrm_purge_data doesn't exist
  + return 10
  dpkg: error processing package postgresql-9.4 (--purge):
   subprocess installed post-removal script returned error exit status 10
  Errors were encountered while processing:
   postgresql-9.4

The template does not get registered because postinst does not load
/usr/share/debconf/confmodule.
In buster this is done by /usr/share/postgresql-common/maintscripts-functions
but in jessie the postinst has to do it manually

cheers,

Andreas


postgresql-9.4_9.4.24-0+deb8u1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 9.4.25-0+deb8u1

Re: Andreas Beckmann 2019-08-26 
<3ce894f6-d6cb-7959-73ee-1e406212d...@debian.org>
> At least for jessie the templates have to be registered during
> preinst/postinst.

Thanks, I put that into the postinst now.

Unfortunately, the jessie-security upload didn't close this bug, so
I'm doing that manually now.

commit e179187ee3f0ea240280bdc4e420f20f04a206bd (tag: debian/9.4.25-0+deb8u1, 
origin/9.4-jessie, 9.4-jessie)
Author: Christoph Berg 
Date:   Mon Nov 18 16:20:38 2019 +0100

New upstream version.

* New upstream version. This is the next-to-last release of the 9.4 series.
  Please upgrade to a newer PostgreSQL major version.
* Register debconf templates in postinst. (Closes: #935759)

diff --git a/debian/changelog b/debian/changelog
index a7dd1b6..e919aa6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+postgresql-9.4 (9.4.25-0+deb8u1) jessie-security; urgency=medium
+
+  * New upstream version. This is the next-to-last release of the 9.4 series.
+Please upgrade to a newer PostgreSQL major version.
+  * Register debconf templates in postinst. (Closes: #935759)
+
+ -- Christoph Berg   Mon, 18 Nov 2019 11:49:49 +0100
+
 postgresql-9.4 (9.4.24-0+deb8u1) jessie-security; urgency=medium

   * New upstream security release.
diff --git a/debian/postgresql-9.4.postinst b/debian/postgresql-9.4.postinst
index 266be11..1a6f6bc 100644
--- a/debian/postgresql-9.4.postinst
+++ b/debian/postgresql-9.4.postinst
@@ -8,6 +8,12 @@ if [ "$1" = configure ]; then
 . /usr/share/postgresql-common/maintscripts-functions

 configure_version $VERSION "$2"
+
+# jessie's debconf requires registering templates in preinst/postinst, 
even if we use them in the postrm only
+if [ -e /usr/share/debconf/confmodule ]; then
+. /usr/share/debconf/confmodule
+db_stop
+fi
 fi

 #DEBHELPER#


Christoph--- End Message ---

Processed: found 945011 in 0.8.0.2-1, found 945010 in 5.8.0.0-1, tagging 944705, found 945012 in 0.4.8-8 ...

[Debian Bug Tracking System]

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

> found 945011 0.8.0.2-1
Bug #945011 [src:haskell-cabal-helper] haskell-cabal-helper: Removal notice: 
unused Haskell library
Marked as found in versions haskell-cabal-helper/0.8.0.2-1.
> found 945010 5.8.0.0-1
Bug #945010 [src:ghc-mod] ghc-mod: Removal notice: unmaintained
Marked as found in versions ghc-mod/5.8.0.0-1.
> tags 944705 + sid bullseye
Bug #944705 [python3-mako] alembic: failing tests with python3.8
Added tag(s) bullseye and sid.
> found 945012 0.4.8-8
Bug #945012 [src:haskell-network-protocol-xmpp] haskell-network-protocol-xmpp: 
Removal notice: unmaintained
Marked as found in versions haskell-network-protocol-xmpp/0.4.8-8.
> tags 945012 + sid bullseye
Bug #945012 [src:haskell-network-protocol-xmpp] haskell-network-protocol-xmpp: 
Removal notice: unmaintained
Added tag(s) sid and bullseye.
> found 945013 0.2.2-9
Bug #945013 [src:haskell-gnuidn] haskell-gnuidn: Removal notice: unmaintained
Marked as found in versions haskell-gnuidn/0.2.2-9.
> tags 943386 + sid bullseye experimental
Bug #943386 [src:libxml2] libxml2: please update tests for python->python2 move
Added tag(s) experimental, bullseye, and sid.
> thanks
Stopping processing here.

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

Processed: 943763

[Debian Bug Tracking System]

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

> notfound 943763 jaraco.itertools/2.0.1-4
Bug #943763 {Done: JCF Ploemen (jcfp) } 
[python3-jaraco.itertools,python3-jaraco.functools] 
python3-jaraco.itertools,python3-jaraco.functools: both ship 
/usr/lib/python3/dist-packages/jaraco/__init__.py
No longer marked as found in versions jaraco.itertools/2.0.1-4.
>
End of message, stopping processing here.

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

Bug#942101: python-msrest build accesses the network during the build

[Luca Boccassi]

On Wed, 13 Nov 2019 14:45:44 + Luca Boccassi <
bl...@debian.org
> wrote:
> Control: tags -1 patch
> 
> On Thu, 10 Oct 2019 14:01:46 +0200 Matthias Klose <
> 
d...@debian.org

> > wrote:
> > Package: src:python-msrest
> > Version: 0.6.1-1
> > Severity: serious
> > Tags: sid bullseye
> > 
> > according to
> > 
> 
https://launchpadlibrarian.net/441507516/buildlog_ubuntu-eoan-amd64.python-msrest_0.6.1-1_BUILDING.txt.gz

> 
> > 
> > the tests access some infrastructure.  The build must not rely on
the
> network, 
> > the autopkg tests can.  Usually the Debian buildds don't check for
> network access.
> 
> Dear Maintainers,
> 
> I have opened an MR on Salsa to skip those tests at build time:
> 
> 
https://salsa.debian.org/python-team/modules/python-msrest/merge_requests/1

Dear Maintainers,

The autoremoval affects packages I maintain, so unless there are any
objections I'll upload an NMU to DELAYED/7 later today with the patch
from the MR.

Thanks!

-- 
Kind regards,
Luca Boccassi


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

Bug#944242: Test issues with BioPython 1.75

[Peter Cock]

On Tue, Nov 19, 2019 at 9:43 AM Andreas Tille  wrote:
>
> Hi Peter,
>
> I'd like to give you credit as the fastest upstream answering a
> question. ;-)  Thanks a lot for it!

Lucky timing.

> On Tue, Nov 19, 2019 at 09:17:17AM +, Peter Cock wrote:
> > Curious - do you have the Python 2.7 version and build details?
>
> I've attached the full build log.

Thanks - I'v had a quick look. There must be something different to
how the build or installed directories are setup - our TravisCI tests
do not pick up the C modules at all.

> > Missing docstrings are unfortunate (and in this case they are in C
> > code which is a bit different), but ultimately this is harmless. What
> > puzzles me is what has triggered this, that we fail to see it on our
> > own testing.
>
> Hmmm, you say its harmless but its breaking the build of the Debian
> package anyway.  So it would be good to have some means against it.

I mean I would not worry about this particular test failing - and would
consider whitelisting this test acceptable.

Without yet being able to reproduce this and test it, does this work?:

https://github.com/peterjc/biopython/commit/5af680b5043c9f160a19e4bb0deab0ccc271280d

If not, we could explicitly exclude the C modules from testing, maybe here:

https://github.com/biopython/biopython/blob/biopython-175/Tests/run_tests.py#L151

i.e. Add "Bio/KDTree/_CKDTree" etc to EXCLUDE_DOCTEST_MODULES
(with the proviso that to date I've only used this with Python modules,
you might need to include the .so extension?)

> Since you are asking about the 2.7 version:  We need to get rid of
> Python2 as soon as all reverse depends of biopython are ported to
> Python3 (or removed from Debian).  This might take some time but if
> we could move this kind of doc string generation to be done by Python3
> this would be some step in the right direction.

Do you have a list of things still depending on Biopython & Python 2.7
handy? We're discussing when exactly to drop Python 2.7 support -
with a final compatible release in December 2019 or January 2020
looking most likely.

Peter

Bug#944844: Bug#944990: patching llvm-8 for julia 1.3.0 (upcoming)

[Sylvestre Ledru]

Le 19/11/2019 à 10:48, Stéphane Glondu a écrit :

On Mon Nov 18 12:54:44 GMT 2019, Sylvestre Ledru wrote:

Sure, I am just setting expectations :)
I am not planning to spend much time on -8.


If so, why is llvm-defaults still pointing at -8?

Because I didn't start the work for the transition.


Are you planning to fix #944844

I just ask for a give back.

S

Bug#944844: FTBFS on mips* (when building target LLVMAnalysis)

[Sylvestre Ledru]

Le 16/11/2019 à 09:00, Stéphane Glondu a écrit :

Package: src:llvm-toolchain-8
Version: 1:8.0.1-4
Severity: serious
Tags: ftbfs
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.08-transition

Dear Maintainer,

llvm-toolchain-8 FTBFS on mips*:

   
https://buildd.debian.org/status/package.php?p=llvm-toolchain-8=unstable

This failure blocks the ocaml transition.


The error is:
../../../bin/llvm-tblgen(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamE+0x44)[0x1202c6564]
Stack dump:
0.	Program arguments: ../../../bin/llvm-tblgen -gen-global-isel -I /<>/lib/Target/AArch64 -I /<>/include -I /<>/lib/Target /<>/lib/Target/AArch64/AArch64.td -o 
/<>/build-llvm/tools/clang/stage2-bins/lib/Target/AArch64/AArch64GenGlobalISel.inc

Bus error
Not sure what it means

I should just remove ocaml support to unblock the transition.


Sylvestre

Bug#944844: Bug#944990: patching llvm-8 for julia 1.3.0 (upcoming)

[Stéphane Glondu]

On Mon Nov 18 12:54:44 GMT 2019, Sylvestre Ledru wrote:
> Sure, I am just setting expectations :)
> I am not planning to spend much time on -8.

If so, why is llvm-defaults still pointing at -8?

Are you planning to fix #944844?


Cheers,

-- 
Stéphane

Bug#944242: Test issues with BioPython 1.75

[Andreas Tille]

Hi Peter,

I'd like to give you credit as the fastest upstream answering a
question. ;-)  Thanks a lot for it!

On Tue, Nov 19, 2019 at 09:17:17AM +, Peter Cock wrote:
> Curious - do you have the Python 2.7 version and build details?

I've attached the full build log.
 
> Missing docstrings are unfortunate (and in this case they are in C
> code which is a bit different), but ultimately this is harmless. What
> puzzles me is what has triggered this, that we fail to see it on our
> own testing.

Hmmm, you say its harmless but its breaking the build of the Debian
package anyway.  So it would be good to have some means against it.
Since you are asking about the 2.7 version:  We need to get rid of
Python2 as soon as all reverse depends of biopython are ported to
Python3 (or removed from Debian).  This might take some time but if
we could move this kind of doc string generation to be done by Python3
this would be some step in the right direction.
 
> As an aside, for Python 3.8 you would ideally include this, it didn't
> get in the tag or tar-ball, but was in the Python 3.8 wheels:
> 
> https://github.com/biopython/biopython/commit/3b8e984e25bca84ea3cb56d8a1eb67006dcd26be

Pushed to the packaging git - thanks a lot for the hint.
 
Kind regards

  Andreas.
 
> On Tue, Nov 19, 2019 at 8:27 AM Andreas Tille  wrote:
> >
> > Hi,
> >
> > it seems that BioPython 1.75 has solved all issues with Python 3.8.
> > However, when trying to build the Debian package I get the following
> > issues in the Build-Time test suite:
> >
> > ...
> > ==
> > ERROR: Bio.KDTree._CKDTree
> > --
> > Traceback (most recent call last):
> >   File "run_tests.py", line 367, in runTest
> > optionflags=doctest.ELLIPSIS)
> >   File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
> > raise ValueError(module, "has no docstrings")
> > ValueError: ( > '/build/python-biopython-1.75+dfsg/.pybuild/cpython2_2.7/build/Bio/KDTree/_CKDTree.so'>,
> >  'has no docstrings')
> > ==
> > ERROR: Bio.Nexus.cnexus
> > --
> > Traceback (most recent call last):
> >   File "run_tests.py", line 367, in runTest
> > optionflags=doctest.ELLIPSIS)
> >   File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
> > raise ValueError(module, "has no docstrings")
> > ValueError: ( > '/build/python-biopython-1.75+dfsg/.pybuild/cpython2_2.7/build/Bio/Nexus/cnexus.so'>,
> >  'has no docstrings')
> > ==
> > ERROR: Bio.PDB.QCPSuperimposer.qcprot
> > --
> > Traceback (most recent call last):
> >   File "run_tests.py", line 367, in runTest
> > optionflags=doctest.ELLIPSIS)
> >   File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
> > raise ValueError(module, "has no docstrings")
> > ValueError: ( > '/build/python-biopython-1.75+dfsg/.pybuild/cpython2_2.7/build/Bio/PDB/QCPSuperimposer/qcprotmodule.so'>,
> >  'has no docstrings')
> > ==
> > ERROR: Bio.PDB.kdtrees
> > --
> > Traceback (most recent call last):
> >   File "run_tests.py", line 367, in runTest
> > optionflags=doctest.ELLIPSIS)
> >   File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
> > raise ValueError(module, "has no docstrings")
> > ValueError: ( > '/build/python-biopython-1.75+dfsg/.pybuild/cpython2_2.7/build/Bio/PDB/kdtrees.so'>,
> >  'has no docstrings')
> > --
> > Ran 519 tests in 287.024 seconds
> >
> > FAILED (failures = 4)
> > Skipping any tests requiring internet access
> > Python version: 2.7.17 (default, Oct 19 2019, 23:36:22)
> > [GCC 9.2.1 20191008]
> > ...
> >
> >
> > Any hint how to solve this?
> >
> > Greetings from Biohackathon
> >
> >  Andreas.
> >
> > --
> > http://fam-tille.de
> 
> ___
> 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


python-biopython_1.75+dfsg-1_amd64.build.xz
Description: application/xz

Bug#944242: Test issues with BioPython 1.75

[Peter Cock]

Curious - do you have the Python 2.7 version and build details?

Missing docstrings are unfortunate (and in this case they are in C
code which is a bit different), but ultimately this is harmless. What
puzzles me is what has triggered this, that we fail to see it on our
own testing.

As an aside, for Python 3.8 you would ideally include this, it didn't
get in the tag or tar-ball, but was in the Python 3.8 wheels:

https://github.com/biopython/biopython/commit/3b8e984e25bca84ea3cb56d8a1eb67006dcd26be

Regards,

Peter

On Tue, Nov 19, 2019 at 8:27 AM Andreas Tille  wrote:
>
> Hi,
>
> it seems that BioPython 1.75 has solved all issues with Python 3.8.
> However, when trying to build the Debian package I get the following
> issues in the Build-Time test suite:
>
> ...
> ==
> ERROR: Bio.KDTree._CKDTree
> --
> Traceback (most recent call last):
>   File "run_tests.py", line 367, in runTest
> optionflags=doctest.ELLIPSIS)
>   File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
> raise ValueError(module, "has no docstrings")
> ValueError: ( '/build/python-biopython-1.75+dfsg/.pybuild/cpython2_2.7/build/Bio/KDTree/_CKDTree.so'>,
>  'has no docstrings')
> ==
> ERROR: Bio.Nexus.cnexus
> --
> Traceback (most recent call last):
>   File "run_tests.py", line 367, in runTest
> optionflags=doctest.ELLIPSIS)
>   File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
> raise ValueError(module, "has no docstrings")
> ValueError: ( '/build/python-biopython-1.75+dfsg/.pybuild/cpython2_2.7/build/Bio/Nexus/cnexus.so'>,
>  'has no docstrings')
> ==
> ERROR: Bio.PDB.QCPSuperimposer.qcprot
> --
> Traceback (most recent call last):
>   File "run_tests.py", line 367, in runTest
> optionflags=doctest.ELLIPSIS)
>   File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
> raise ValueError(module, "has no docstrings")
> ValueError: ( '/build/python-biopython-1.75+dfsg/.pybuild/cpython2_2.7/build/Bio/PDB/QCPSuperimposer/qcprotmodule.so'>,
>  'has no docstrings')
> ==
> ERROR: Bio.PDB.kdtrees
> --
> Traceback (most recent call last):
>   File "run_tests.py", line 367, in runTest
> optionflags=doctest.ELLIPSIS)
>   File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
> raise ValueError(module, "has no docstrings")
> ValueError: ( '/build/python-biopython-1.75+dfsg/.pybuild/cpython2_2.7/build/Bio/PDB/kdtrees.so'>,
>  'has no docstrings')
> --
> Ran 519 tests in 287.024 seconds
>
> FAILED (failures = 4)
> Skipping any tests requiring internet access
> Python version: 2.7.17 (default, Oct 19 2019, 23:36:22)
> [GCC 9.2.1 20191008]
> ...
>
>
> Any hint how to solve this?
>
> Greetings from Biohackathon
>
>  Andreas.
>
> --
> http://fam-tille.de

Processed: Different Build issue reported to Upstream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #937657 [src:python-colormap] python-colormap: Python2 removal in 
sid/bullseye
Added tag(s) upstream.
> forwarded -1 https://github.com/cokelaer/colormap/issues/11
Bug #937657 [src:python-colormap] python-colormap: Python2 removal in 
sid/bullseye
Set Bug forwarded-to-address to 
'https://github.com/cokelaer/colormap/issues/11'.

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

Bug#937657: Different Build issue reported to Upstream

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/cokelaer/colormap/issues/11

There is some remaining build time issue which I reported upstream.

...
==
ERROR: test_get_cmap.test_get_cmap
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/python-colormap-1.0.2/.pybuild/cpython3_3.8_colormap/build/test/test_get_cmap.py",
 line 7, in test_get_cmap
get_cmap("nipy_spectral")
  File 
"/build/python-colormap-1.0.2/.pybuild/cpython3_3.8_colormap/build/colormap/get_cmap.py",
 line 57, in cmap_builder
raise ValueError(txt)
ValueError: name provided nipy_spectral is not recognised. 
 valid name can be found in colormap.colormap_names

--
Ran 13 tests in 0.168s

FAILED (errors=1)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd 
/build/python-colormap-1.0.2/.pybuild/cpython3_3.8_colormap/build; python3.8 -m 
nose -v test

Any help from Debian would be welcome anyway to speed up the Python3
migration.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#945064: unrardll needs a sourceful upload to support python3.8?

[Matthias Klose]

Package: src:unrardll
Version: 0.1.3-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

unrardll shows up in
https://release.debian.org/transitions/html/python3.8.html

but cannot be binNMUed because it's a contrib package b-d on a non-free package.
 Please do a sourceful upload to add support for Python 3.8.

Processed: raise severity for Python 3.8 issue

[Debian Bug Tracking System]

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

> severity 944774 serious
Bug #944774 [python3-gpg] Support python 3.8
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#944242: Test issues with BioPython 1.75

[Andreas Tille]

Hi,

it seems that BioPython 1.75 has solved all issues with Python 3.8.
However, when trying to build the Debian package I get the following
issues in the Build-Time test suite:

...
==
ERROR: Bio.KDTree._CKDTree
--
Traceback (most recent call last):
  File "run_tests.py", line 367, in runTest
optionflags=doctest.ELLIPSIS)
  File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
raise ValueError(module, "has no docstrings")
ValueError: (,
 'has no docstrings')
==
ERROR: Bio.Nexus.cnexus
--
Traceback (most recent call last):
  File "run_tests.py", line 367, in runTest
optionflags=doctest.ELLIPSIS)
  File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
raise ValueError(module, "has no docstrings")
ValueError: (,
 'has no docstrings')
==
ERROR: Bio.PDB.QCPSuperimposer.qcprot
--
Traceback (most recent call last):
  File "run_tests.py", line 367, in runTest
optionflags=doctest.ELLIPSIS)
  File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
raise ValueError(module, "has no docstrings")
ValueError: (,
 'has no docstrings')
==
ERROR: Bio.PDB.kdtrees
--
Traceback (most recent call last):
  File "run_tests.py", line 367, in runTest
optionflags=doctest.ELLIPSIS)
  File "/usr/lib/python2.7/doctest.py", line 2412, in DocTestSuite
raise ValueError(module, "has no docstrings")
ValueError: (,
 'has no docstrings')
--
Ran 519 tests in 287.024 seconds

FAILED (failures = 4)
Skipping any tests requiring internet access
Python version: 2.7.17 (default, Oct 19 2019, 23:36:22) 
[GCC 9.2.1 20191008]
...


Any hint how to solve this?

Greetings from Biohackathon

 Andreas.

-- 
http://fam-tille.de

Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5

[Michael Biebl]

Control: severity -1 normal
Control: retitle -1 udev aborts processing rules on failures

Am 19.11.19 um 02:18 schrieb Michael Biebl:
> Am 19.11.19 um 00:56 schrieb Klaumi Klingsporn:
>> That leaves me with the question: Why the hell on my
>> amd64-system (with i386 enabled only as
>> foreign-architecture) the i386 version of libinput-bin was 
>> installed?
> 
> I'm puzzled as well how so many users ended up with a non-native
> libinput-bin:i386. This is not good. Imho apt should be much more
> careful when installing non-native packages and prefer the native version.

I've submitted a change in 243-8 which allows non-native binaries to be
executed from udev rules. This should fix the issue for most/all
affected users.

I want to keep this bug report open though, because I think the new
behaviour in udev of aborting processing udev rules as soon as we hit an
error is to brittle. We should continue processing udev rules.
Let's hope I can convince upstream about this.

Downgrading the severity though, as this should no longer affect so many
users.

Michael

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #944675 [udev] udev: Keyboard and mouse not working in X.org with udev 243-5
Bug #944813 [udev] xserver-xorg-input-evdev: Keyboard and mouse don't work 
after X started
Bug #944838 [udev] xorg: after recent upgrade on two different machines, X no 
longer responds to kbd or mouse input
Severity set to 'normal' from 'grave'
Severity set to 'normal' from 'grave'
Severity set to 'normal' from 'grave'
> retitle -1 udev aborts processing rules on failures
Bug #944675 [udev] udev: Keyboard and mouse not working in X.org with udev 243-5
Bug #944813 [udev] xserver-xorg-input-evdev: Keyboard and mouse don't work 
after X started
Bug #944838 [udev] xorg: after recent upgrade on two different machines, X no 
longer responds to kbd or mouse input
Changed Bug title to 'udev aborts processing rules on failures' from 'udev: 
Keyboard and mouse not working in X.org with udev 243-5'.
Changed Bug title to 'udev aborts processing rules on failures' from 
'xserver-xorg-input-evdev: Keyboard and mouse don't work after X started'.
Changed Bug title to 'udev aborts processing rules on failures' from 'xorg: 
after recent upgrade on two different machines, X no longer responds to kbd or 
mouse input'.

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

Bug#944714: moonshot-trust-router ftbfs during rebuilds for libevent 2.1.7

[peter green]

Tags 944714 +patch
Thanks.

The easy fix here is to remove -Werror, in the long term of course migration to 
a non-deprecated type should be considered but that is IMO an issue for 
upstream not Debian.

I have tested said change and uploaded to raspbian, a debdiff sould appear soon 
at https://debdiffs.raspbian.org/main/m/moonshot-trust-router/ No intent to NMU 
in Debian.

Processed: re: moonshot-trust-router ftbfs during rebuilds for libevent 2.1.7

[Debian Bug Tracking System]

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

> Tags 944714 +patch
Bug #944714 [src:moonshot-trust-router] moonshot-trust-router ftbfs during 
rebuilds for libevent 2.1.7
Added tag(s) patch.
> Thanks.
Stopping processing here.

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