Re: Python2 removal: package with low-popcon reverse dependencies
On 10/11/19 9:26 PM, Christian Kastner wrote: > On 11.10.19 19:47, Matthias Klose wrote: >> On 11.10.19 18:27, Christian Kastner wrote: >>> This would nevertheless be a case for the "py2keep", right? >> >> No. >> >> #933348 is another bug for removed packages (mopidy-scrobler). Do you >> really want to keep that? > > Not at all, I'd actually prefer just dropping the Python2 version of > python-cachetools. However, this breaks things, and it wasn't entirely > clear to me much breakage is acceptable. It's becoming increasingly clear to me that, at some point, we will need to just ignore the breakage. Bust this needs to be discussed here first. Maybe the better way to fix the situation is to increase the severity of the py2 removal bug to serious, so we leave a chance to the maintainer to take care of the package before the autorm. See the other thread I've just started about this. Cheers, Thomas Goirand (zigo)
Re: Python2 removal: package with low-popcon reverse dependencies
On 11.10.19 19:47, Matthias Klose wrote: > On 11.10.19 18:27, Christian Kastner wrote: >> This would nevertheless be a case for the "py2keep", right? > > No. > > #933348 is another bug for removed packages (mopidy-scrobler). Do you > really want to keep that? Not at all, I'd actually prefer just dropping the Python2 version of python-cachetools. However, this breaks things, and it wasn't entirely clear to me much breakage is acceptable. > Is the mopidy popcon really enough to keep it? Don't look at the > popcon of any python module. The relevant popocon is the one for the > application. OK. > No, this is not yet done. Pending a dh-python upload. So assuming I had a Python2 module that needed updating (instead of outright removing it), I'd await this upload. Thanks, Christian
Re: Python2 removal: package with low-popcon reverse dependencies
On 11.10.19 18:27, Christian Kastner wrote: Hi, python-cachetools provides modules for Python2 and Python3. The Python2 module as two reverse dependencies, both with low installed popcon: python-cachetools: 302 mopidy-podcast: 109 mopidy-internetarchive: 95 This would nevertheless be a case for the "py2keep", right? No. #933348 is another bug for removed packages (mopidy-scrobler). Do you really want to keep that? Is the mopidy popcon really enough to keep it? Don't look at the popcon of any python module. The relevant popocon is the one for the application. Would this also be the case if python-cachetools itself had a lower popcon, say 50? Or is any form of dependency a case for "py2keep"? Furthermore, the instructions in the Python2 removal request #937627 say: 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. The binary package has versioned dependencies generating during the build process, so there is nothing else to do, right? No, this is not yet done. Pending a dh-python upload.
Python2 removal: package with low-popcon reverse dependencies
Hi, python-cachetools provides modules for Python2 and Python3. The Python2 module as two reverse dependencies, both with low installed popcon: python-cachetools: 302 mopidy-podcast: 109 mopidy-internetarchive: 95 This would nevertheless be a case for the "py2keep", right? Would this also be the case if python-cachetools itself had a lower popcon, say 50? Or is any form of dependency a case for "py2keep"? Furthermore, the instructions in the Python2 removal request #937627 say: > 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. The binary package has versioned dependencies generating during the build process, so there is nothing else to do, right? Christian
