Bug#965288: marked as done (r-cran-findpython: Python2 removal in sid/bullseye)
Your message dated Fri, 25 Sep 2020 09:49:09 + with message-id and subject line Bug#965288: fixed in r-cran-findpython 1.0.5-4 has caused the Debian Bug report #965288, regarding r-cran-findpython: 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.) -- 965288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-findpython Version: 1.0.5-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, in details: (binary:r-cran-findpython)Recommends->python 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 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: r-cran-findpython Source-Version: 1.0.5-4 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-findpython, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-findpython 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: Fri, 25 Sep 2020 11:29:56 +0200 Source: r-cran-findpython Architecture: source Version: 1.0.5-4 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 965288 967038 Changes: r-cran-findpython (1.0.5-4) unstable; urgency=medium . * Team upload. * Drop python from alternatives Closes: #965288, #967038 Checksums-Sha1: 47110a124777d2d9caed7f6546ef1337cee3fef9 2146 r-cran-findpython_1.0.5-4.dsc 9ab9366b437fb5f36d2dfd383159f92128b14c34 2576 r-cran-findpython_1.0.5-4.debian.tar.xz 5e78b6329a5855d913824e49bc7e95908e57dc33 8469 r-cran-findpython_1.0.5-4_amd64.buildinfo Checksums-Sha256: 774d0244d8da0c9a73c5369f32bbe697970a5d897fe3db39c545ddc756f70cd1 2146 r-cran-findpython_1.0.5-4.dsc c11158a5301158ce0a9471e46b83e34bd040dbe33754fb81a40d314d3af2 2576 r-cran-findpython_1.0.5-4.debian.tar.xz 9dd6c44ba81fd2b9f26857705a609cdad8ec9f88cf59f90520d0e2f33aba79de 8469 r-cran-findpython_1.0.5-4_amd64.buildinfo Files: 29c8da6995786323f4675868833ec980 2146 gnu-r optional r-cran-findpython_1.0.5-4.dsc 6f62924c0ab9e2b071cae6780949d11f 2576 gnu-r
Bug#965288: marked as done (r-cran-findpython: Python2 removal in sid/bullseye)
Your message dated Fri, 31 Jul 2020 15:01:35 +0200 with message-id and subject line Re: Bug#965288: r-cran-findpython: Python2 removal in sid/bullseye has caused the Debian Bug report #965288, regarding r-cran-findpython: 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.) -- 965288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-findpython Version: 1.0.5-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, in details: (binary:r-cran-findpython)Recommends->python 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 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 --- On Sun, 19 Jul 2020 09:51:09 +0300 Adrian Bunk wrote: > On Sun, Jul 19, 2020 at 02:45:22AM -0400, Sandro Tosi wrote: > > On Sun, Jul 19, 2020 at 2:41 AM Adrian Bunk wrote: > > > > > > On Sun, Jul 19, 2020 at 02:33:33AM -0400, Sandro Tosi wrote: > > > > > Recommends: r-cran-testthat, python3 | python > > > > > > > > > > Non-default alternative looks OK to me. > > > > > > > > it doesnt really make much sense: either it needs python2 or python3; > > > > if "| python" is not needed, it can be just easily dropped, and avoid > > > > the confusion it causes (special cases are not special enough) > > > > > > As the package name says it does not need python, it finds python: > > > > > > Description-en: GNU R functions to find an acceptable Python binary > > > This GNU R package is designed to find an acceptable Python > > > binary. It is possible to specify a minimum and a maximum Python > > > version as well as specifying needed Python modules. > > > > > > "python3 | python" looks correct to me for that. > > > > the point of these bugs (as the subject says) is to remove python2 > > dependencies, so "| python" has to go. if it doesnt, then this bug > > ought to stay open until it is addressed. > > This would only make sense if the point were to not ship python2 > in bullseye. Since there is only a recommends on python(2), and that is not against policy nor the Python 2 removal process then I am closing this bug. Thanks for checking! -- Michael R. Crusoe signature.asc Description: OpenPGP digital signature --- End Message ---
