Your message dated Tue, 24 Dec 2019 17:47:40 -0500
with message-id
<CAB4XWXw3r+=APJ8wwEaP2Zjf2zrpo08eN=5b5yuipgipyt9...@mail.gmail.com>
and subject line Re: yagv: Python2 removal in sid/bullseye
has caused the Debian Bug report #938861,
regarding yagv: 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.)
--
938861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:yagv
Version: 0.4~20130422.r5bd15ed+dfsg-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 <bug number of blocking py2removal bug> + src:yagv
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~20171211.r234ef16+dfsg-1
On Fri, 30 Aug 2019 07:59:19 +0000 Matthias Klose <d...@debian.org> wrote:
> Package: src:yagv
> Version: 0.4~20130422.r5bd15ed+dfsg-4
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
https://tracker.debian.org/news/1088912/accepted-yagv-0420171211r234ef16dfsg-1-source-into-unstable/
--- End Message ---
