Control: tag -1 +fixed-upstream, pending THank you for reporting this bug. It has been committed into my repository and will be part of next upload.
commit 81f92cdb4843aaccfd2c36e61595b4cf3449b44b (HEAD -> debian, origin/debian)
Author: Ritesh Raj Sarraf <r...@debian.org>
Date: Thu Nov 28 12:27:55 2019 +0530
Drop some python2 based recommends
Thanks: Sandro Tosi
Closes: #945628
python-soappy is not needed anymore. We use python3-debianbts
python-lzma is not needed anymore. lzma module is part of Python
standard modules now
diff --git a/debian/control b/debian/control
index 7083461..6b14456 100644
--- a/debian/control
+++ b/debian/control
@@ -12,7 +12,7 @@ Vcs-Browser:
https://anonscm.debian.org/cgit/apt-offline/apt-offline.git
Package: apt-offline
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends}, apt, less, python3-magic
-Recommends: python-soappy, debian-archive-keyring, python-lzma,
python3-debianbts
+Recommends: debian-archive-keyring, python3-debianbts
Description: offline APT package manager
apt-offline is an Offline APT Package Manager.
.
On Wed, 2019-11-27 at 23:58 +0000, Sandro Tosi wrote:
> Source: apt-offline
> Version: 1.8.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 (the specific reason can be found searching this
> source package in
> https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
> 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.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
