Your message dated Sat, 14 Mar 2020 21:11:48 +0000
with message-id <[email protected]>
and subject line Bug#936962: fixed in logbook 1.5.3-3
has caused the Debian Bug report #936962,
regarding logbook: 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 [email protected]
immediately.)


-- 
936962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936962
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:logbook
Version: 1.4.3-1
Severity: normal
Tags: sid bullseye
User: [email protected]
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 [email protected] 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 <bug number of blocking py2removal bug> + src:logbook

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 [email protected] mailing list.

--- End Message ---
--- Begin Message ---
Source: logbook
Source-Version: 1.5.3-3
Done: Sandro Tosi <[email protected]>

We believe that the bug you reported is fixed in the latest version of
logbook, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi <[email protected]> (supplier of updated logbook 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 14 Mar 2020 16:33:37 -0400
Source: logbook
Architecture: source
Version: 1.5.3-3
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze <[email protected]>
Changed-By: Sandro Tosi <[email protected]>
Closes: 936962
Changes:
 logbook (1.5.3-3) unstable; urgency=medium
 .
   * Complete python2 removal, which was done already as a NMU but that the
     maintainer decided to ignore and perform partially; Closes: #936962
Checksums-Sha1:
 ffe84bf924c762dc368dbdd89aa80ca1f3a3073b 2189 logbook_1.5.3-3.dsc
 1a54e746b79d5dd5b0a59ed434e9ba103f62da3a 4480 logbook_1.5.3-3.debian.tar.xz
 1cb8e448df61817a57538be060ca0dfca0f79e53 7518 logbook_1.5.3-3_source.buildinfo
Checksums-Sha256:
 f45e74affb581ac74dabd951a56ed65462686b957de04927ca431cf05254bc95 2189 
logbook_1.5.3-3.dsc
 4f1fabe6875d0858aaf3dc9a38a64a5e3b718d9eb415bc91252cc39a987ed63c 4480 
logbook_1.5.3-3.debian.tar.xz
 26a607cfa1c1c078e8fa46f1aca1b0f2938bec0e7b23a145354c5fb67c41fffd 7518 
logbook_1.5.3-3_source.buildinfo
Files:
 309db13b977c8c66989f5fdee61781c5 2189 python optional logbook_1.5.3-3.dsc
 57f1d29f022263589f002d348da4cd77 4480 python optional 
logbook_1.5.3-3.debian.tar.xz
 9cffc5276b1dccbcc234f50143d7287e 7518 python optional 
logbook_1.5.3-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl5tP9YACgkQh588mTgB
qU9FuBAAk/46clSTB73GBmLUoG2+vL3lBytv8AaQRybsTAWW6gOJDvELvzA9vHzp
14AXSIZEgxFLmQT8j8JZRov7rrMT3suO0Qds62D4DJIMHLhAVYxzHwMcoZDjWwto
O/1MVYK7GsMt0i0QRblwT9X9Boi3kMsNeyLs1CQi/9I0zG5DxHj/MBMtuvf9lxTq
ujy9pWT2g8KnfeJajmE9a/uX0eBh8rh1gD/BkJNrHsoAeF4r8LW+y53QgHRD+/+z
ODFSxHf+bQOf1wQXCPzwTraTJy+YUYK6TJ83mtT7X5EgOQ/iJByj6El4O0TYg+Uz
FzI8S6vfiextlzsWi2ygxVLGgqJ6XAHqvK/cnStj/swI1mkCyDAeOtEuPjHqjgxw
d/VF5Lqdac7iODK+vNTogxbupQtAyjr9Q/FFh8/YbELOT0/Mn/fVzeW7B3/HstZn
978ryOobOp4j3muV2794gUxy/gQ2inHbv1Pwn4raJYG26kSfw5kiP0Jw0q0ytpgZ
5I2KK5yonIYBBPJum9efzcsSxlN9i8teMG29qedQk7Ry1aX9h5/zQ7hb6baZpC5l
3dsteR8dxGKoSBAeIGa1QbozEDSE6mpo7p/xqMZA0MR0JP4BMjSD6fAWoG2bQWJP
3PCEFdsL0vKNgQ6oXPfa3yQOW4IhdBuiW7uagYY28qJxdf6JtwI=
=44No
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to