Re: Transition tracker for rm python2 live
Scott K wrote: On 2019-07-24 09:01, eamanu15 . wrote: El mar., 23 de jul. de 2019 a la(s) 21:55, Drew Parsons escribió: What should "success" or completion look like on the tracker? I uploaded pyfttw (not python-fftw, which is a different package) hoping to get the first line of good green, but it has gone yellow rather than green. mmm maybe yellow is ok? Once the python2 binaries are decrufted it should disappear off the tracker entirely. I see. The yellow means the package has been updated to python3 only, but the old python2 cruft is still sitting there. Drew
Re: Transition tracker for rm python2 live
On July 24, 2019 1:01:47 AM UTC, "eamanu15 ." wrote: >El mar., 23 de jul. de 2019 a la(s) 21:55, Drew Parsons >(dpars...@debian.org) >escribió: > >> Scott Kitterman wrote: >> > See https://release.debian.org/transitions/html/python2-rm.html >> > >> > The ones near the top of the stack (bottom of the page) are less >likely >> > to >> > have rdepends that need to be sorted before action can be taken on >> > them. >> >> >> What should "success" or completion look like on the tracker? I >> uploaded pyfttw (not python-fftw, which is a different package) >hoping >> to get the first line of good green, but it has gone yellow rather >than >> green. >> > >mmm maybe yellow is ok? Once the python2 binaries are decrufted it should disappear off the tracker entirely. Scott K
Re: Transition tracker for rm python2 live
El mar., 23 de jul. de 2019 a la(s) 21:55, Drew Parsons (dpars...@debian.org) escribió: > Scott Kitterman wrote: > > See https://release.debian.org/transitions/html/python2-rm.html > > > > The ones near the top of the stack (bottom of the page) are less likely > > to > > have rdepends that need to be sorted before action can be taken on > > them. > > > What should "success" or completion look like on the tracker? I > uploaded pyfttw (not python-fftw, which is a different package) hoping > to get the first line of good green, but it has gone yellow rather than > green. > mmm maybe yellow is ok? > > Drew > > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: Transition tracker for rm python2 live
Scott Kitterman wrote: See https://release.debian.org/transitions/html/python2-rm.html The ones near the top of the stack (bottom of the page) are less likely to have rdepends that need to be sorted before action can be taken on them. What should "success" or completion look like on the tracker? I uploaded pyfttw (not python-fftw, which is a different package) hoping to get the first line of good green, but it has gone yellow rather than green. Drew
Python 2 and PyPy module removal from Debian
Hi, During DebConf19 we¹ have tried to figure out how to manage Python 2 and PyPy module removal from Debian and below is our proposal. After discussing it on this mailing list we plan to send an email to debian-devel@l.d.o with a mass bug report and later an announcement about Python 2.X / PyPy module removal with some hints about what to expect to debian-devel-announce@l.d.o. There's a release tracker set up for Python 2 removal: https://release.debian.org/transitions/html/python2-rm.html but we plan to report a bug for each package that uses Python 2 or PyPy. All these bugs will get "py2removal" usertag and later one or more additional usertags - to make progress tracking a bit easier (release tracker is not optimised for our case). Severity will be set to a RC one at some point so that packages will be autoremoved from testing. Additional tags we will use are: • py2leaf - leaf package ready to be removed, i.e. without (build-)dependencies (including Recommends) in Debian main, • py3available - Python 3 support is available upstream, package needs an update in Debian, • py3noport - there's no upstream support for Python 3, needs a port done by us or package will be removed, • py2keep - package that should not be removed for now (popcon >1000 by default). Please don't add this usertag without discussing it on the mailing list first, • py2rm - packages that we will remove from Debian due to low popcon, etc. - all packages with popcon <100 will get this one by default Each bug will mention wiki help page (which we invite you to improve): https://wiki.debian.org/Python/2Removal documentation = Please keep the python-foo-doc package. Do not rename it to python3-foo-doc. If python-foo was providing documentation: move it to python3-foo or create python-foo-doc (not python3-foo-doc!) binary package. If your package uses python-sphinx to build docs: replace it with python3-sphinx. missing dh-python build dependency == There are ≈62² packages that use old dh_python2 helper (the one provided by python package). This helper will be removed in few months. Please add dh-python to Build-Depends (if your package cannot be upgraded to Python 3 or removed from Debian). Bug reports will be reported soon for these packages. There are ≈11² packages that use dh_python3 but do not depend on dh-python. python3 package will stop depending on dh-python soon, so please add missing dependency. Boost = In the next Boost transition Python 2 and Python 3 will get separate -dev packages. Please make sure you build-depend on the right one (and remove Python 2.X support if possible). DPMT / PAPT === No need to wait for a bug report. If you have a leaf package, remove it now. If you're not a DD, do it in the git repo and ping Piotr. [¹] Dimitri, Matthias, Piotr, Stefano, Thomas [²] https://lintian.debian.org/tags/missing-build-dependency-for-dh_-command.html signature.asc Description: PGP signature
Re: Removing python2 packages
On Tue, 23 Jul 2019 10:40:29 -0400 (EDT) Scott Talbert wrote: > When removing leaf python2 packages for bullseye, is there anything > special that needs to be done, other than removing the building of > the python2 subpackage? > > For example, obsoleting of the old package or anything along those > lines? Obsoleting would infer that the Python2 version hangs around in some way. That would defeat the object somewhat. Most leaf packages will be binaries, so the binary can just change to Python3. If there's a Python2 module or other support package, just drop it. Put an entry in NEWS if you think people may have out-of-distro scripts using the Python2 module. Otherwise, a note in README.Debian or just debian/changelog is probably enough. It's fairly obvious when a Python leaf binary moves to Python3 support. As long it continues to work, most users aren't going to even notice. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpzUYLNoBm9B.pgp Description: OpenPGP digital signature
Re: Transition tracker for rm python2 live
Hi, po 22. 7. 2019 v 12:19 odesílatel eamanu15 . napsal: > For a NMU for the PY2 remove I have just change the files on salsa and > letting know to the maintainer or, just writte here to get help on the > upload? > NMU=non-maintainer upload. This is not NMU. You should prepare changes on Salsa DPMT/PAPT repos and request someone from team (or one of uploader) to sponsor it. -- Best regards Ondřej Nový
Re: Removing python2 packages
Hi, út 23. 7. 2019 v 11:40 odesílatel Scott Talbert napsal: > When removing leaf python2 packages for bullseye, is there anything > __modules__ package :) > special that needs to be done, other than removing the building of the > python2 subpackage? > > For example, obsoleting of the old package or anything along those lines? > * check reverse-depends and "reverse-depends -b" * remove from d/control * remove from d/tests * remove from d/rules * check/remove d/python-* files * test * upload -- Best regards Ondřej Nový
Removing python2 packages
When removing leaf python2 packages for bullseye, is there anything special that needs to be done, other than removing the building of the python2 subpackage? For example, obsoleting of the old package or anything along those lines? Scott
