Your message dated Fri, 31 Jul 2020 15:01:35 +0200
with message-id <b45f34a1-6e53-eb1e-1faf-8584fcdd9...@debian.org>
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 <b...@debian.org> 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 <b...@debian.org> 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 ---
