Your message dated Fri, 06 Sep 2019 01:57:36 -0400 with message-id <3395125.vuouv1UY7v@l5580> and subject line Re: transaction: Python2 removal in sid/bullseye has caused the Debian Bug report #938717, regarding RM: transaction -- remove package for Python2 removal; no rdeps 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.) -- 938717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938717 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:transaction Version: 1.4.3-3 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:transaction 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 ---It looks like the python3 binaries will need to stay: Checking reverse dependencies... # Broken Depends: python-pyramid-tm: python-pyramid-tm python-repoze.tm2: python-repoze.tm2 python3-repoze.tm2 # Broken Build-Depends: python-btrees: python3-transaction python-repoze.tm2: python-transaction python3-transaction python-wsme: python3-transaction Dependency problem found. Closing the bug to remove the whole package. Scott K
--- End Message ---
