Bug#939641: dnsrecon: Python2 removal in sid/bullseye

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#939641: dnsrecon: Python2 removal in sid/bullseye

Andreas Henriksson-3
Package: dnsrecon
Version: 0.8.14-1
Severity: normal
Tags: sid bullseye
User: [hidden email]
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 [hidden email] 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 <bug number of blocking py2removal bug> + src:pyeapi

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 [hidden email] mailing list.

Reply | Threaded
Open this post in threaded view
|

Bug#939641: dnsrecon: Python2 removal in sid/bullseye

Scott Kitterman-5
On Sat, 7 Sep 2019 10:16:36 +0200 Andreas Henriksson <[hidden email]> wrote:

> Package: dnsrecon
> Version: 0.8.14-1
> Severity: normal
> Tags: sid bullseye
> User: [hidden email]
> 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.
This is one of two packages still in Testing that needs the python2 version of
dnspython.  It would be really nice to see it packaged to use python3 so we
can make progress on getting rid of python2 (which no longer has upstream
security support).

There is evidence in the upstream commit history [1] that this will work with
either python2 or python3, so I sould appreciate it if you could see if
switching to python3 works.  If you need help with the packaging changes for
that, please let me know (cc me since I am not subscribed to the bug).  I
don't, however, know how to test it since I don't use the package and there's
no test suite.

Scott K

[1] https://github.com/darkoperator/dnsrecon/commit/
1a7a58332f99a3310847f506ff382b71e88d1837

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#939641: dnsrecon: Python2 removal in sid/bullseye

Raphael Hertzog-3
Control: forwarded -1 https://github.com/darkoperator/dnsrecon/issues/115

On Tue, 25 Feb 2020, Scott Kitterman wrote:
> There is evidence in the upstream commit history [1] that this will work with
> either python2 or python3, so I sould appreciate it if you could see if
> switching to python3 works.  If you need help with the packaging changes for

A quick test shows that this was not extensively tested with Python 3.

I have fixed a few issues that I saw but I'm still going ahead with the
switch.

Cheers,
--
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog <[hidden email]>
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋    The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄⠀⠀⠀⠀   Debian Long Term Support: https://deb.li/LTS

signature.asc (535 bytes) Download Attachment