Bug#937671: marked as done (python-crypto: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 02 Apr 2020 04:04:09 +
with message-id 
and subject line Bug#937671: fixed in python-crypto 2.6.1-13.1
has caused the Debian Bug report #937671,
regarding python-crypto: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-crypto

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-crypto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 23:40:18 -0400
Source: python-crypto
Architecture: source
Version: 2.6.1-13.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Ramacher 
Changed-By: Sandro Tosi 
Closes: 937671
Changes:
 python-crypto (2.6.1-13.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937671
Checksums-Sha1:
 a724e3d79e541a2af3aad05469f7989661f32347 2372 python-crypto_2.6.1-13.1.dsc
 521a08463c0b5e7f28cf3a4eeda8fec2e86d36df 24404 
python-crypto_2.6.1-13.1.debian.tar.xz
 f579defcb27590aa0404baba5055c55414f44869 8736 
python-crypto_2.6.1-13.1_amd64.buildinfo
Checksums-Sha256:
 6894661c80688666bbf84ce4075cc5400c0b842f5987aa4cf449ecd63dc3b1e2 2372 
python-crypto_2.6.1-13.1.dsc
 4d56d2c62f5f0ce9b8a7f60d0f14252c3504265e205b654443815c172872b3de 24404 
python-crypto_2.6.1-13.1.debian.tar.xz
 1dec8f43a4721e6756f7b9b1209967248750d8ba9b3b472e34aa6423eedbe6de 8736 

Bug#937643: marked as done (python-characteristic: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 02 Apr 2020 03:48:41 +
with message-id 
and subject line Bug#937643: fixed in python-characteristic 14.3.0-7
has caused the Debian Bug report #937643,
regarding python-characteristic: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-characteristic

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-characteristic 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 23:24:47 -0400
Source: python-characteristic
Architecture: source
Version: 14.3.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sandro Tosi 
Closes: 937643
Changes:
 python-characteristic (14.3.0-7) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937643
Checksums-Sha1:
 0c4d90e79a58cb90073d0a2ed0d8b8df706a50df 2015 
python-characteristic_14.3.0-7.dsc
 78b9528c38d92f85c0a14a82caf1e7f0282abda6 2920 
python-characteristic_14.3.0-7.debian.tar.xz
 87f964b6cc4cb05d0b21ed760c1ae5c2e8c4cee0 8759 
python-characteristic_14.3.0-7_amd64.buildinfo
Checksums-Sha256:
 4a7fdf3fc64d08a0d21a4a8ed69cb326847d41733d57bb20d91715def85dbcbc 2015 
python-characteristic_14.3.0-7.dsc
 7f0e1950d5f8da704866ff5268f795b8c0a3e58919d5c87931a3f43bb8633d25 2920 
python-characteristic_14.3.0-7.debian.tar.xz
 

Bug#936329: marked as done (constantly: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 02 Apr 2020 03:48:24 +
with message-id 
and subject line Bug#936329: fixed in constantly 15.1.0-2
has caused the Debian Bug report #936329,
regarding constantly: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:constantly

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated constantly package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 23:34:12 -0400
Source: constantly
Architecture: source
Version: 15.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 936329
Changes:
 constantly (15.1.0-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
   * d/control: Remove trailing whitespaces
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #936329
   * Set DPMT to Maintainer, Free to Uploaders
Checksums-Sha1:
 30834594e62c0cbd8a8fa05168b877f77164f9e3 2032 constantly_15.1.0-2.dsc
 b905b08c9be3c6e1a308c0b62e1a56305fc291f8 2612 constantly_15.1.0-2.debian.tar.xz
 7dbd90a658d4d43e1c45d28eff49289478c11e38 6490 
constantly_15.1.0-2_source.buildinfo
Checksums-Sha256:
 

Bug#952131: marked as done (pyhamcrest: FTBFS: build-dependency not installable: python-pytest-cov)

[Debian Bug Tracking System]

Your message dated Thu, 02 Apr 2020 03:48:36 +
with message-id 
and subject line Bug#952131: fixed in pyhamcrest 1.9.0-3
has caused the Debian Bug report #952131,
regarding pyhamcrest: FTBFS: build-dependency not installable: python-pytest-cov
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.)


-- 
952131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyhamcrest
Version: 1.9.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), dh-python, python-all, 
> python-hypothesis, python-mock, python-pytest-cov, python-setuptools, 
> python-six, python3-all, python3-hypothesis, python3-mock, 
> python3-pytest-cov, python3-setuptools, python3-six, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), dh-python, python-all, 
> python-hypothesis, python-mock, python-pytest-cov, python-setuptools, 
> python-six, python3-all, python3-hypothesis, python3-mock, 
> python3-pytest-cov, python3-setuptools, python3-six, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [433 B]
> Get:5 copy:/<>/apt_archive ./ Packages [518 B]
> Fetched 1908 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: python-pytest-cov but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/pyhamcrest_1.9.0-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: pyhamcrest
Source-Version: 1.9.0-3
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyhamcrest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 23:29:39 -0400
Source: pyhamcrest
Architecture: source
Version: 1.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: David Villa Alises 
Changed-By: Sandro Tosi 
Closes: 937456 952131
Changes:
 pyhamcrest (1.9.0-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937456, #952131
Checksums-Sha1:
 94786ff1943a1353ad4fb1d05ef5c205eb6dcc7c 2104 pyhamcrest_1.9.0-3.dsc
 1ca1781be13ff50e3f76094552513e5b0a0ca428 5588 

Bug#937456: marked as done (pyhamcrest: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 02 Apr 2020 03:48:35 +
with message-id 
and subject line Bug#937456: fixed in pyhamcrest 1.9.0-3
has caused the Debian Bug report #937456,
regarding pyhamcrest: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pyhamcrest

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pyhamcrest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 23:29:39 -0400
Source: pyhamcrest
Architecture: source
Version: 1.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: David Villa Alises 
Changed-By: Sandro Tosi 
Closes: 937456 952131
Changes:
 pyhamcrest (1.9.0-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937456, #952131
Checksums-Sha1:
 94786ff1943a1353ad4fb1d05ef5c205eb6dcc7c 2104 pyhamcrest_1.9.0-3.dsc
 1ca1781be13ff50e3f76094552513e5b0a0ca428 5588 pyhamcrest_1.9.0-3.debian.tar.xz
 334480029c5e8ebad69296fe037c9640f7e737e2 7400 
pyhamcrest_1.9.0-3_source.buildinfo
Checksums-Sha256:
 6437235b7096de7f98c19180115703c7a4821de10ef6549224addaf75a3a5835 2104 
pyhamcrest_1.9.0-3.dsc
 9c467de864636fe70fd2aa5102b0ee69cb200058d4824a9f09b0a76e3e3ebe6b 5588 
pyhamcrest_1.9.0-3.debian.tar.xz
 e8242f3f5b7c1553c93bb25ff2390700fd2614816f94ed7e88d2f69b0067c1ec 7400 
pyhamcrest_1.9.0-3_source.buildinfo
Files:
 056cc5bb36af72f290ddb57a0f239488 2104 

Bug#937671: python-crypto: diff for NMU version 2.6.1-13.1

[Sandro Tosi]

Control: tags 937671 + patch


Dear maintainer,

I've prepared an NMU for python-crypto (versioned as 2.6.1-13.1). The diff
is attached to this message.

Regards.

diff -Nru python-crypto-2.6.1/debian/changelog python-crypto-2.6.1/debian/changelog
--- python-crypto-2.6.1/debian/changelog	2019-11-16 04:46:30.0 -0500
+++ python-crypto-2.6.1/debian/changelog	2020-04-01 23:40:18.0 -0400
@@ -1,3 +1,10 @@
+python-crypto (2.6.1-13.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937671
+
+ -- Sandro Tosi   Wed, 01 Apr 2020 23:40:18 -0400
+
 python-crypto (2.6.1-13) unstable; urgency=medium
 
   [ Sebastian Ramacher ]
diff -Nru python-crypto-2.6.1/debian/control python-crypto-2.6.1/debian/control
--- python-crypto-2.6.1/debian/control	2019-10-22 15:21:34.0 -0400
+++ python-crypto-2.6.1/debian/control	2020-04-01 23:36:36.0 -0400
@@ -6,8 +6,6 @@
  debhelper-compat (= 12),
  dh-python,
  libgmp-dev,
- python-all-dbg,
- python-all-dev,
  python3-all-dbg,
  python3-all-dev (>= 3.3.2-5~)
 Standards-Version: 4.4.1
@@ -16,42 +14,6 @@
 Homepage: http://www.pycrypto.org/
 Rules-Requires-Root: no
 
-Package: python-crypto
-Architecture: any
-Depends:
- ${misc:Depends},
- ${python:Depends},
- ${shlibs:Depends}
-Provides:
- ${python:Provides}
-Description: cryptographic algorithms and protocols for Python
- A collection of cryptographic algorithms and protocols, implemented
- for use from Python. Among the contents of the package:
- .
-  * Hash functions: HMAC, MD2, MD4, MD5, RIPEMD160, SHA, SHA256.
-  * Block encryption algorithms: AES, ARC2, Blowfish, CAST, DES, Triple-DES.
-  * Stream encryption algorithms: ARC4, simple XOR.
-  * Public-key algorithms: RSA, DSA, ElGamal.
-  * Protocols: All-or-nothing transforms, chaffing/winnowing.
-  * Miscellaneous: RFC1751 module for converting 128-bit keys
-into a set of English words, primality testing, random number generation.
-
-Package: python-crypto-dbg
-Section: debug
-Architecture: any
-Depends:
- python-crypto (= ${binary:Version}),
- ${misc:Depends},
- ${python:Depends},
- ${shlibs:Depends}
-Provides:
- ${python:Provides}
-Description: cryptographic algorithms and protocols for Python (debug extension)
- A collection of cryptographic algorithms and protocols, implemented
- for use from Python.
- .
- This package contains the extensions built for the Python debug interpreter.
-
 Package: python3-crypto
 Architecture: any
 Depends:
diff -Nru python-crypto-2.6.1/debian/python-crypto-dbg.install python-crypto-2.6.1/debian/python-crypto-dbg.install
--- python-crypto-2.6.1/debian/python-crypto-dbg.install	2017-11-07 15:10:21.0 -0500
+++ python-crypto-2.6.1/debian/python-crypto-dbg.install	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-usr/lib/python2.*/*-packages/Crypto/*/*_d.so
diff -Nru python-crypto-2.6.1/debian/python-crypto-dbg.preinst python-crypto-2.6.1/debian/python-crypto-dbg.preinst
--- python-crypto-2.6.1/debian/python-crypto-dbg.preinst	2015-12-06 08:31:53.0 -0500
+++ python-crypto-2.6.1/debian/python-crypto-dbg.preinst	1969-12-31 19:00:00.0 -0500
@@ -1,10 +0,0 @@
-#!/bin/sh
-set -e
-
-# handle symlink to directory conversion (#700778)
-DOCDIR=/usr/share/doc/python-crypto-dbg
-if [ -L $DOCDIR ] ; then
-  rm $DOCDIR
-fi
-
-#DEBHELPER#
diff -Nru python-crypto-2.6.1/debian/python-crypto.docs python-crypto-2.6.1/debian/python-crypto.docs
--- python-crypto-2.6.1/debian/python-crypto.docs	2017-11-07 15:10:21.0 -0500
+++ python-crypto-2.6.1/debian/python-crypto.docs	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-README
diff -Nru python-crypto-2.6.1/debian/python-crypto.install python-crypto-2.6.1/debian/python-crypto.install
--- python-crypto-2.6.1/debian/python-crypto.install	2017-11-07 15:10:21.0 -0500
+++ python-crypto-2.6.1/debian/python-crypto.install	1969-12-31 19:00:00.0 -0500
@@ -1,6 +0,0 @@
-usr/lib/python2*/*-packages/*.egg-info
-usr/lib/python2*/*-packages/Crypto/*.py
-usr/lib/python2*/*-packages/Crypto/*/*.py
-usr/lib/python2*/*-packages/Crypto/*/*/*.py
-usr/lib/python2*/*-packages/Crypto/*/*[!_][!d].so
-usr/lib/python2*/*-packages/Crypto/SelfTest/*
diff -Nru python-crypto-2.6.1/debian/python-crypto.pydist python-crypto-2.6.1/debian/python-crypto.pydist
--- python-crypto-2.6.1/debian/python-crypto.pydist	2015-12-06 08:31:53.0 -0500
+++ python-crypto-2.6.1/debian/python-crypto.pydist	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-pycrypto python-crypto; PEP386
diff -Nru python-crypto-2.6.1/debian/rules python-crypto-2.6.1/debian/rules
--- python-crypto-2.6.1/debian/rules	2019-10-20 08:55:57.0 -0400
+++ python-crypto-2.6.1/debian/rules	2020-04-01 23:36:46.0 -0400
@@ -6,7 +6,7 @@
 endif
 
 %:
-	dh $@ --with=python2,python3 --buildsystem=pybuild
+	dh $@ --with=python3 --buildsystem=pybuild
 
 override_dh_clean:
 	# Keep LEGAL/copy/LICENSE.orig
diff -Nru python-crypto-2.6.1/debian/tests/control 

Processed: python-crypto: diff for NMU version 2.6.1-13.1

[Debian Bug Tracking System]

Processing control commands:

> tags 937671 + patch
Bug #937671 [src:python-crypto] python-crypto: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Processed: Bug#936329 marked as pending in constantly

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#937415: marked as done (pycurl: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 02 Apr 2020 03:33:29 +
with message-id 
and subject line Bug#937415: fixed in pycurl 7.43.0.2-3
has caused the Debian Bug report #937415,
regarding pycurl: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pycurl

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated pycurl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 23:22:15 -0400
Source: pycurl
Architecture: source
Version: 7.43.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 929194 937415
Changes:
 pycurl (7.43.0.2-3) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937415
   * debian/control
 - annotate flaky as nocheck, patch by Helmut Grohne; Closes: #929194
Checksums-Sha1:
 1563ddf1e04b09a226736513f05183bab6e2fc22 2304 pycurl_7.43.0.2-3.dsc
 f0e66ee3903c307a09ce8a894b29f618f6d1f912 9368 pycurl_7.43.0.2-3.debian.tar.xz
 5797a688abc488ce39c69a765671d0c5ba531539 9205 
pycurl_7.43.0.2-3_source.buildinfo
Checksums-Sha256:
 a184d3d1045edcef989bc156730377b86805da22936024f5bade8fbb951a4320 2304 
pycurl_7.43.0.2-3.dsc
 1ba903f277e1f8813304e0e048d06efbaaca617e0e26ab8c9fdc2c37faa518a2 9368 
pycurl_7.43.0.2-3.debian.tar.xz
 246ce41f8a8f57e3726ba0a447d9cf69bbc6758c5da9919a0e3e641e235092b9 9205 

Bug#936329: marked as pending in constantly

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #936329 in constantly 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/constantly/-/commit/417ef27432fa2f7ec60bf67c8323c8214b608c8e


Drop python2 support; Closes: #936329


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/936329

Bug#952131: marked as pending in pyhamcrest

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #952131 in pyhamcrest 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/pyhamcrest/-/commit/ac4aa2ffdc72e8847d5ef8aaf1cf9dcfe0acdf06


Drop python2 support; Closes: #937456, #952131


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952131

Processed: Bug#937456 marked as pending in pyhamcrest

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#937456: marked as pending in pyhamcrest

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #937456 in pyhamcrest 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/pyhamcrest/-/commit/ac4aa2ffdc72e8847d5ef8aaf1cf9dcfe0acdf06


Drop python2 support; Closes: #937456, #952131


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937456

Processed: Bug#952131 marked as pending in pyhamcrest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952131 [src:pyhamcrest] pyhamcrest: FTBFS: build-dependency not 
installable: python-pytest-cov
Added tag(s) pending.

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

Processed: Bug#937415 marked as pending in pycurl

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#937415: marked as pending in pycurl

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #937415 in pycurl 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/pycurl/-/commit/b180abc9189cd40674e81282b1d925c3f8a82639


Drop python2 support; Closes: #937415


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937415

Bug#936714: marked as done (hyperlink: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 02 Apr 2020 03:18:27 +
with message-id 
and subject line Bug#936714: fixed in hyperlink 19.0.0-2
has caused the Debian Bug report #936714,
regarding hyperlink: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:hyperlink

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated hyperlink package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 23:04:18 -0400
Source: hyperlink
Architecture: source
Version: 19.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 936714
Changes:
 hyperlink (19.0.0-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #936714
Checksums-Sha1:
 604452876f6d3907edd5aae5412c0d89828b4a7d 2090 hyperlink_19.0.0-2.dsc
 0bb2a7267d56b9a6d89b4ebf4f59e24958509d2d 2440 hyperlink_19.0.0-2.debian.tar.xz
 6e298d30f03ab1ac82508c4059864e1291c18214 7580 
hyperlink_19.0.0-2_source.buildinfo
Checksums-Sha256:
 7fe2021cba615cd6bc84ed31fc056e9c3c1717cf368f7b12e122d1cbf7b2f77a 2090 
hyperlink_19.0.0-2.dsc
 8a5665467d8a2840de0161819f284c3c75a26e3cf417c1296cb1d0411ad38bc6 2440 
hyperlink_19.0.0-2.debian.tar.xz
 

Bug#938487: marked as done (singledispatch: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 02 Apr 2020 03:18:32 +
with message-id 
and subject line Bug#938487: fixed in singledispatch 3.4.0.3-3
has caused the Debian Bug report #938487,
regarding singledispatch: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:singledispatch

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated singledispatch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 23:09:26 -0400
Source: singledispatch
Architecture: source
Version: 3.4.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938487
Changes:
 singledispatch (3.4.0.3-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Barry Warsaw ]
   * d/control: Put DPMT in Maintainers and myself in Uploaders.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/watch: Use https protocol
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938487
Checksums-Sha1:
 af2eede7479f70d2bcae794a20adadaf00b4e6e8 2102 

Bug#938487: marked as pending in singledispatch

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #938487 in singledispatch 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/singledispatch/-/commit/10bb7fe14c87cd081b74de5b4ade4008202d3605


Drop python2 support; Closes: #938487


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938487

Processed: Bug#938487 marked as pending in singledispatch

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#936714: marked as pending in hyperlink

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #936714 in hyperlink 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/hyperlink/-/commit/12b108324c4503d6eaffcb870ef9259f24de22f9


Drop python2 support; Closes: #936714


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/936714

Processed: Bug#936714 marked as pending in hyperlink

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: py2removal bugs severity updates - 2020-04-02 02:36:26.198620+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # and https://lists.debian.org/debian-python/2020/03/msg00087.html
> # mail threads for more details on this severity update
> # python-constantly is a module and has 0 external rdeps or not in testing
> severity 936329 serious
Bug #936329 [src:constantly] constantly: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # pssh is an application, has low popcon (562 <= 1000), and has 0 external 
> rdeps or not in testing
> severity 937329 serious
Bug #937329 [src:pssh] pssh: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-hamcrest is a module and has 0 external rdeps or not in testing
> severity 937456 serious
Bug #937456 [src:pyhamcrest] pyhamcrest: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # syslog-summary is an application, has low popcon (692 <= 1000), and has 0 
> external rdeps or not in testing
> severity 943282 serious
Bug #943282 [src:syslog-summary] syslog-summary: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # neopi is an application, has low popcon (398 <= 1000), and has 0 external 
> rdeps or not in testing
> severity 945710 serious
Bug #945710 [src:neopi] neopi: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # cfv is an application, has low popcon (387 <= 1000), and has 0 external 
> rdeps or not in testing
> severity 936288 serious
Bug #936288 [src:cfv] cfv: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # chirp is an application, has low popcon (350 <= 1000), and has 0 external 
> rdeps or not in testing
> severity 936299 serious
Bug #936299 [src:chirp] chirp: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-characteristic is a module and has 0 external rdeps or not in testing
> severity 937643 serious
Bug #937643 [src:python-characteristic] python-characteristic: Python2 removal 
in sid/bullseye
Severity set to 'serious' from 'normal'
> # trash-cli is an application, has low popcon (753 <= 1000), and has 0 
> external rdeps or not in testing
> severity 938719 serious
Bug #938719 [src:trash-cli] trash-cli: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # cvs2svn is an application, has low popcon (303 <= 1000), and has 0 external 
> rdeps or not in testing
> severity 942980 serious
Bug #942980 [src:cvs2svn] cvs2svn: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # denyhosts is an application, has low popcon (852 <= 1000), and has 0 
> external rdeps or not in testing
> severity 943009 serious
Bug #943009 [src:denyhosts] denyhosts: Python2 removal in sid/bullseye
Bug #936385 [src:denyhosts] denyhosts: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> # xboxdrv is an application, has low popcon (696 <= 1000), and has 0 external 
> rdeps or not in testing
> severity 945748 serious
Bug #945748 [src:xboxdrv] xboxdrv: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # gnat-gps is an application, has low popcon (354 <= 1000), and has 0 
> external rdeps or not in testing
> severity 936624 serious
Bug #936624 [src:gnat-gps] gnat-gps: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-crypto is a module and has 0 external rdeps or not in testing
> severity 937671 serious
Bug #937671 [src:python-crypto] python-crypto: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # virt-goodies is an application, has low popcon (430 <= 1000), and has 0 
> external rdeps or not in testing
> severity 938782 serious
Bug #938782 [src:virt-goodies] virt-goodies: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-avahi is a module and has 0 external rdeps or not in testing
> severity 936173 serious
Bug #936173 [src:avahi] avahi: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # postnews is an application, has low popcon (557 <= 1000), and has 0 
> external rdeps or not in testing
> severity 937312 serious
Bug #937312 [src:postnews] postnews: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-pycurl is a module and has 0 external rdeps or not in testing
> severity 937415 serious
Bug #937415 [src:pycurl] pycurl: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-singledispatch is a module and has 0 external rdeps or not in testing
> severity 938487 serious
Bug #938487 [src:singledispatch] singledispatch: Python2 

Bug#955527: kernelshark: Crash (SIGSEGV) when pressing the "+" button

[Boyuan Yang]

Package: kernelshark
Version:  2.8.3-5
Severity: grave
X-Debbugs-CC: sudipm.mukher...@gmail.com

Dear Debian kernelshark (trace-cmd) maintainer,

When I perform the following actions in kernelshark in Debian Sid, kernel
shark will crash:

1. Open kernelshark
2. Click the "+" button

Partial traceback is as follows:


===
Thread 1 "kernelshark" received signal SIGSEGV, Segmentation fault.
0x76d77918 in ksmodel_zoom (histo=0x7fffde60, r=,
mark=, zoom_in=) at ./kernel-
shark/src/libkshark-model.c:693
693 ./kernel-shark/src/libkshark-model.c: No such file or directionary.
(gdb) bt full
#0  0x76d77918 in ksmodel_zoom (histo=0x7fffde60, r=, mark=, zoom_in=) at ./kernel-
shark/src/libkshark-model.c:693
range = 
min = 
max = 
delta_min = 
delta_tot = 
#1  0x76d77d0a in ksmodel_zoom_in (histo=, r=, mark=) at ./kernel-shark/src/libkshark-model.c:722
No locals.
#2  0x77f591ba in KsGraphModel::zoomIn (this=0x7fffde50, r=0.01,
mark=-1) at ./kernel-shark/src/KsModels.cpp:473
No locals.
#3  0x77f6bb41 in KsTraceGraph::_updateGraphs (this=0x7fffd930,
action=KsTraceGraph::GraphActions::ZoomIn) at ./kernel-
shark/src/KsGLWidget.hpp:72
k = 0.01
bin = 
#4  0x775bc4e8 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#5  0x77aa358d in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#6  0x77aa3c6d in QAbstractButton::mousePressEvent(QMouseEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.



Let me know if more information is needed to debug this issue. Thanks!

-- 
Regards,
Boyuan Yang


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

Bug#938637: Status of telepathy-gabble and telepathy-salut IRT py2removal

[Sandro Tosi]

> I've just requested access to the telepathy team in salsa, so that i
> can push my changes there.

for now, attached the patch for the just uploaded package
diff --git a/debian/changelog b/debian/changelog
index 1550f7159..e398df2c1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+telepathy-gabble (0.18.4-2) unstable; urgency=medium
+
+  * Remove gobject, openssl, twisted from b-d, part of py2removal effort
+
+ -- Sandro Tosi   Wed, 01 Apr 2020 20:03:42 -0400
+
 telepathy-gabble (0.18.4-1) unstable; urgency=medium
 
   * debian/watch: Verify the gpg signature of the upstream tarball
diff --git a/debian/control b/debian/control
index 8a632adb7..d7efe5efb 100644
--- a/debian/control
+++ b/debian/control
@@ -17,9 +17,6 @@ Build-Depends: debhelper (>= 10),
libsoup2.4-dev (>= 2.42),
libtelepathy-glib-dev (>= 0.19.7),
python,
-   python-gobject,
-   python-openssl,
-   python-twisted,
xsltproc,
libsqlite3-dev,
libnice-dev (>= 0.0.11)

Bug#954826: libgcc-8-dev: depends on unavailable version of libgcc-s1

[Andreas Beckmann]

On Thu, 26 Mar 2020 21:02:59 +0100 Matthias Klose  wrote:
> yes, but we cannot rebuild the package, because it build-depends on gnat-8.
> Filed a removal bug for gcc-8 instead.

An easy fix would probably be to temporarily add a versioned
  Provides: libgcc-s1 (= 1:${binary:Version})
to libgcc-s1 in src:gcc-10 which should make libgcc-8-dev installable
again, s.t. gcc-8 can be rebuilt fixed.

Andreas

Bug#885476: marked as done (rabbitvcs: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Wed, 1 Apr 2020 18:20:44 -0400
with message-id 

and subject line Re: rabbitvcs: Depends on unmaintained pygtk
has caused the Debian Bug report #885476,
regarding rabbitvcs: Depends on unmaintained pygtk
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.)


-- 
885476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rabbitvcs
Version: 0.16-1.1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.18-1--- End Message ---

Bug#937638: marked as done (python-certifi: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 22:03:43 +
with message-id 
and subject line Bug#937638: fixed in python-certifi 2019.11.28-2
has caused the Debian Bug report #937638,
regarding python-certifi: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-certifi

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-certifi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 17:52:48 -0400
Source: python-certifi
Architecture: source
Version: 2019.11.28-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sandro Tosi 
Closes: 937638
Changes:
 python-certifi (2019.11.28-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #937638
Checksums-Sha1:
 13ebe742c3724ea5e7a2a47a6e8a3d4878e32729 1979 python-certifi_2019.11.28-2.dsc
 9f8451649a382d4a38ca4979a94ee67d7576d0fd 7628 
python-certifi_2019.11.28-2.debian.tar.xz
 4a4ee8b4d74d42e854fec2141bd8ebe97750ef78 6519 
python-certifi_2019.11.28-2_source.buildinfo
Checksums-Sha256:
 bb169b876b858f6f922a4b42f953ad2909cf0ebd44a1f908d1d1d6fab4c8f9d3 1979 
python-certifi_2019.11.28-2.dsc
 2eeae9ababc631bf42a548db490f0da84d14fd88731c67213d83cb771b72d067 7628 
python-certifi_2019.11.28-2.debian.tar.xz
 393ebfd29099c26f77fc61567b2591a70a37cbbb0f7fda691d86bb95d440fbe7 6519 

Bug#938483: marked as done (simplegeneric: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 22:03:54 +
with message-id 
and subject line Bug#938483: fixed in simplegeneric 0.8.1-3
has caused the Debian Bug report #938483,
regarding simplegeneric: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:simplegeneric

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated simplegeneric package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 17:41:02 -0400
Source: simplegeneric
Architecture: source
Version: 0.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 938483
Changes:
 simplegeneric (0.8.1-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Convert git repository from git-dpm to gbp layout
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #938483
Checksums-Sha1:
 e5cf185b5c04b826f2e7e13f63e371fc3f3b1fd3 2088 simplegeneric_0.8.1-3.dsc
 61dccdc18937c1735354797a23a05dd59fbae879 3356 
simplegeneric_0.8.1-3.debian.tar.xz
 42f2d5ad8af3c2bde46e06b99bf2b6aafdcb700a 6501 
simplegeneric_0.8.1-3_source.buildinfo
Checksums-Sha256:
 beb4eb63c2ef2afe82d7e76f687d6362676236a2a86372a5402bc56367e68157 2088 
simplegeneric_0.8.1-3.dsc
 3b21e70ce4b5f9929c51d93686c76909c25357b4b6e9c8b3dcd6bd8088ac3037 3356 

Bug#938278: marked as done (python-xmltodict: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 22:03:48 +
with message-id 
and subject line Bug#938278: fixed in python-xmltodict 0.12.0-2
has caused the Debian Bug report #938278,
regarding python-xmltodict: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-xmltodict

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-xmltodict package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 17:48:59 -0400
Source: python-xmltodict
Architecture: source
Version: 0.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Badia 
Changed-By: Sandro Tosi 
Closes: 938278
Changes:
 python-xmltodict (0.12.0-2) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #938278
Checksums-Sha1:
 589cdbdcb0a6be12a5f62ce947eedce3efb949f5 2021 python-xmltodict_0.12.0-2.dsc
 92ba274e0721ec93d531a052e0e8028094882c77 2756 
python-xmltodict_0.12.0-2.debian.tar.xz
 b654ff6374d4e88890f0e2bdc2b0dca2b024b764 6513 
python-xmltodict_0.12.0-2_source.buildinfo
Checksums-Sha256:
 5d0e1c4c57eeaf5901cb1fcdf85f9da941b87b6d876bc321a7c3c853c34d47b3 2021 
python-xmltodict_0.12.0-2.dsc
 988269139df327eb9f60b4de09eb27c73fd0437354a79d60e704f57f8e0da8a8 2756 
python-xmltodict_0.12.0-2.debian.tar.xz
 c249dea503d8869ea65603e4b8dfe752cc21705f7969d25be30d7bd45599951a 6513 

Bug#937638: python-certifi: Python2 removal in sid/bullseye

[Sandro Tosi]

On Fri, 30 Aug 2019 07:37:18 + Matthias Klose  wrote:
> Package: src:python-certifi
> Version: 2018.8.24-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

Consider maintain this package under the Debian python modules team umbrella

Bug#938278: python-xmltodict: Python2 removal in sid/bullseye

[Sandro Tosi]

On Fri, 30 Aug 2019 07:48:50 + Matthias Klose  wrote:
> Package: src:python-xmltodict
> Version: 0.11.0-2
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

Consider maintain this package under the Debian python modules team umbrella

Bug#938483: marked as pending in simplegeneric

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #938483 in simplegeneric 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/simplegeneric/-/commit/2f3c66ede1e868d201c944a4e6dfd61cad99caca


Drop python2 support; Closes: #938483


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/938483

Processed: Bug#938483 marked as pending in simplegeneric

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: py2removal bugs severity updates - 2020-04-01 21:36:46.190537+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-certifi is a module and has 0 external rdeps or not in testing
> severity 937638 serious
Bug #937638 [src:python-certifi] python-certifi: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-xmltodict is a module and has 0 external rdeps or not in testing
> severity 938278 serious
Bug #938278 [src:python-xmltodict] python-xmltodict: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # python-simplegeneric is a module and has 0 external rdeps or not in testing
> severity 938483 serious
Bug #938483 [src:simplegeneric] simplegeneric: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-backports-shutil-get-terminal-size is a module and has 0 external 
> rdeps or not in testing
> severity 937600 serious
Bug #937600 [src:python-backports-shutil-get-terminal-size] 
python-backports-shutil-get-terminal-size: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: tagging 955432

[Debian Bug Tracking System]

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

> tags 955432 + moreinfo unreproducible
Bug #955432 [src:gnome-shell-xrdesktop] gnome-shell-xrdesktop: FTBFS: 
dh_missing: warning: usr/share/bash-completion/completions/gnome-extensions 
exists in debian/tmp but is not installed to anywhere
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Bug#938637: Status of telepathy-gabble and telepathy-salut IRT py2removal

[Sandro Tosi]

Hello,
telepathy-gabble and telepathy-salut are the last 2 reverse
dependencies for python-twisted in Debian unstable, and i'd very much
like to remove that package soon.

It looks like twisted is only used for tests in both those packages
and it looks like they are not being run in d/rules anyway.

I'll try update the package to remove the dependency on python-twisted
(and all other python2 modules i can).

I've just requested access to the telepathy team in salsa, so that i
can push my changes there.

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Processed: fixed 945171 in 1:9.15.6-1

[Debian Bug Tracking System]

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

> fixed 945171 1:9.15.6-1
Bug #945171 {Done: Salvatore Bonaccorso } [src:bind9] bind9: 
CVE-2019-6477: TCP-pipelined queries can bypass tcp-clients limit
The source 'bind9' and version '1:9.15.6-1' do not appear to match any binary 
packages
Marked as fixed in versions bind9/1:9.15.6-1.
> thanks
Stopping processing here.

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

Bug#885506: bumping severity of pygtk bugs

[Moritz Mühlenhoff]

On Mon, Oct 07, 2019 at 04:53:03PM +0200, Thibaut Paumard wrote:
> Dear Jeremy,
> 
> Thanks, I have warned upstream that YAO will be removed if not updated
> to Python 3 and Gtk 3.

It's now the last package blocking the removal of pygtk, let's remove it.

Cheers,
Moritz

Bug#890168: python-gasp: Please switch to python-gobject-2/python-gi

[Moritz Mühlenhoff]

On Tue, Mar 24, 2020 at 10:13:33PM +0100, Moritz Mühlenhoff wrote:
> On Sun, Oct 06, 2019 at 06:00:02PM -0400, Jeremy Bicha wrote:
> > Control: severity -1 serious
> > Tags: fixed-upstream
> > 
> > It looks to me like upstream has ported gasp to Python3 and GObject
> > Introspection.
> > 
> > https://launchpad.net/gasp-core
> 
> Hi Luke,
> are you still interested in maintaining python-gasp/updating it to
> the current upstream? Otherwise I'll file a removal bug, it's among
> the last handful of packages blocking the pygtk removal at this point.

I've filed an RM bug now to unclock the pygtk removal. gasp can
still be reintroduced before the bullseye release.

Cheers,
Moritz

Bug#955511: xbmc-pvr-addons: Should be removed from testing

[Balint Reczey]

Source: xbmc-pvr-addons
Severity: serious

Hi,

The source builds only transitional packages and they are not needed anymore.
After removing them from testing they can be removed from unstable as well.

Cheers,
Balint

-- 
Balint Reczey
Ubuntu & Debian Developer

Processed: OpenSSL EOF handling, severity import

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #954402 [m2crypto] m2crypto: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'

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

Processed: OpenSSL EOF handling, severity import

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #954416 [python3.8] python3.8: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'

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

Processed: OpenSSL EOF handling, severity import

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #954418 [python2.7] python2.7: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'

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

Processed: OpenSSL EOF handling, severity import

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #954419 [ruby2.7] ruby2.7: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'

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

Bug#954402: OpenSSL EOF handling, severity import

[Sebastian Andrzej Siewior]

Control: severity -1 important

OpenSSL 1.1.1f is in unstable now which reverts the unexpected EOF
reporting via SSL_ERROR_SSL.
In the OpenSSL 3.0 release it will be reported again as SSL_ERROR_SSL
with reason code SSL_R_UNEXPECTED_EOF_WHILE_READING.
Therefore the severity is downgraded to `important' because it no longer
leads to an error during build but will later.

Sebastian

Processed: OpenSSL EOF handling, severity import

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #954417 [python3.7] python3.7: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'

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

Bug#953347: marked as done (src:fuzzywuzzy: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Wed, 1 Apr 2020 22:09:29 +0200
with message-id <9fd18286-a935-e7de-5654-a4b2cc195...@debian.org>
and subject line Re: src:fuzzywuzzy: fails to migrate to testing for too long
has caused the Debian Bug report #953347,
regarding src:fuzzywuzzy: fails to migrate to testing for too long
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.)


-- 
953347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fuzzywuzzy
Version: 0.17.0-1
Severity: serious
Control: fixed -1 0.17.0-2
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:fuzzywuzzy in
its current version in unstable has been trying to migrate for 190 days.
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.18.0-1

On Sun, 8 Mar 2020 10:31:54 +0100 Paul Gevers  wrote:
> Your package is only blocked because the arch:all binary package(s)
> aren't built on a buildd. Unfortunately the Debian infrastructure
> doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
> shortly do a no-changes source-only upload to DELAYED/15, closing this
> bug. Please let me know if I should delay or cancel that upload.

A regular upload beat my binNMU, thank you. Closing this bug.

Paul



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#953186: marked as done (src:python-django-rest-hooks: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Wed, 1 Apr 2020 22:07:19 +0200
with message-id <69e20560-d250-66d6-cf9a-2d2b0c94f...@debian.org>
and subject line Re: src:python-django-rest-hooks: fails to migrate to testing 
for too long
has caused the Debian Bug report #953186,
regarding src:python-django-rest-hooks: fails to migrate to testing for too long
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.)


-- 
953186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-rest-hooks
Version: 1.5.0-1
Severity: serious
Control: fixed -1 1.6.0-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:python-django-rest-hooks in its current version in unstable has been
trying to migrate for 231 days. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

Because the only issue with the version of your package in unstable is
that you uploaded an arch:all binary (which isn't allowed anymore to
migrate to testing, but unfortunately can't be binNMU'ed), I will
shortly do a source-only upload to DELAYED/15, closing this bug.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.5.0-1.1

On Thu, 5 Mar 2020 17:26:24 +0100 Paul Gevers  wrote:
> Because the only issue with the version of your package in unstable is
> that you uploaded an arch:all binary (which isn't allowed anymore to
> migrate to testing, but unfortunately can't be binNMU'ed), I will
> shortly do a source-only upload to DELAYED/15, closing this bug.

I had a typo in the changelog. This package migrated to testing.

Paul




signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#954495: marked as done (libpoe-component-sslify-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 1)

[Debian Bug Tracking System]

Your message dated Wed, 1 Apr 2020 21:59:35 +0200
with message-id <20200401195935.ga32...@jadzia.comodo.priv.at>
and subject line Re: Bug#954495: libpoe-component-sslify-perl: FTBFS: 
dh_auto_test: error: perl Build test --verbose 1 returned exit code 1
has caused the Debian Bug report #954495,
regarding libpoe-component-sslify-perl: FTBFS: dh_auto_test: error: perl Build 
test --verbose 1 returned exit code 1
to be marked as done.

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

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


-- 
954495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpoe-component-sslify-perl
Version: 1.012-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_auto_configure
>   perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
> "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
> Creating new 'Build' script for 'POE-Component-SSLify' version '1.012'
>dh_auto_build
>   perl Build
> cp lib/POE/Component/SSLify.pm blib/lib/POE/Component/SSLify.pm
> cp lib/POE/Component/SSLify/ServerHandle.pm 
> blib/lib/POE/Component/SSLify/ServerHandle.pm
> cp lib/POE/Component/SSLify/ClientHandle.pm 
> blib/lib/POE/Component/SSLify/ClientHandle.pm
>dh_auto_test
>   perl Build test --verbose 1
> t/00-compile.t  
> 1..3
> ok 1 - POE/Component/SSLify.pm loaded ok
> ok 2 - POE/Component/SSLify/ClientHandle.pm loaded ok
> ok 3 - POE/Component/SSLify/ServerHandle.pm loaded ok
> ok
> # 
> # Versions for all modules listed in MYMETA.json (including optional ones):
> # 
> # === Configure Requires ===
> # 
> # Module   Want  Have
> # --- - -
> # ExtUtils::MakeMaker   any  7.34
> # Module::Build::Tiny 0.039 0.039
> # 
> # === Test Requires ===
> # 
> # Module  Want Have
> # ---  
> # ExtUtils::MakeMaker  any 7.34
> # File::Spec   any 3.78
> # File::Temp   any   0.2309
> # IO::Handle  1.28 1.40
> # IPC::Open3   any 1.20
> # POE1.2671.368
> # POE::Component::Client::TCP  any1.368
> # POE::Component::Server::TCP  any1.368
> # POE::Filter::Stream  any1.368
> # Socket   any2.027
> # Test::FailWarnings   any0.008
> # Test::More  1.001002 1.302162
> # 
> # === Test Recommends ===
> # 
> # Module Want Have
> # --  
> # CPAN::Meta 2.120900 2.150010
> # 
> # === Runtime Requires ===
> # 
> # ModuleWant  Have
> #  - -
> # Exporter   any  5.73
> # IO::Handle1.28  1.40
> # Net::SSLeay   1.36  1.88
> # POE  1.267 1.368
> # Scalar::Util   any  1.50
> # Symbol any  1.08
> # Task::Weaken  1.03  1.06
> # parent any 0.237
> # strict any  1.11
> # warnings   any  1.44
> # 
> t/00-report-prereqs.t . 
> 1..1
> ok 1
> ok
> # 
> # Net::SSLeay::ver_number is 0x1010105f
> # OpenSSL 1.1.1e  17 Mar 2020
> # built on: Wed Mar 18 19:59:39 2020 UTC
> # platform: debian-amd64
> # OPENSSLDIR: "/usr/lib/ssl"
> # pogomips: 55573740
> t/00-ssleay-info.t  
> ok 1 - fake test for info
> 1..1
> ok
> t/99_mire_test.t .. skipped: AUTHOR TEST
> t/apocalypse.t  skipped: Test::Apocalypse required for 
> validating the distribution
> t/connect_hook.t .. 
> ok 1 - SERVER: SSLify_Options 
> ok 2 - SERVER: Server_SSLify 
> ok 3 - SERVER: SSLify_GetStatus is pending
> ok 4 - SERVER: accepted
> ok 5 - CLIENT: Client_SSLify 
> ok 6 - CLIENT: SSLify_GetStatus is pending
> ok 7 - CLIENT: connected
> ok 8 - CLIENT: Got callback hook status
> ok 9 - CLIENT: Status received from callback is OK
> ok 10 - CLIENT: SSLify_GetCipher: TLS_AES_256_GCM_SHA384
> ok 11 - CLIENT: SSLify_GetStatus is done
> ok 12 - 

Bug#954371: [Pkg-openssl-devel] Bug#954371: Bug#954371: libio-socket-ssl-perl: FTBFS since openssl 1.1.1e

[Salvatore Bonaccorso]

Control: reassign -1 libio-socket-ssl-perl 2.067-1
Control: severity -1 important

Hi,

On Wed, Apr 01, 2020 at 08:40:05PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-03-31 21:49:51 [+0200], Salvatore Bonaccorso wrote:
> > Hi Kurt,
> Hi Salvatore,
> 
> > I see, but then I prefer to loop in Steffen Ullrich into the loop
> > (upstream of IO::Socket::SSL). Steffen, see the above comment from
> > Kurt in the Debian bug, so it looks we cannot close
> > https://github.com/noxxi/p5-io-socket-ssl/issues/93 by marking 1.1.1e
> > as broken only. What do you think?
> 
> we have openssl f in unstable so the visibile problem is gone for now.
> Can this bug be assigned back to libio-socket-ssl-perl?

Okay let's do that.

Steffen Any comment on Kurt's hints in
https://bugs.debian.org/954371#42?

Regards,
Salvatore

Processed: Re: Bug#954371: [Pkg-openssl-devel] Bug#954371: Bug#954371: libio-socket-ssl-perl: FTBFS since openssl 1.1.1e

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libio-socket-ssl-perl 2.067-1
Bug #954371 [src:openssl] libio-socket-ssl-perl: FTBFS since openssl 1.1.1e
Bug reassigned from package 'src:openssl' to 'libio-socket-ssl-perl'.
No longer marked as found in versions openssl/1.1.1e-1.
Ignoring request to alter fixed versions of bug #954371 to the same values 
previously set
Bug #954371 [libio-socket-ssl-perl] libio-socket-ssl-perl: FTBFS since openssl 
1.1.1e
Marked as found in versions libio-socket-ssl-perl/2.067-1.
> severity -1 important
Bug #954371 [libio-socket-ssl-perl] libio-socket-ssl-perl: FTBFS since openssl 
1.1.1e
Severity set to 'important' from 'serious'

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

Bug#907453: marked as done (irda-utils: No IrDA support in the buster kernel)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:27:52 +
with message-id 
and subject line Bug#955337: Removed package(s) from unstable
has caused the Debian Bug report #907453,
regarding irda-utils: No IrDA support in the buster kernel
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.)


-- 
907453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: irda-utils
Version: 0.9.18-15
Severity: serious
Tags: buster sid

The upstream kernel dropped IrDA support,
shipping irda-utils in buster might therefore
not make sense.
--- End Message ---
--- Begin Message ---
Version: 0.9.18-15+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#937523: marked as done (pyrit-opencl: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:29:28 +
with message-id 
and subject line Bug#955344: Removed package(s) from unstable
has caused the Debian Bug report #937523,
regarding pyrit-opencl: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pyrit-opencl

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#947298: marked as done (ipython-py2: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:10:09 +
with message-id 
and subject line Bug#955404: Removed package(s) from unstable
has caused the Debian Bug report #947298,
regarding ipython-py2: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
947298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipython-py2
Version: 5.8.0-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests, in details:

(source:ipython-py2)Build-Depends->python
(source:ipython-py2)Build-Depends->python-backports-shutil-get-terminal-size
(source:ipython-py2)Build-Depends->python-ipython-genutils
(source:ipython-py2)Build-Depends->python-matplotlib
(source:ipython-py2)Build-Depends->python-nose
(source:ipython-py2)Build-Depends->python-pexpect
(source:ipython-py2)Build-Depends->python-pickleshare
(source:ipython-py2)Build-Depends->python-prompt-toolkit
(source:ipython-py2)Build-Depends->python-setuptools
(source:ipython-py2)Testsuite-Triggers->python
(binary:python-ipython)Depends->python-decorator
(binary:python-ipython)Depends->python-pexpect
(binary:python-ipython)Depends->python-pickleshare
(binary:python-ipython)Depends->python-pkg-resources
(binary:python-ipython)Depends->python-prompt-toolkit
(binary:python-ipython)Depends->python-pygments
(binary:python-ipython)Depends->python-simplegeneric
(binary:python-ipython)Depends->python-traitlets
(binary:python-ipython)Depends->python2:any
(binary:python-ipython)Depends->python2:any
(binary:python-ipython)Depends->python-backports-shutil-get-terminal-size
(binary:python-ipython)Depends->python-pathlib2
(binary:ipython)Depends->python-ipython

Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#938567: marked as done (starpy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:09:33 +
with message-id 
and subject line Bug#955382: Removed package(s) from unstable
has caused the Debian Bug report #938567,
regarding starpy: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
938567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:starpy
Version: 1.0.1.0.git.20151124-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:starpy

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#937726: marked as done (python-elements: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:11:15 +
with message-id 
and subject line Bug#955503: Removed package(s) from unstable
has caused the Debian Bug report #937726,
regarding python-elements: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
937726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-elements
Version: 0.13+svn20090823.230+dfsg-2.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-elements

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.13+svn20090823.230+dfsg-2.1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#899900: marked as done (python-elements: Invalid maintainer address debian-olpc-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:11:15 +
with message-id 
and subject line Bug#955503: Removed package(s) from unstable
has caused the Debian Bug report #899900,
regarding python-elements: Invalid maintainer address 
debian-olpc-de...@lists.alioth.debian.org
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.)


-- 
899900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-elements
Version: 0.13+svn20090823.230+dfsg-2.1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of python-elements,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package python-elements since the list address
debian-olpc-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
debian-olpc-de...@lists.alioth.debian.org is 6.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.13+svn20090823.230+dfsg-2.1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#895520: marked as done (libunique-1.0-0: deprecated and unmaintained upstream)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:07:24 +
with message-id 
and subject line Bug#955350: Removed package(s) from unstable
has caused the Debian Bug report #895520,
regarding libunique-1.0-0: deprecated and unmaintained upstream
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.)


-- 
895520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libunique-1.0-0
Version: 1.1.6-4
Severity: important
Tags: upstream wontfix

libunique is obsolete, and is no longer maintained by its former upstream
developers. The supported replacement is GApplication or GtkApplication,
available since GLib 2.26 and GTK+ 3.0.

Official migration guide:
https://developer.gnome.org/gtk3/stable/gtk-migrating-unique-GtkApplication.html

smcv
--- End Message ---
--- Begin Message ---
Version: 1.1.6-6+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#952035: marked as done (ruby-ridley: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError:)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:08:19 +
with message-id 
and subject line Bug#955372: Removed package(s) from unstable
has caused the Debian Bug report #952035,
regarding ruby-ridley: FTBFS: ERROR: Test "ruby2.7" failed:  ArgumentError:
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.)


-- 
952035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-ridley
Version: 5.1.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  ArgumentError:
>extra arguments
>  # ./lib/ridley/connection.rb:148:in `block in stream'
>  # ./lib/ridley/connection.rb:147:in `stream'
>  # (celluloid):0:in `remote procedure call'
>  # (celluloid):0:in `remote procedure call'
>  # ./lib/ridley/chef_objects/cookbook_object.rb:140:in `download_file'
>  # ./lib/ridley/chef_objects/cookbook_object.rb:90:in `block (2 levels) 
> in download'
>  # ./lib/ridley/chef_objects/cookbook_object.rb:87:in `each'
>  # ./lib/ridley/chef_objects/cookbook_object.rb:87:in `block in download'
>  # ./lib/ridley/chef_objects/cookbook_object.rb:84:in `each'
>  # ./lib/ridley/chef_objects/cookbook_object.rb:84:in `download'
>  # ./lib/ridley/resources/cookbook_resource.rb:84:in `download'
>  # (celluloid):0:in `remote procedure call'
>  # ./spec/acceptance/cookbook_resource_spec.rb:18:in `block (4 levels) in 
> '
> 
> Deprecation Warnings:
> 
> RSpec::Core::Configuration#treat_symbols_as_metadata_keys_with_true_values= 
> is deprecated, it is now set to true as default and setting it to false has 
> no effect.
> 
> Using `stub` from rspec-mocks' old `:should` syntax without explicitly 
> enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly 
> enable `:should` instead. Called from 
> /usr/lib/ruby/vendor_ruby/celluloid/calls.rb:26:in `public_send'.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 2 deprecation warnings total
> 
> Finished in 4.85 seconds (files took 1.96 seconds to load)
> 461 examples, 1 failure, 18 pending
> 
> Failed examples:
> 
> rspec ./spec/acceptance/cookbook_resource_spec.rb:20 # Client API operations 
> downloading a cookbook when the cookbook of the name/version is found 
> downloads the cookbook to the destination
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/ruby-ridley_5.1.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 5.1.1-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#885813: marked as done (xfce4-notes-plugin: Depends on libunique)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:06:12 +
with message-id 
and subject line Bug#955349: Removed package(s) from unstable
has caused the Debian Bug report #885813,
regarding xfce4-notes-plugin: Depends on libunique
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.)


-- 
885813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-notes-plugin
Version: 1.8.1-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libunique
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on libunique.

The 1.8.0 NEWS entry says that there is a gtk3 build option, but it is
"missing features" compared to the gtk2 version.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.8.1-3+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#936720: marked as done (identicurse: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:04:22 +
with message-id 
and subject line Bug#955252: Removed package(s) from unstable
has caused the Debian Bug report #936720,
regarding identicurse: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:identicurse
Version: 0.9+dfsg0-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:identicurse

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#937267: marked as done (pebl: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:04:43 +
with message-id 
and subject line Bug#955305: Removed package(s) from unstable
has caused the Debian Bug report #937267,
regarding pebl: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pebl

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#719916: marked as done (Getting "Unexpected title page format Error" from yahoo2mbox)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:05:02 +
with message-id 
and subject line Bug#955334: Removed package(s) from unstable
has caused the Debian Bug report #719916,
regarding Getting "Unexpected title page format Error" from yahoo2mbox
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.)


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

Package: yahoo2mbox
Version: 0.24-1

I entered the following on the command line:
rich@rich2:/usr/bin$ ./yahoo2mbox.pl -o ~/board18 --user=richpri2010 
--pass=BD18yahoo http://games.groups.yahoo.com/group/BOARD18/


I recieved the following output:
bash: ./yahoo2mbox.pl: No such file or directory
rich@rich2:/usr/bin$ ./yahoo2mbox -o ~/board18 --user=richpri2010 
--pass=BD18yahoo http://games.groups.yahoo.com/group/BOARD18/

Logging in as richpri2010... ok.
Getting number of messages in group 
http://games.groups.yahoo.com/group/BOARD18/...

Unexpected title page format (Yahoo! Groups).

No output file was produced.

--
Rich Price
r...@gandalf.ws
---
“The abdomen is the reason why man does
not readily take himself to be a god.”
   Friedrich Nietzsche
 
--- End Message ---
--- Begin Message ---
Version: 0.25-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#938202: marked as done (python-stompy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:03:57 +
with message-id 
and subject line Bug#955251: Removed package(s) from unstable
has caused the Debian Bug report #938202,
regarding python-stompy: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-stompy

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#885282: marked as done (gameclock: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:03:16 +
with message-id 
and subject line Bug#955199: Removed package(s) from unstable
has caused the Debian Bug report #885282,
regarding gameclock: Depends on unmaintained pygtk
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.)


-- 
885282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gameclock
Version: 5.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 5.1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#938210: marked as done (python-tcpwrap: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:03:37 +
with message-id 
and subject line Bug#955200: Removed package(s) from unstable
has caused the Debian Bug report #938210,
regarding python-tcpwrap: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-tcpwrap

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#936577: marked as done (gameclock: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:03:16 +
with message-id 
and subject line Bug#955199: Removed package(s) from unstable
has caused the Debian Bug report #936577,
regarding gameclock: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:gameclock

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#754377: marked as done (eeepc-acpi-scripts: fails to install due to insserv rejecting the script header)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:02:55 +
with message-id 
and subject line Bug#955195: Removed package(s) from unstable
has caused the Debian Bug report #754377,
regarding eeepc-acpi-scripts: fails to install due to insserv rejecting the 
script header
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.)


-- 
754377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eeepc-acpi-scripts
Version: 1.1.12
Severity: serious
tags: sid jessie
User: debian...@lists.debian.org
Usertags: piuparts


Hi, 

during a test with piuparts I noticed your package failed to install due to 
insserv rejecting the script header. Some notes are 
available from at http://wiki.debian.org/LSBInitScripts

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

  Selecting previously unselected package eeepc-acpi-scripts.
  (Reading database ... 7553 files and directories currently installed.)
  Preparing to unpack .../eeepc-acpi-scripts_1.1.12_all.deb ...
  Unpacking eeepc-acpi-scripts (1.1.12) ...
  Setting up eeepc-acpi-scripts (1.1.12) ...
  Removing stray rc.d stop links
  update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults
  insserv: Service udev has to be enabled to start service eeepc-acpi-scripts
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package eeepc-acpi-scripts (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   eeepc-acpi-scripts
  E: Sub-process /usr/bin/dpkg returned an error code (1)

This only occurs in sid and jessie, but not with the same version of eeepc-
acpi-scripts in wheezy:

https://piuparts.debian.org/jessie/fail/eeepc-acpi-scripts_1.1.12.log
https://piuparts.debian.org/sid/fail/eeepc-acpi-scripts_1.1.12.log
https://piuparts.debian.org/wheezy/pass/eeepc-acpi-scripts_1.1.12.log


cheers,
Holger
Start: 2014-07-05 09:44:39 UTC

Package: eeepc-acpi-scripts
Version: 1.1.12
Installed-Size: 142
Maintainer: Debian Eee PC Team 
Architecture: all
Depends: acpid (>= 1:2.0.0-1), acpi-support-base, acpi-support, initscripts (>= 2.88dsf-13.3), pm-utils, rfkill (>= 0.3-3)
Suggests: alsa-utils, libnotify-bin
Description: Scripts to support suspend and hotkeys on the Asus Eee PC laptop
Description-md5: 00cfc39420956e29eab8942cc6c0b1a4
Tag: hardware::laptop, hardware::power:acpi, implemented-in::shell,
 role::plugin, works-with::TODO
Section: utils
Priority: extra
Filename: pool/main/e/eeepc-acpi-scripts/eeepc-acpi-scripts_1.1.12_all.deb
Size: 26064
MD5sum: f2187aefabf873425dcc665800c69bb1
SHA1: 697ff2176503af4d2531e21b2fcf70b00056336d
SHA256: f9e9f8f07b6aae4c4129756ff0b6f7e6634be42a904f2379f7812c3fc60f8b56

Executing: sudo env PYTHONPATH=/srv/piuparts.debian.org/lib/python2.7/dist-packages timeout -s INT -k 5m 35m /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt eeepc-acpi-scripts=1.1.12
0m0.0s INFO: --
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts is wrong.
0m0.0s INFO: --
0m0.0s INFO: piuparts version 0.59~201405301115~0.58-62-g352dac2 starting up.
0m0.0s INFO: Command line arguments: /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt eeepc-acpi-scripts=1.1.12
0m0.0s INFO: Running on: Linux piu-slave-bm-a 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64
0m0.0s DEBUG: Created temporary directory /srv/piuparts.debian.org/tmp/tmpIsoBLn
0m0.0s DEBUG: Unpacking /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz into /srv/piuparts.debian.org/tmp/tmpIsoBLn

Bug#954897: marked as done (RM: pydxcluster - RoQA; python2-only; no upstream release since 2016; low popcon; no rdeps)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:00:10 +
with message-id 
and subject line Bug#954897: Removed package(s) from unstable
has caused the Debian Bug report #954897,
regarding RM: pydxcluster - RoQA; python2-only; no upstream release since 2016; 
low popcon; no rdeps
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.)


-- 
954897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pydxcluster
Severity: serious
Tags: sid, bullseye

Hello,
i believe this package should be removed:

* python2-only
* no upstream releases since 2016 (with no other sign of development)
* low popcon
* no rdeps

If i dont hear back within a week with a good reason to keep this package, i'll
file for it's removal.

Regards,
Sandro

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

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

Versions of packages pydxcluster depends on:
ii  python2.7.16-1
pn  python-pygame 
ii  python-requests   2.21.0-1
ii  python-tk 2.7.16-2
pn  python-xmltodict  

pydxcluster recommends no packages.

pydxcluster suggests no packages.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

pydxcluster | 2.21-2 | source, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
pydxcluster |  2.21-2+b1 | amd64

--- Reason ---
RoQA; python2-only; no upstream release since 2016; low popcon; no rdeps
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/954897

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

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

Bug#912495: marked as done (pydxcluster: Please migrate to python3-pygame)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:00:15 +
with message-id 
and subject line Bug#954897: Removed package(s) from unstable
has caused the Debian Bug report #912495,
regarding pydxcluster: Please migrate to python3-pygame
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.)


-- 
912495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pydxcluster
Severity: wishlist
User: python-modules-t...@lists.alioth.debian.org
Usertags: python3-migration

Dear maintainer,

thanks for maintaining a pygame-based game in Debian!

As you might have heard, Python 2 will be end of life in the not so
far future. Thus, I would like to start to get the reverse
dependencies of the Python 2 version of pygame down, so this can be
done with some time and not in a hurried effort that probably makes
us loose games from Debian.

If you already know that your game will work with Python 3, please
build against and depend on python3-pygame, which has long been
available in sid and will migrate to buster shortly.

If you do not yet know whether this will work, your chances that it
will just work are still quite good, so please just give it a shot.

If you find your package does not work with Python 3 yet, you can…

a) …check what to do with upstream

b) …try to patch it (and forward your patch upstream)

c) …tag this bug report help - the next pygame-fluent kangaroo

is reserved for you!

Feel free to ask any questions if you are unsure what to do.

Cheers, Nik 
--- End Message ---
--- Begin Message ---
Version: 2.21-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#945731: marked as done (pydxcluster: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:00:15 +
with message-id 
and subject line Bug#954897: Removed package(s) from unstable
has caused the Debian Bug report #912495,
regarding pydxcluster: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
912495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pydxcluster
Version: 2.21-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#938461: marked as done (securepass-tools: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:02:13 +
with message-id 
and subject line Bug#955179: Removed package(s) from unstable
has caused the Debian Bug report #938461,
regarding securepass-tools: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:securepass-tools

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

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

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#899689: marked as done (securepass-tools: Invalid maintainer address pkg-securepass-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 19:02:13 +
with message-id 
and subject line Bug#955179: Removed package(s) from unstable
has caused the Debian Bug report #899689,
regarding securepass-tools: Invalid maintainer address 
pkg-securepass-de...@lists.alioth.debian.org
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.)


-- 
899689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:securepass-tools
Version: 0.4.6-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of securepass-tools,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package securepass-tools since the list address
pkg-securepass-de...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-securepass-de...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.4.6-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

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

Bug#954371: [Pkg-openssl-devel] Bug#954371: Bug#954371: libio-socket-ssl-perl: FTBFS since openssl 1.1.1e

[Sebastian Andrzej Siewior]

On 2020-03-31 21:49:51 [+0200], Salvatore Bonaccorso wrote:
> Hi Kurt,
Hi Salvatore,

> I see, but then I prefer to loop in Steffen Ullrich into the loop
> (upstream of IO::Socket::SSL). Steffen, see the above comment from
> Kurt in the Debian bug, so it looks we cannot close
> https://github.com/noxxi/p5-io-socket-ssl/issues/93 by marking 1.1.1e
> as broken only. What do you think?

we have openssl f in unstable so the visibile problem is gone for now.
Can this bug be assigned back to libio-socket-ssl-perl?

> Regards,
> Salvatore

Sebastian

Processed: py2removal bugs severity updates - 2020-04-01 17:36:45.994787+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # not all bin pkgs are leaf for src:gimp-plugin-registry, lower severity
> severity 936612 normal
Bug #936612 [src:gimp-plugin-registry] gimp-plugin-registry: Python2 removal in 
sid/bullseye
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#946771: marked as done (librdf-doap-perl: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 16:48:37 +
with message-id 
and subject line Bug#946771: fixed in librdf-doap-perl 0.104-2
has caused the Debian Bug report #946771,
regarding librdf-doap-perl: autopkgtest failure
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.)


-- 
946771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librdf-doap-perl
Version: 0.104-1
Severity: serious
Justification: no testing migration with autopkgtest failure

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

librdf-doap-perl 0.104-1 has enabled autopkgtest-pkg-perl.
Unfortunately they fail:
https://ci.debian.net/packages/libr/librdf-doap-perl/unstable/amd64/
https://ci.debian.net/data/autopkgtest/unstable/amd64/libr/librdf-doap-perl/3669776/log.gz

The failure is in the third test, syntax.t:

# Subtest: all modules in librdf-doap-perl pass the syntax check
1..22
ok 1 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Addition.pm 
exited successfully
ok 2 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/BackCompat.pm 
exited successfully
# Undefined subroutine ::Trine::NIL_GRAPH called at 
/usr/share/perl5/RDF/Trine/Node/Resource.pm line 78.
# Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 
314.
# Compilation failed in require at 
/usr/share/perl5/RDF/DOAP/Change/Bugfix.pm line 9.
# BEGIN failed--compilation aborted at 
/usr/share/perl5/RDF/DOAP/Change/Bugfix.pm line 9.
not ok 3 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Bugfix.pm 
exited successfully
ok 4 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Documentation.pm 
exited successfully
ok 5 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Packaging.pm 
exited successfully
ok 6 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Regression.pm 
exited successfully
ok 7 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Removal.pm exited 
successfully
ok 8 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/SecurityFix.pm 
exited successfully
ok 9 - /usr/bin/perl -wc 
/usr/share/perl5/RDF/DOAP/Change/SecurityRegression.pm exited successfully
ok 10 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Tests.pm exited 
successfully
ok 11 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change/Update.pm exited 
successfully
# Undefined subroutine ::Trine::NIL_GRAPH called at 
/usr/share/perl5/RDF/Trine/Node/Resource.pm line 78.
# Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 
314.
# Compilation failed in require at /usr/share/perl5/RDF/DOAP/Change.pm line 
9.
# BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Change.pm 
line 9.
not ok 12 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Change.pm exited 
successfully
# Undefined subroutine ::Trine::NIL_GRAPH called at 
/usr/share/perl5/RDF/Trine/Node/Resource.pm line 78.
# Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 
314.
# Compilation failed in require at /usr/share/perl5/RDF/DOAP/Change.pm line 
9.
# BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Change.pm 
line 9.
# Compilation failed in require at /usr/share/perl5/RDF/DOAP/ChangeSet.pm 
line 10.
# BEGIN failed--compilation aborted at 
/usr/share/perl5/RDF/DOAP/ChangeSet.pm line 10.
not ok 13 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/ChangeSet.pm exited 
successfully
ok 14 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Issue.pm exited 
successfully
ok 15 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Person.pm exited 
successfully
# Undefined subroutine ::Trine::NIL_GRAPH called at 
/usr/share/perl5/RDF/Trine/Node/Resource.pm line 78.
# Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 
314.
# Compilation failed in require at /usr/share/perl5/RDF/DOAP/Project.pm 
line 9.
# BEGIN failed--compilation aborted at /usr/share/perl5/RDF/DOAP/Project.pm 
line 9.
not ok 16 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Project.pm exited 
successfully
ok 17 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Repository.pm exited 
successfully
ok 18 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Resource.pm exited 
successfully
ok 19 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Types.pm exited 
successfully
ok 20 - /usr/bin/perl -wc /usr/share/perl5/RDF/DOAP/Utils.pm exited 
successfully
# Undefined subroutine ::Trine::NIL_GRAPH called at 
/usr/share/perl5/RDF/Trine/Node/Resource.pm line 78.
# 

Bug#946771: marked as pending in librdf-doap-perl

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #946771 in librdf-doap-perl 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/perl-team/modules/packages/librdf-doap-perl/-/commit/4cfb301ac587b2a49bd03a65ae1d7759704d4e63


avoid failing autopkgtest-pkg-perl voodoo; closes: bug#946771, thanks to gregor 
herrmann


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/946771

Processed: Bug#946771 marked as pending in librdf-doap-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #946771 [src:librdf-doap-perl] librdf-doap-perl: autopkgtest failure
Added tag(s) pending.

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

Processed: severity of 936612 is serious

[Debian Bug Tracking System]

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

> severity 936612 serious
Bug #936612 [src:gimp-plugin-registry] gimp-plugin-registry: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 937103 is serious

[Debian Bug Tracking System]

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

> severity 937103 serious
Bug #937103 [src:nagios-plugins-contrib] nagios-plugins-contrib: Python2 
removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 954673 - sid
Bug #954673 {Done: Lev Lamberov } [src:swi-prolog] 
swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
Removed tag(s) sid.
> tags 954673 - bullseye
Bug #954673 {Done: Lev Lamberov } [src:swi-prolog] 
swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
Removed tag(s) bullseye.
> notfound 954673 8.0.3+dfsg-1
Bug #954673 {Done: Lev Lamberov } [src:swi-prolog] 
swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
No longer marked as found in versions swi-prolog/8.0.3+dfsg-1.
> notfound 954673 8.1.26+dfsg-2
Bug #954673 {Done: Lev Lamberov } [src:swi-prolog] 
swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
Ignoring request to alter found versions of bug #954673 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#954673: marked as done (swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 20:56:22 +0500
with message-id <87h7y319p5.fsf@localhost>
and subject line 
has caused the Debian Bug report #954673,
regarding swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes 
of inactivity
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.)


-- 
954673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swi-prolog
Version: 8.0.3+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> 49:   test cert_mismatch: wrong answer (compared using ==)
> 49: ERROR: Expected: 'key values mismatch'
> 49: ERROR: Got:  'ee key too small'
> 49: ..
> 49: ERROR: /<>/packages/ssl/test_ssl.pl:229:
> 49:   test missing_key: wrong answer (compared using ==)
> 49: ERROR: Expected: 'no private key assigned'
> 49: ERROR: Got:  'ee key too small'
> 49: ERROR: /<>/packages/ssl/test_ssl.pl:232:
> 49:   test missing_key: wrong answer (compared using ==)
> 49: ERROR: Expected: 'no private key assigned'
> 49: ERROR: Got:  'ee key too small'
> 49:  done
> 49: % PL-Unit: ssl_server Client error:
> 49: ERROR: read_util:read_line_to_codes/2: I/O error in read on stream 
> (0x559e81f70860) (Success)
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/swi-prolog_8.0.3+dfsg-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
It was a bug in openssl which is now fixed in openssl 1.1.1f. So,
closing this bug report.

Regards,
Lev--- End Message ---

Bug#954626: marked as done (libnet-server-mail-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Wed, 1 Apr 2020 17:24:42 +0200
with message-id <20200401152442.ga1...@jadzia.comodo.priv.at>
and subject line Re: Bug#954626: libnet-server-mail-perl: FTBFS: dh_auto_test: 
error: make -j4 test TEST_VERBOSE=1 returned exit code 2
has caused the Debian Bug report #954626,
regarding libnet-server-mail-perl: FTBFS: dh_auto_test: error: make -j4 test 
TEST_VERBOSE=1 returned exit code 2
to be marked as done.

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

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


-- 
954626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnet-server-mail-perl
Version: 0.28-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/esmtp.t . 
> 1..10
> ok 1 - use Net::Server::Mail::ESMTP;
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10
> ok
> t/lmtp.t .. 
> 1..10
> ok 1 # skip You don't seem to have Net::LMTP installed on your system
> ok 2 # skip You don't seem to have Net::LMTP installed on your system
> ok 3 # skip You don't seem to have Net::LMTP installed on your system
> ok 4 # skip You don't seem to have Net::LMTP installed on your system
> ok 5 # skip You don't seem to have Net::LMTP installed on your system
> ok 6 # skip You don't seem to have Net::LMTP installed on your system
> ok 7 # skip You don't seem to have Net::LMTP installed on your system
> ok 8 # skip You don't seem to have Net::LMTP installed on your system
> ok 9 # skip You don't seem to have Net::LMTP installed on your system
> ok 10 # skip You don't seem to have Net::LMTP installed on your system
> ok
> t/smtp.t .. 
> 1..10
> ok 1 - use Net::Server::Mail::SMTP;
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10
> ok
> # Error: Can't call method "peerhost" on an undefined value at t/starttls.t 
> line 131.
> # kill 9, 2163 (server)
> t/starttls.t .. 
> ok 1 - Accepted client for Test01: STARTTLS support
> ok 2 - Accepted client for Test02: STARTTLS invalid parameters
> ok 3 - Accepted client for Test03: STARTTLS handshake
> All 3 subtests passed 
> 
> Test Summary Report
> ---
> t/starttls.t (Wstat: 13 Tests: 3 Failed: 0)
>   Non-zero wait status: 13
>   Parse errors: No plan found in TAP output
> Files=4, Tests=33,  2 wallclock secs ( 0.02 usr  0.00 sys +  0.30 cusr  0.06 
> csys =  0.38 CPU)
> Result: FAIL
> Failed 1/4 test programs. 0/33 subtests failed.
> make[1]: *** [Makefile:861: test_dynamic] Error 255
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/21/libnet-server-mail-perl_0.28-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On Sun, 22 Mar 2020 12:21:39 +0100, gregor herrmann wrote:

> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.

> Confirmed.
> Probably related to OpenSSL 1.1.1e / #954371 (libio-socket-ssl-perl).

Indeed, with OpenSSL 1.1.1f / #954371 fixed is builds again.

As there's nothing we can do in _this_ package, I'm closing the bug.

Cheers,
gregor

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


signature.asc
Description: Digital Signature
--- End Message ---

Bug#944592: marked as done (FTBFS with OCaml 4.08.1 (safe strings))

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 15:11:44 +
with message-id 
and subject line Bug#944592: fixed in ocaml-deriving-ocsigen 0.7.1-1.1
has caused the Debian Bug report #944592,
regarding FTBFS with OCaml 4.08.1 (safe strings)
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.)


-- 
944592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ocaml-deriving-ocsigen
Version: 0.7.1-1
Severity: serious
Tags: ftbfs
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.08-transition

Dear Maintainer,

ocaml-deriving-ocsigen FTBFS with OCaml 4.08.1 because -safe-string is
the default now:

  https://buildd.debian.org/status/package.php?p=ocaml-deriving-ocsigen


Cheers,

-- 
Stéphane

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: ocaml-deriving-ocsigen
Source-Version: 0.7.1-1.1
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
ocaml-deriving-ocsigen, 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.
Gianfranco Costamagna  (supplier of updated 
ocaml-deriving-ocsigen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 16:30:46 +0200
Source: ocaml-deriving-ocsigen
Binary: libderiving-ocsigen-ocaml-dev libderiving-ocsigen-ocaml
Architecture: source
Version: 0.7.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Gianfranco Costamagna 
Description:
 libderiving-ocsigen-ocaml - deriving functions from type declarations in OCaml 
(runtime)
 libderiving-ocsigen-ocaml-dev - deriving functions from type declarations in 
OCaml (devt files)
Closes: 944592
Changes:
 ocaml-deriving-ocsigen (0.7.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Dimitri John Ledkov  ]
   * Cherrypick upstream patch to fix ftbfs with new ocaml (Closes: #944592).
   * Add libnum-ocaml-dev dependency
Checksums-Sha1:
 49618237807b45790502373589a7ca9a23ebff59 2373 
ocaml-deriving-ocsigen_0.7.1-1.1.dsc
 19a4b3ed1f5a80dc3ff35f2df381453d259ec2ba 4684 
ocaml-deriving-ocsigen_0.7.1-1.1.debian.tar.xz
 1e99a924a35b8a9244181d8ba95f9d619d37e2ef 7647 
ocaml-deriving-ocsigen_0.7.1-1.1_source.buildinfo
Checksums-Sha256:
 f8d707c42d2b92fb03fcd4d58d888319ee3cfd83495c7440f93124ea65cf2454 2373 
ocaml-deriving-ocsigen_0.7.1-1.1.dsc
 b7784e31d918b79441ac56ab80a356a3adee9c3f2ef4b7825c8a4c73471fdc13 4684 
ocaml-deriving-ocsigen_0.7.1-1.1.debian.tar.xz
 fe1c60f73813162d7a9c4c339dc00aa54c7235390ea63e31d3ab305dd828 7647 
ocaml-deriving-ocsigen_0.7.1-1.1_source.buildinfo
Files:
 37346146b800c1e89e25728240d05f91 2373 ocaml optional 
ocaml-deriving-ocsigen_0.7.1-1.1.dsc
 115e2dbb9aacd4ce119529ad8e1a0af4 4684 ocaml optional 
ocaml-deriving-ocsigen_0.7.1-1.1.debian.tar.xz
 cad73047e11bdad783b26e917e36d5cf 7647 ocaml optional 
ocaml-deriving-ocsigen_0.7.1-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl6EpeEACgkQ808JdE6f
XdlSxg/6Arc4H1sIbdsHpAhiAtO9wpKXqheCo1WnB7XjmlU75CejSyfqo2Xex1W4
UXkXMmAhfFmEvr18j6fvYzTtdPt8kZWFFnsmSN2OwJe/MgiPuHwww5gh6Bvd7y6r
Rya3kh9HPupPSD5ccKuYMK+t4bkAXnKlvoWHD0YYxeepaznJDvbj+9N9SrhCrO+1
YNQBO09F0fhprQslh/MjIyjHJXp1WRd65+qWQ3SP3X+j8qonaMNBmrYVJJ4vovpE
Rv3EqKb5ib3GnJvEA/nQ/6H3OUNbGR74CtpGMc99lGyw5r6V8BnTCDDSfHnTFUwg
TZbF1QbkV2gDn9pxq/auTl+sOEJMJ+WqDtWWiDqjlmoZz7jzp6wqGz6hOsDaBcpm
IuxaomG8ZfhGn9hu06DJc0nDjyE2yYPKCdNjQz/XUSFryjYQmKku3MF2325WKEXn
63VJsaYFOZI2xRzLBAA3l21rC4b1bjLf2NzqeBm5jLZ226t7+hapPmcQHXufi536
+ptjH+Yldggot6Swt2H5kjs+GDZ0YRlbnMEDfwWW4cUn7g3DDPCwAZHddquvbYwR

Processed: Re: [Pkg-libvirt-maintainers] Bug#955490: libvirt-daemon: ERROR internal error: child reported (status=125): Kernel does not provide mount namespace: Permission denied

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #955490 [libvirt-daemon] libvirt-daemon: ERRORinternal error: child 
reported (status=125): Kernel does not provide mount namespace: Permission 
denied
Severity set to 'normal' from 'grave'

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

Bug#955490: [Pkg-libvirt-maintainers] Bug#955490: libvirt-daemon: ERROR internal error: child reported (status=125): Kernel does not provide mount namespace: Permission denied

[Guido Günther]

control: severity -1 normal

Hi,
On Wed, Apr 01, 2020 at 04:39:34PM +0200, usuario wrote:
> Package: libvirt-daemon
> Version: 6.0.0-4
> Severity: grave
> Tags: a11y
> Justification: renders package unusable

certainly not unusable since others ore running just fine.
 -- Guido

> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
> sudo virt-install \
> -n vm1 \
> -r 512 \
> --vcpus=2 \
> --os-variant=debiantesting \
> --disk /var/lib/libvirt/images/vm1.img,size=2 \
> --nographics \
> -l http://ftp.debian.org/debian/dists/testing/main/installer-amd64/ \
> -x console=ttyS0,115200
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Launch above command
> 
>* What was the outcome of this action?
> 
> Below error:
> 
> ERRORinternal error: child reported (status=125): Kernel does not provide 
> mount namespace: Permission denied
> 
>* What outcome did you expect instead?
> 
> A success message confirming I'm able to install the Virtual Machine
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_GB:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libvirt-daemon depends on:
> ii  libblkid1   2.34-0.1
> ii  libc6   2.30-2
> ii  libcap-ng0  0.7.9-2.1+b2
> ii  libdbus-1-3 1.12.16-2
> ii  libdevmapper1.02.1  2:1.02.167-1+b1
> ii  libfuse22.9.9-3
> ii  libgcc-s1   10-20200324-1
> ii  libglib2.0-02.64.1-1
> ii  libnetcf1   1:0.2.8-1+b3
> ii  libparted2  3.3-4
> ii  libpcap0.8  1.9.1-2
> ii  libpciaccess0   0.14-1
> ii  libselinux1 3.0-1+b1
> ii  libudev1244.3-1
> ii  libvirt-daemon-driver-qemu  6.0.0-4
> ii  libvirt06.0.0-4
> ii  libxml2 2.9.10+dfsg-4
> 
> Versions of packages libvirt-daemon recommends:
> ii  libvirt-daemon-driver-lxc   6.0.0-4
> ii  libvirt-daemon-driver-vbox  6.0.0-4
> ii  libvirt-daemon-driver-xen   6.0.0-4
> ii  libxml2-utils   2.9.10+dfsg-4
> ii  netcat-openbsd  1.206-1
> ii  qemu-kvm1:4.2-3
> 
> Versions of packages libvirt-daemon suggests:
> pn  libvirt-daemon-driver-storage-gluster  
> pn  libvirt-daemon-driver-storage-rbd  
> pn  libvirt-daemon-driver-storage-zfs  
> ii  libvirt-daemon-system  6.0.0-4
> pn  numad  
> 
> -- debconf-show failed
> 
> ___
> Pkg-libvirt-maintainers mailing list
> pkg-libvirt-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers

Processed: Re: FTBFS with OCaml 4.08.1 (safe strings)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #944592 [src:ocaml-deriving-ocsigen] FTBFS with OCaml 4.08.1 (safe strings)
Added tag(s) patch and pending.

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

Bug#944592: FTBFS with OCaml 4.08.1 (safe strings)

[Gianfranco Costamagna]

control: tags -1 patch pending

diff uploaded

G.

On Tue, 12 Nov 2019 10:22:55 +0100 =?utf-8?q?St=C3=A9phane_Glondu?= 
 wrote:
> Package: src:ocaml-deriving-ocsigen
> Version: 0.7.1-1
> Severity: serious
> Tags: ftbfs
> User: debian-ocaml-ma...@lists.debian.org
> Usertags: ocaml-4.08-transition
> 
> Dear Maintainer,
> 
> ocaml-deriving-ocsigen FTBFS with OCaml 4.08.1 because -safe-string is
> the default now:
> 
>   https://buildd.debian.org/status/package.php?p=ocaml-deriving-ocsigen
> 
> 
> Cheers,
> 
> -- 
> Stéphane
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
> LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
diff -Nru ocaml-deriving-ocsigen-0.7.1/debian/changelog 
ocaml-deriving-ocsigen-0.7.1/debian/changelog
--- ocaml-deriving-ocsigen-0.7.1/debian/changelog   2016-08-03 
16:27:18.0 +0200
+++ ocaml-deriving-ocsigen-0.7.1/debian/changelog   2020-04-01 
16:30:46.0 +0200
@@ -1,3 +1,13 @@
+ocaml-deriving-ocsigen (0.7.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Dimitri John Ledkov  ]
+  * Cherrypick upstream patch to fix ftbfs with new ocaml (Closes: #944592).
+  * Add libnum-ocaml-dev dependency
+
+ -- Gianfranco Costamagna   Wed, 01 Apr 2020 
16:30:46 +0200
+
 ocaml-deriving-ocsigen (0.7.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru ocaml-deriving-ocsigen-0.7.1/debian/control 
ocaml-deriving-ocsigen-0.7.1/debian/control
--- ocaml-deriving-ocsigen-0.7.1/debian/control 2016-08-03 16:26:27.0 
+0200
+++ ocaml-deriving-ocsigen-0.7.1/debian/control 2020-04-01 16:30:43.0 
+0200
@@ -11,6 +11,7 @@
   debhelper (>= 9),
   libtype-conv-camlp4-dev (>= 108),
   liboptcomp-camlp4-dev,
+  libnum-ocaml-dev,
   oasis (>= 0.4.5),
   camlp4-extra
 Standards-Version: 3.9.8
diff -Nru 
ocaml-deriving-ocsigen-0.7.1/debian/patches/df07e7150f4d196720fa6b44a289783ae9168810.patch
 
ocaml-deriving-ocsigen-0.7.1/debian/patches/df07e7150f4d196720fa6b44a289783ae9168810.patch
--- 
ocaml-deriving-ocsigen-0.7.1/debian/patches/df07e7150f4d196720fa6b44a289783ae9168810.patch
  1970-01-01 01:00:00.0 +0100
+++ 
ocaml-deriving-ocsigen-0.7.1/debian/patches/df07e7150f4d196720fa6b44a289783ae9168810.patch
  2020-04-01 16:30:43.0 +0200
@@ -0,0 +1,82 @@
+From df07e7150f4d196720fa6b44a289783ae9168810 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Daniel=20Hillerstr=C3=B6m?= 
+Date: Tue, 14 Nov 2017 19:56:45 +
+Subject: [PATCH] Since OCaml 4.06.0 (-safe-string option) bytes and strings
+ cannot be used interchangeably. This patch fixes the code base such that the
+ modules Bytes and String (and hence types bytes and string) are no longer
+ used interchangeably.
+
+---
+ lib/deriving_Dump.ml | 7 ---
+ lib/deriving_interned.ml | 9 +
+ syntax/common/utils.ml   | 2 +-
+ 3 files changed, 10 insertions(+), 8 deletions(-)
+
+diff --git a/lib/deriving_Dump.ml b/lib/deriving_Dump.ml
+index 13e356f..9bafe3d 100644
+--- a/lib/deriving_Dump.ml
 b/lib/deriving_Dump.ml
+@@ -142,7 +142,7 @@ module Dump_string = Defaults (
+ for i = 0 to len - 1 do
+   Bytes.unsafe_set s i (Stream.next stream)
+ done;
+-s
++Bytes.to_string s
+   end
+ )
+ 
+@@ -241,7 +241,8 @@ module Dump_via_marshal (P : sig type a end) = Defaults (
+   struct
+ include P
+ let to_buffer buffer obj = Buffer.add_string buffer (Marshal.to_string 
obj [Marshal.Closures])
+-let from_stream stream = 
++let from_stream stream =
++  let to_string bs = Bytes.to_string bs in
+   let readn n = 
+ let s = Bytes.create n in
+ for i = 0 to n - 1 do
+@@ -252,5 +253,5 @@ module Dump_via_marshal (P : sig type a end) = Defaults (
+   let header = readn Marshal.header_size in
+   let datasize = Marshal.data_size header 0 in
+   let datapart = readn datasize in
+-Marshal.from_string (header ^ datapart) 0
++Marshal.from_string ((to_string header) ^ (to_string datapart)) 0
+   end)
+diff --git a/lib/deriving_interned.ml b/lib/deriving_interned.ml
+index d53bcc7..88aad8f 100644
+--- a/lib/deriving_interned.ml
 b/lib/deriving_interned.ml
+@@ -14,15 +14,16 @@ type t = int * string
+ deriving (Show)
+ 
+ let intern s =
+-  try BytesMap.find s !map
++  let bs = Bytes.of_string s in
++  try BytesMap.find bs !map
+   with Not_found ->
+-let fresh = (!counter, Bytes.of_string s) in begin
+-  map := BytesMap.add s fresh !map;
++let fresh = (!counter, s) in begin
++  map := BytesMap.add bs fresh !map;
+   incr counter;
+   fresh
+ end
+ 
+-let to_string (_,s) = Bytes.to_string s
++let to_string (_,s) = s
+ let name 

Bug#955490: libvirt-daemon: ERROR internal error: child reported (status=125): Kernel does not provide mount namespace: Permission denied

[usuario]

Package: libvirt-daemon
Version: 6.0.0-4
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

sudo virt-install \
-n vm1 \
-r 512 \
--vcpus=2 \
--os-variant=debiantesting \
--disk /var/lib/libvirt/images/vm1.img,size=2 \
--nographics \
-l http://ftp.debian.org/debian/dists/testing/main/installer-amd64/ \
-x console=ttyS0,115200

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Launch above command

   * What was the outcome of this action?

Below error:

ERRORinternal error: child reported (status=125): Kernel does not provide 
mount namespace: Permission denied

   * What outcome did you expect instead?

A success message confirming I'm able to install the Virtual Machine

*** End of the template - remove these template lines ***


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

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

Versions of packages libvirt-daemon depends on:
ii  libblkid1   2.34-0.1
ii  libc6   2.30-2
ii  libcap-ng0  0.7.9-2.1+b2
ii  libdbus-1-3 1.12.16-2
ii  libdevmapper1.02.1  2:1.02.167-1+b1
ii  libfuse22.9.9-3
ii  libgcc-s1   10-20200324-1
ii  libglib2.0-02.64.1-1
ii  libnetcf1   1:0.2.8-1+b3
ii  libparted2  3.3-4
ii  libpcap0.8  1.9.1-2
ii  libpciaccess0   0.14-1
ii  libselinux1 3.0-1+b1
ii  libudev1244.3-1
ii  libvirt-daemon-driver-qemu  6.0.0-4
ii  libvirt06.0.0-4
ii  libxml2 2.9.10+dfsg-4

Versions of packages libvirt-daemon recommends:
ii  libvirt-daemon-driver-lxc   6.0.0-4
ii  libvirt-daemon-driver-vbox  6.0.0-4
ii  libvirt-daemon-driver-xen   6.0.0-4
ii  libxml2-utils   2.9.10+dfsg-4
ii  netcat-openbsd  1.206-1
ii  qemu-kvm1:4.2-3

Versions of packages libvirt-daemon suggests:
pn  libvirt-daemon-driver-storage-gluster  
pn  libvirt-daemon-driver-storage-rbd  
pn  libvirt-daemon-driver-storage-zfs  
ii  libvirt-daemon-system  6.0.0-4
pn  numad  

-- debconf-show failed

Bug#952026: More information

[Daniel Leidert]

I debugged this case and looked into the FTBFS of ruby-handlebas-assets. I
checked out the upstream git repository and it tests just fine even when I
raise the haml and rake gem versions to match the ones in Debian. But it fails
with exactly the same error if I replace the javascript files in
vendor/assets/javascript by the javascript files provided by libjs-handlebars.
So there seems to be some incompatbility or difference with these files
actually causing the build issue (and I don't believe it's the version
difference of 4.7.2 vs 4.7.3).

Regards, Daniel


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

Processed: retitle 952026 to ruby-handlebars-assets: FTBFS with current libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not defined

[Debian Bug Tracking System]

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

> retitle 952026 ruby-handlebars-assets: FTBFS with current libjs-handlebars 
> version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not 
> defined
Bug #952026 [src:ruby-handlebars-assets] ruby-handlebars-assets: FTBFS: ERROR: 
Test "ruby2.5" failed: Invalid gemspec in [handlebars_assets.gemspec]: No such 
file or directory - git
Changed Bug title to 'ruby-handlebars-assets: FTBFS with current 
libjs-handlebars version: ERROR: ExecJS::ProgramError: ReferenceError: 
Handlebars is not defined' from 'ruby-handlebars-assets: FTBFS: ERROR: Test 
"ruby2.5" failed: Invalid gemspec in [handlebars_assets.gemspec]: No such file 
or directory - git'.
> thanks
Stopping processing here.

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

Bug#955488: nat-rtsp-dkms: Does not build with kernel >= 5.3

[Adrien]

Package: nat-rtsp-dkms
Version: 0.7+4.18-0.1
Severity: grave
Justification: renders package unusable

Hi,

There is a new package on upstream, that should fix this.

However, it renders the package unusable with current kernel.

Thanks for this package,

Adrien

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

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

Versions of packages nat-rtsp-dkms depends on:
ii  dkms  2.8.1-5

nat-rtsp-dkms recommends no packages.

nat-rtsp-dkms suggests no packages.

-- no debconf information

Bug#943068: marked as done (iptables-converter: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 13:33:41 +
with message-id 
and subject line Bug#943068: fixed in iptables-converter 0.9.8-1.1
has caused the Debian Bug report #943068,
regarding iptables-converter: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
943068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iptables-converter
Version: 0.9.8-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

We believe that the bug you reported is fixed in the latest version of
iptables-converter, 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.
Thomas Goirand  (supplier of updated iptables-converter 
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: Sun, 22 Mar 2020 13:01:11 +0100
Source: iptables-converter
Binary: iptables-converter iptables-converter-doc
Architecture: source all
Version: 0.9.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Johannes Hubertz 
Changed-By: Thomas Goirand 
Description:
 iptables-converter - convert iptables-commands from a file to iptables-save 
format
 iptables-converter-doc - convert iptables-commands from a file to 
iptables-save format - d
Closes: 805459 943068
Changes:
 iptables-converter (0.9.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch the package to Python 3 (Closes: #943068):
 - Remove obsolete X-Python-Version:.
 - Replaced python2 direct depends by ${python3:Depends}.
 - Removed python2 build-depends, replaced python3 build-depends by a
   python3-all build-depends.
 - Use python3 to build the sphinx doc.
   * Ran wrap-and-sort -bastk.
   * Fixed the package descriptions (Closes: #805459).
   * Removed useless overrides.
   * Switched to debhelper-compat = 12.
   * 

Bug#952093: marked as done (sumaclust: FTBFS: mtcompare_sumaclust.c:18:10: fatal error: libfasta/sequence.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 13:18:58 +
with message-id 
and subject line Bug#952093: fixed in sumaclust 1.0.34-2
has caused the Debian Bug report #952093,
regarding sumaclust: FTBFS: mtcompare_sumaclust.c:18:10: fatal error: 
libfasta/sequence.h: No such file or directory
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.)


-- 
952093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sumaclust
Version: 1.0.34-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> gcc -O3 -w -c -o libfasta/fasta_seq_writer.o libfasta/fasta_seq_writer.c 
> mtcompare_sumaclust.c:18:10: fatal error: libfasta/sequence.h: No such file 
> or directory
>18 | #include "libfasta/sequence.h"
>   |  ^
> compilation terminated.
> make[1]: *** [global.mk:20: mtcompare_sumaclust.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/sumaclust_1.0.34-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: sumaclust
Source-Version: 1.0.34-2
Done: Andreas Tille 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 14:45:13 +0200
Source: sumaclust
Architecture: source
Version: 1.0.34-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 952093 954262
Changes:
 sumaclust (1.0.34-2) unstable; urgency=medium
 .
   * Fix Build
 Closes: #952093, #954262
   * Polish watch file
   * Standards-Version: 4.5.0 (routine-update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
Checksums-Sha1:
 021797f101fe1461d8ff80dc373ebd902c589f7e 1987 sumaclust_1.0.34-2.dsc
 c1615825a8e98edfd1abf25e6d2be271b93cf1c0 10380 sumaclust_1.0.34-2.debian.tar.xz
 951759461619f0a5f62007888979c572a5fdeb28 5741 
sumaclust_1.0.34-2_amd64.buildinfo
Checksums-Sha256:
 af606f84839f4d08a9ba252b15dcc962008b83fbeceedcb94bf85c9ec009fd96 1987 
sumaclust_1.0.34-2.dsc
 6d503df602bb9c5f48d711a8c016864b65c86d254b4e84c5ff85d206d30c0956 10380 
sumaclust_1.0.34-2.debian.tar.xz
 bae5d6333e361d5356b6f13d235a0a9c000646df2c94271ed6795edd1a58 5741 
sumaclust_1.0.34-2_amd64.buildinfo
Files:
 482f6e208f78fd54903bc9e80def66b0 1987 science optional sumaclust_1.0.34-2.dsc
 9013a8ae323e59cf7de30ce8184cc8b2 10380 science optional 
sumaclust_1.0.34-2.debian.tar.xz
 dc499af86cbb195016389922b3a75c6a 5741 science optional 
sumaclust_1.0.34-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl6EjhcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE1VhAAhIHWh/jY9HSq28nW5rSLoe4f5Q2/ULYU
SkV4IkzduWnuNmJ8AdTvlmnAg+QALoaSfp8adzLoe1+QXZscNhXqDNCkc5qjhN9V
WEVRYMiQJL8z6gluH8H37lukG9IW9RXDKWdF9pOu8gEQPPTKc0KSzRZMZ01Kjbn9
VYwGCKWvfTwDruCL2EVvPm4duZwmxxC9LNYEl8lCpSS0j1uaxFxzZo9LO9n6HyAO
tPTXwIObVbqquE1GBiJ0vP/cIFWMEaNhuTXF6FfurGMmnNDJlUR18BAgueWX4brr
ysiqv/IIZZQkuK3kE4/CiKCH2yg9PhoO+ukQVBBH2BJXv3Dsbr/vCTrVVZ/6xUfR
CzQR5nw15rD47LU0ANhmF2bofa0VttTDJgAWMn4ye/cfiUgYLa41O7Ed6/wd6UEB
aOGPMSk/5L+u9dZgCBzfLEIuGjhT3FFkMjGPSop723jRUr6GsmxWzhshgnOV226C
rHgn+y6AYz3umnl7TUBH4vwzJSdeinzT3d5rVesV0GsajlgPNa61SOpW3qli/DoL
Jpt1OmmL8SWQFWxgIw0VlaYE/vDb3eT7V7ardpGh4thqFwCGjXVepqvMyjC1zbPI
fpaaMIDiUmStM5JppmULt+yeUZ5AS7BYJ9+bWk3INqJ3WcMjye+cFnE4VxnXGYgg
PfhiUpTpbZY=
=jYSj
-END PGP 

Bug#954262: marked as done (src:sumaclust: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 13:18:58 +
with message-id 
and subject line Bug#954262: fixed in sumaclust 1.0.34-2
has caused the Debian Bug report #954262,
regarding src:sumaclust: fails to migrate to testing for too long
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.)


-- 
954262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sumaclust
Version: 1.0.31-2
Severity: serious
Control: fixed -1 1.0.34-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:sumaclust in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=sumaclust




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sumaclust
Source-Version: 1.0.34-2
Done: Andreas Tille 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Apr 2020 14:45:13 +0200
Source: sumaclust
Architecture: source
Version: 1.0.34-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 952093 954262
Changes:
 sumaclust (1.0.34-2) unstable; urgency=medium
 .
   * Fix Build
 Closes: #952093, #954262
   * Polish watch file
   * Standards-Version: 4.5.0 (routine-update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
Checksums-Sha1:
 021797f101fe1461d8ff80dc373ebd902c589f7e 1987 sumaclust_1.0.34-2.dsc
 c1615825a8e98edfd1abf25e6d2be271b93cf1c0 10380 sumaclust_1.0.34-2.debian.tar.xz
 951759461619f0a5f62007888979c572a5fdeb28 5741 
sumaclust_1.0.34-2_amd64.buildinfo
Checksums-Sha256:
 af606f84839f4d08a9ba252b15dcc962008b83fbeceedcb94bf85c9ec009fd96 1987 
sumaclust_1.0.34-2.dsc
 6d503df602bb9c5f48d711a8c016864b65c86d254b4e84c5ff85d206d30c0956 10380 
sumaclust_1.0.34-2.debian.tar.xz
 bae5d6333e361d5356b6f13d235a0a9c000646df2c94271ed6795edd1a58 5741 
sumaclust_1.0.34-2_amd64.buildinfo
Files:
 482f6e208f78fd54903bc9e80def66b0 1987 science optional sumaclust_1.0.34-2.dsc
 9013a8ae323e59cf7de30ce8184cc8b2 10380 science optional 
sumaclust_1.0.34-2.debian.tar.xz
 dc499af86cbb195016389922b3a75c6a 5741 science optional 
sumaclust_1.0.34-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl6EjhcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE1VhAAhIHWh/jY9HSq28nW5rSLoe4f5Q2/ULYU
SkV4IkzduWnuNmJ8AdTvlmnAg+QALoaSfp8adzLoe1+QXZscNhXqDNCkc5qjhN9V

Bug#954511: marked as done (bioperl-run: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 255)

[Debian Bug Tracking System]

Your message dated Wed, 01 Apr 2020 13:18:33 +
with message-id 
and subject line Bug#954511: fixed in bioperl-run 1.7.3-4
has caused the Debian Bug report #954511,
regarding bioperl-run: FTBFS: dh_auto_test: error: perl Build test --verbose 1 
returned exit code 255
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.)


-- 
954511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bioperl-run
Version: 1.7.3-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir t.skip
> for t in Blat Eponine Glimmer2 Gumby RepeatMasker Phyml Hyphy BWA MCS ; do mv 
> t/${t}.t t.skip ; done
> mv: cannot stat 't/Gumby.t': No such file or directory
> mv: cannot stat 't/BWA.t': No such file or directory
> PATH=$PATH:/usr/lib/emboss:/usr/lib/phylip/bin/:/usr/lib/tigr-glimmer:debian/test_hack_bin
>  \
> HOME_4_TCOFFEE=/tmp COILSDIR=/usr/share/ncoils/ \
> dh_auto_test --no-parallel
>   perl Build test --verbose 1
> 
> AMAP version AMAP.2.2 - align multiple protein sequences and print to 
> standard output
> PROBCONS Written by Chuong Do
> AMAP algorithm implemented by Ariel Schwartz
> 
> Using parameter set:
> initDistrib[] = { 0.40006 0.300119 0.300119 }
> gapOpen[] = { 0.01993141696 0.01993141696 }
>   gapExtend[] = { 0.7943345308 0.7943345308 }
> 
> Loading sequence file: t/data/cysprot.fa
> Computing posterior matrices
> Building DAG
> Starting the sequence annealing process
> Creating candidate edge list
> Adding edges to the DAG
> 
> AMAP version AMAP.2.2 - align multiple protein sequences and print to 
> standard output
> PROBCONS Written by Chuong Do
> AMAP algorithm implemented by Ariel Schwartz
> 
> Using parameter set:
> initDistrib[] = { 0.40006 0.300119 0.300119 }
> gapOpen[] = { 0.01993141696 0.01993141696 }
>   gapExtend[] = { 0.7943345308 0.7943345308 }
> 
> Loading sequence file: /tmp/ftWO42xDDD
> Computing posterior matrices
> Building DAG
> Starting the sequence annealing process
> Creating candidate edge list
> Adding edges to the DAG
> t/Amap.t .. 
> 1..18
> ok 1 - use Bio::Tools::Run::Alignment::Amap;
> ok 2 - use Bio::SeqIO;
> ok 3 - use File::Spec;
> ok 4 - Found input file
> ok 5 - An object of class 'Bio::Tools::Run::Alignment::Amap' isa 
> 'Bio::Tools::Run::Alignment::Amap'
> ok 6 - program_dir returned correct default
> ok 7 - error_string returned correct default
> ok 8 - aformat returned correct default
> ok 9 - outfile_name returned correct default
> ok 10 - Correct exe default name
> ok 11 - Correct minimum program version
> ok 12 - No error occured
> ok 13 - outfile_name returned something
> ok 14 - An object of class 'Bio::SimpleAlign' isa 'Bio::SimpleAlign'
> ok 15 - Correct number of seqs returned
> ok 16 - An object of class 'Bio::SimpleAlign' isa 'Bio::SimpleAlign'
> ok 17 - Correct number of seqs returned
> ok 18 - Got the correct ave % identity
> ok
> t/BEDTools.t .. skipped: The optional module 
> Bio::Tools::Run::BEDTools (or dependencies thereof) was not installed
> # You named your test '71'.  You shouldn't use numbers for your test 
> names.
> # Very confusing.
> # You named your test '91'.  You shouldn't use numbers for your test 
> names.
> # Very confusing.
> t/Coil.t .. 
> 1..6
> ok 1 - use Bio::Tools::Run::Coil;
> ok 2 - use Bio::SeqIO;
> ok 3
> ok 4
> ok 5 - 71
> ok 6 - 91
> ok
> t/Consense.t .. 
> 1..8
> ok 1 - use Bio::Tools::Run::Phylo::Phylip::Consense;
> ok 2 - use Bio::AlignIO;
> ok 3 - An object of class 'Bio::Tools::Run::Phylo::Phylip::Consense' isa 
> 'Bio::Tools::Run::Phylo::Phylip::Consense'
> ok 4 - could not set rooted option
> consense: can't find input tree file "intree"
> Please enter a new file name> 
> 
> Consensus tree program, version 3.697
> 
> Settings for this run:
>  C Consensus type (MRe, strict, MR, Ml):  Majority rule (extended)
>  OOutgroup root:  No, use as outgroup species 
>  1
>  RTrees to be treated as Rooted:  No
>  T   Terminal type (IBM PC, ANSI, none):  ANSI
>  1Print out the sets of species:  Yes
>  2 Print indications of progress of run:  Yes
>  3   Print out tree:  Yes
>  4  

Bug#944424: closed by Debian FTP Masters (reply to Nobuhiro Iwamatsu ) (Bug#944424: fixed in cairo-dock-plug-ins 3.4.1-6)

[Ricardo Mones]

On Wed, Apr 01, 2020 at 07:51:07AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:cairo-dock-plug-ins package:
> 
> #944424: cairo-dock-plug-ins: libetpan 1.9.4 uses now pkg-config
> 
> It has been closed by Debian FTP Masters  
> (reply to Nobuhiro Iwamatsu ).

Thank you!

best regards,
-- 
  Ricardo Mones 
  ~
  I'm sorry, my responses are limited. You must ask the right 
  questions.   A hologram



signature.asc
Description: PGP signature

Bug#955346: rabbitcs-thunar: Don't depend on thunarx-python (python2)

[Jeremy Bicha]

I think this fix is a bit wrong. I don't think rabbitvcs-thunar does
anything useful without the Python package.

apt will keep a recommended removed package installed upon upgrade,
but the removed package cannot receive security or bugfix updates. The
package is unsupported and we shouldn't encourage users to have
unsupported packages silently kept on upgrade.

I do understand that the NEW queue can be frustrating to deal with, so
as long as the python package is fixed before the Bullseye release,
then I'm ok with this fix for now.

Thanks,
Jeremy Bicha

Bug#955474: [Pkg-samba-maint] Bug#955474: FTBFS: fatal error: stropts.h: No such file or directory

[Andrew Bartlett]

On Wed, 2020-04-01 at 11:18 +0200, Raphaël Hertzog wrote:
> Source: samba
> Version: 2:4.11.5+dfsg-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in
> the past)
> User: de...@kali.org
> Usertags: origin-kali

This is a python bug, it should not be setting HAVE_STROPTS_H.

See bug 954582

-- 
Andrew Bartlett   https://samba.org/~abartlet/
Authentication Developer, Samba Team  https://samba.org
Samba Developer, Catalyst IT  
https://catalyst.net.nz/services/samba