Your message dated Sun, 22 Dec 2019 11:36:51 +0000
with message-id <e1iizxx-0007ag...@fasolo.debian.org>
and subject line Bug#938441: fixed in schedule 0.3.2-1.1
has caused the Debian Bug report #938441,
regarding schedule: 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.)


-- 
938441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:schedule
Version: 0.3.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 <bug number of blocking py2removal bug> + src:schedule

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: schedule
Source-Version: 0.3.2-1.1

We believe that the bug you reported is fixed in the latest version of
schedule, 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.
Ondřej Nový <on...@debian.org> (supplier of updated schedule package)

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


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 20 Dec 2019 12:02:21 +0100
Source: schedule
Architecture: source
Version: 0.3.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Donncha O'Cearbhaill <donn...@donncha.is>
Changed-By: Ondřej Nový <on...@debian.org>
Closes: 938441
Changes:
 schedule (0.3.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop Python 2 support (Closes: #938441).
Checksums-Sha1:
 91cdac34dbe00685b7ab80a04f92203db7420a39 1992 schedule_0.3.2-1.1.dsc
 b659593a785c90910b043e676861aee11d6fb581 2228 schedule_0.3.2-1.1.debian.tar.xz
 31b0e701e34850ffa631ca17203c5b446582bbd5 6282 
schedule_0.3.2-1.1_amd64.buildinfo
Checksums-Sha256:
 4ea5dd1f73bd37bf6a78503e7e0a0d5e9b70e0051a48270452c62203b04dd99c 1992 
schedule_0.3.2-1.1.dsc
 166403de5336e6089ac515cdc312fe66b1a1e007b9de785ab8523c5fb4cc63da 2228 
schedule_0.3.2-1.1.debian.tar.xz
 840711b3382044ac1771880c6fb65a73be88be5315f1f42450db36653413c651 6282 
schedule_0.3.2-1.1_amd64.buildinfo
Files:
 ef87dd6607a6adde8b8a772cce084df9 1992 python optional schedule_0.3.2-1.1.dsc
 7e95f43ca7cc2f58799a86a53832fc26 2228 python optional 
schedule_0.3.2-1.1.debian.tar.xz
 6ecd834dac0880e1fe0e73e72087f606 6282 python optional 
schedule_0.3.2-1.1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl38qtsACgkQNXMSVZ0e
BkvFOw/+PrHobmwnh3I5/yiSOPp6kHW6W/nf50Hy8Q2fQRN8nZGy9zT3yyN+aV81
Y2pXDlBMjRTWTP0eYyKtmQsQ/OqfZp5wyLBeTAISK3EAQs7yFyG7vC5n1lfaxOZI
Zjt7f45AO4bPP1VMu3eMCkueRHItUEXwe15rS3ujH5TOHO2HYI+G+v9PeT0agiu7
HMeDdYreEXyi20z/2yJ8xJDVhU7FNbYBoJEb9mJZV4F+b9Oq3PtP5lQVbJNCexWm
Hm/b5wIrAXsiT/SwzoPpmT6W8DclbP5vJsu2rPaimm5E9oQbiEKoTvCqmaLGUoos
/yFIuLFxYPWYVOiPA0JvHMzNiZYjjqQkNMPRNmDlKpIep56C9XtWwMREy9gI9lzZ
gYdQWGyaHSzryz2GYZGW5k4q2Glr7krMNys9eYWK43Eabvka0PUzvwA77FAMTOkW
bjj1/H4s/nkGriXjFbgYP0YkssdZhHtSP8bjCrcsmjAhpCr/oLqPqrp8GUC846Nc
luVxMbY8j3lWbP87VaI6XbGfax59EZ23zFSaE5SuM98k6cQdaDU6/RpsnMmsz3C3
DgM2pnOFhm20yO1s8QBwOHw4Oko+i3cRle1bZgx4xu96asrR1Kbhed5p53lpYCbr
m0/nBuHAY2RK2rnuwK1n0qTBhMtfJmNL7pCdRTyfAq4ksCWFPEs=
=A+Mn
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to