Your message dated Wed, 30 Nov 2022 18:11:42 +0000 with message-id <[email protected]> and subject line Bug#938921: Removed package(s) from unstable has caused the Debian Bug report #938921, regarding RM: zorp -- RoQA; py2 leftover 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.) -- 938921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938921 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:zorp Version: 6.0.10-4 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:zorp 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 ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libzorp-7.0 | 7.0.1~alpha2-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libzorp-dev | 7.0.1~alpha2-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x munin-plugins-zorp | 7.0.1~alpha2-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x nagios-plugins-zorp | 7.0.1~alpha2-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x zorp | 7.0.1~alpha2-3 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x zorp-modules | 7.0.1~alpha2-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x ------------------- Reason ------------------- RoQA; py2 leftover ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected]. The full log for this bug can be viewed at https://bugs.debian.org/938921 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
