On Fri, 30 Aug 2019 07:28:59 +0000 Matthias Klose <[email protected]> wrote: > Package: src:obitools > Version: 1.2.13+dfsg-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". ...
I don't see any evidence of upstream progress on converting to python3. This package is blocking several others. Would it be best to remove it? It can always be re-introduced if a python3 port appears. Scott K
signature.asc
Description: This is a digitally signed message part.
