[Debian-med-packaging] Bug#943125: Please port Hisat2 to Python3 (Was: Bug#943125: hisat2: Python2 removal in sid/bullseye)

Andreas Tille andreas at an3as.eu
Mon Dec 16 08:53:55 GMT 2019


Control: tags -1 upstream
Control: forwarded -1 hisat2.genomics at gmail.com

Hi,

as you can read in below bug report Debian will drop Python2 since it
is end of life.  It would be great if you could port HISAT2 to Python3.
I'd recommend to use the 2to3 tool.  Feel free to respond to the
e-mail address of this bug report if you might need more information
or any help.

Kind regards

         Andreas.


On Wed, Oct 23, 2019 at 02:33:26AM +0000, morph at debian.org wrote:
> Source: hisat2
> Version: 2.1.0-2
> Severity: normal
> Tags: sid bullseye
> User: debian-python at 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_take2.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-python at 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-python at lists.debian.org mailing list.
> 
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list