On Fri, Aug 30, 2019 at 07:55:57AM +0000, Matthias Klose wrote: > Package: src:tnetstring [...] > 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.
There is already a corresponding python3 package, source package name tnetstring3, binary package name python3-tnetstring. When python2 is removed from debian, this package can be removed, as well. However, I'd prefer to keep the package in sid as long as python2 is still there. Therefore, I'm not sure if this option is appropriate: > - 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". I'd prefer an option like this: - Keep the package as long as python2 is in sid, and remove them at the same time. Jan
