Bug#938605: marked as done (svgtune: Python2 removal in sid/bullseye)
Your message dated Mon, 22 Jun 2020 22:48:37 + with message-id and subject line Bug#938605: fixed in svgtune 0.3.0-2 has caused the Debian Bug report #938605, regarding svgtune: 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.) -- 938605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:svgtune Version: 0.2.0-2 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 + src:svgtune 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 --- Source: svgtune Source-Version: 0.3.0-2 Done: Yaroslav Halchenko We believe that the bug you reported is fixed in the latest version of svgtune, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yaroslav Halchenko (supplier of updated svgtune package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Jun 2020 11:05:03 -0400 Source: svgtune Architecture: source Version: 0.3.0-2 Distribution: unstable Urgency: medium Maintainer: Yaroslav Halchenko Changed-By: Yaroslav Halchenko Closes: 938605 Changes: svgtune (0.3.0-2) unstable; urgency=medium . * Completely remove mentioning of python (not python3) in debian/control (Closes: #938605) Checksums-Sha1: c1f49fb0af0d99e8236d6372847ca6011d325d99 1829 svgtune_0.3.0-2.dsc b52ba69a7ab3feb1791d216bb1bf00943b5b377a 1965 svgtune_0.3.0-2.diff.gz f36c46823af93adad473737617b19f48b987 5914 svgtune_0.3.0-2_source.buildinfo Checksums-Sha256: c008fcf6f51b72a9ebfc8f73017b5a91898842079dcbb800b688b72b9d7fb86d 1829 svgtune_0.3.0-2.dsc 3be801f1c546c1e9fcee1895a37daabb024db9f051c2861ef79d0fe728c77d66 1965 svgtune_0.3.0-2.diff.gz 423bdcd4d9f828a7ea9c884a14d67c395fc29fd6d7be7328ed45119a43d0731f 5914 svgtune_0.3.0-2_source.buildinfo Files: d1a6657c2d327a74abd67e5834b463b5 1829
Bug#938605: marked as done (svgtune: Python2 removal in sid/bullseye)
Your message dated Thu, 07 May 2020 20:35:40 -0400 with message-id <2f3cd2e49538cb07173ea26410453f0b6894be7a.ca...@debian.org> and subject line Re: svgtune: Python2 removal in sid/bullseye has caused the Debian Bug report #938605, regarding svgtune: 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.) -- 938605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:svgtune Version: 0.2.0-2 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 + src:svgtune 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.3.0-1 It seems that the new version has made it compatible with Python3. -- Regards, Boyuan Yang On Fri, 30 Aug 2019 07:54:44 + Matthias Klose wrote: > Package: src:svgtune > Version: 0.2.0-2 > 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
