Your message dated Tue, 14 Jan 2020 08:42:04 +0100
with message-id
<CACujMDN7LvTeWoT4AN3yW9v19Q3dWTCQKKznV7rVpLhfqsz5=g...@mail.gmail.com>
and subject line Re: Bug#948846: sparkleshare: Python2 removal in sid/bullseye
has caused the Debian Bug report #948846,
regarding sparkleshare: 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.)
--
948846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sparkleshare
Version: 3.28+git20190525+cf446c0-1
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:sparkleshare)Recommends->python
(binary:sparkleshare)Recommends->python-nautilus
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 ---
Version: 3.28+git20190525+cf446c0-1
On Mon, 13 Jan 2020 at 23:45, Sandro Tosi <mo...@debian.org> wrote:
>
> Source: sparkleshare
> Version: 3.28+git20190525+cf446c0-1
> 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:sparkleshare)Recommends->python
> (binary:sparkleshare)Recommends->python-nautilus
>
> 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.
--
Cheers,
Andrej
--- End Message ---
