Bug#936588: marked as done (gcc-9-cross-ports: Python2 removal in sid/bullseye)
Your message dated Tue, 10 Sep 2019 20:41:24 + with message-id and subject line Bug#936588: fixed in gcc-9-cross-ports 10 has caused the Debian Bug report #936588, regarding gcc-9-cross-ports: 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.) -- 936588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gcc-9-cross-ports Version: 8 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:gcc-9-cross-ports 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: gcc-9-cross-ports Source-Version: 10 We believe that the bug you reported is fixed in the latest version of gcc-9-cross-ports, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-9-cross-ports 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: Tue, 10 Sep 2019 21:54:32 +0200 Source: gcc-9-cross-ports Architecture: source Version: 10 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 936588 Changes: gcc-9-cross-ports (10) unstable; urgency=medium . * Build using gcc 9.2.1-8. * Build-depend on python3. Closes: #936588. * Stop building mipsel and mips64el packages, now built from the gcc-cross-mipsen source package. Checksums-Sha1: 402352dd9d2a714fe40f337b5b5fe67740928564 35768 gcc-9-cross-ports_10.dsc b8185684861e336c4e0ba50632cdf11fa61f3c54 42004 gcc-9-cross-ports_10.tar.xz e8104ca0e7805edc4c6d71ac530f16e729884ed9 16774 gcc-9-cross-ports_10_source.buildinfo Checksums-Sha256: 0a74d945b070df3161076727dd8431c41dfeb35dd41779d8190b32b29befbf2f 35768 gcc-9-cross-ports_10.dsc e325bf13ce5f005ee159fb2926b9c41af538a134ff9b6fe29362f4ffdf3128a4 42004 gcc-9-cross-ports_10.tar.xz
Bug#936588: marked as done (gcc-9-cross-ports: Python2 removal in sid/bullseye)
Your message dated Tue, 10 Sep 2019 11:04:40 + with message-id and subject line Bug#936588: fixed in cross-toolchain-base-ports 35 has caused the Debian Bug report #936588, regarding gcc-9-cross-ports: 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.) -- 936588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gcc-9-cross-ports Version: 8 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:gcc-9-cross-ports 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: cross-toolchain-base-ports Source-Version: 35 We believe that the bug you reported is fixed in the latest version of cross-toolchain-base-ports, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated cross-toolchain-base-ports 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: Tue, 10 Sep 2019 12:09:05 +0200 Source: cross-toolchain-base-ports Architecture: source Version: 35 Distribution: unstable Urgency: medium Maintainer: Cross Toolchain Base Team Changed-By: Matthias Klose Closes: 936588 Changes: cross-toolchain-base-ports (35) unstable; urgency=medium . * Fix gcc-source extraction step. * Build using glibc 2.29-1. * Build using gcc 9.2.1-8. * Merge glibc-2.30 changes from Ubuntu. * Build gm2 using Python3. Closes: #936588. Checksums-Sha1: 218b244773b55a3c7b12b1ece79a45850f110037 6191 cross-toolchain-base-ports_35.dsc e757ade5efbce7f5554662d58d40508e2efa3291 42124 cross-toolchain-base-ports_35.tar.xz c04e758363e69eb9ff17a9aab02d9dd80489c8ea 9116 cross-toolchain-base-ports_35_source.buildinfo Checksums-Sha256: ce7bada5857f82e4bcaa7b022dd826aa53dee864d2d6f2c612ca57afff995ab0 6191 cross-toolchain-base-ports_35.dsc
