Re: Python2/Qt4 removal
On Saturday, August 24, 2019 2:46:04 AM EDT Guðjón Guðjónsson wrote: > Hi list > > QScintilla Qt4/python2 version has one reverse dependency and it is the > tora package that is marked for autoremoval on the 5th of September. > > Shall I keep support for Qt4/python2 in my upgrade or is it ok to remove it? You should wait until it's either upgraded or removed from unstable. It depends directly on the library, not the python binding, so if nothing else is using the python bindings they can be dropped now even if you keep Qt4 support for the moment. I note that the new upstream release of tora supports Qt5, so I would recommend emailing the maintainer (there's already a bug) to ask them to either upgrade the package or file an rm request. Scott K
Re: py2-rm: a few leaf packages to work on
On Thu, 15 Aug 2019 14:08:41 +0200 Thomas Goirand wrote: > Hi there! > > According to the daily graph I built here: > http://py2graph.infomaniak.ch/py2.7.deps.svg > > we can work on Python 2 removal for the below packages. How is that graph turned into a list of packages? It's too large to scan manually. I'm attaching a sorted list of the packages you mentioned in the first email but I can't see how to update the list from the graph. I'm trying to work out what links to python-tftpy or whether it merely links to others (and why, because the package itself doesn't declare any dependencies except python2 and I can't find rdepends in apt-cache). It's not included in the list output, so I'm confused. https://packages.debian.org/unstable/python-tftpy Context: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784028#10 0.8.0 has Python3 support but packaging it is more work than it probably deserves, unless there is some reason to keep the package. > Note that I > have *not* checked for reverse dependencies, please do so before > working on a package. The list isn't exhaustive at all, and didn't > check if a package is just a remaining curft, though it's hopefully > still helpful as a TODO list. > > Cheers, > > Thomas Goirand (zigo) > -- Neil Williams = http://www.linux.codehelp.co.uk/ py2.yaml Description: application/yaml pgpOJQyyl6HJu.pgp Description: OpenPGP digital signature
Re: Watch file for riverbankcomputing (QScintilla)
Hi Guðjón! On Sat, Aug 24, 2019 at 08:43:33AM +0200, Guðjón Guðjónsson wrote: > I am working on the QScintilla package and starting on the watch file > but I cannot figure out how to fix the URL. I tried to use the > pyqt5 package as a template but without luck. > The URL is > https://www.riverbankcomputing.com/static/Downloads/QScintilla/2.11.2/QScintilla_gpl-2.11.2.tar.gz > and the pyqt5 watch file contains: > https://www.riverbankcomputing.com/software/pyqt/download5 \ > /static/Downloads/PyQt5/[\d.]+/PyQt5_gpl-([\d.]+)\.tar\.gz > > but it doesn't help me :( The following seems to work for me: version=3 opts=dversionmangle=s/\+dfsg// \ https://www.riverbankcomputing.com/software/qscintilla/download \ /static/Downloads/QScintilla/[\d.]+/QScintilla_gpl-([\d.]+)\.tar\.gz If you are going to replace custom repacking code with Files-Excluded field in debian/copyright, then change second line to this: opts=dversionmangle=s/\+dfsg//,repacksuffix=+dfsg \ -- Dmitry Shachnev signature.asc Description: PGP signature
Re: py2-rm: a few leaf packages to work on
On 8/24/19 10:38 AM, Neil Williams wrote: > How is that graph turned into a list of packages? It's too large to > scan manually. Well, I did it manually... and this is only a short list, as a suggestion for a todo list, so nothing exhaustive... I very much would welcome something automated. BTW, working on this (as I've assigned myself to do a Python 2 support removal for at least one package a day), I've seen that lots of the packages are just bit-rotting stuff that has sometimes been uploaded only once, and that nobody cares about anymore. We should have spotted these earlier, IMO, and probably ping the maintainers. I'm still waiting on Piotr (or someone else) to do the mail to -devel and the mass-bug-filling ... Any news on this? Thomas
Removing py2 support from python-xattr
Hi, I came across python-xattr, which I know well because it's used in Swift. I went to investigate it's reverse dependencies, and discovered that it's py2 version is only used by calendarserver, which itself, is py2 only upstream, and is full of py2-ism that would need to be fixed (and the work is really non-trivial and huge). Since we decided to work on leaf packages only, what to do in this case, as it doesn't look like calendarserver will be fixed anytime soon? Shall we wait? For how long? I've of course filed a bug against calendarserver, but I'm quite sure this wont be enough to get things moving. Please, let's generalize and see the whole picture. There will be A LOT more cases like this one, and I don't think that waiting forever will solve the situation. It is my opinion that we should set a kind of policy (ie: wait for how long?) and then act... Cheers, Thomas Goirand (zigo)
Re: Removing py2 support from python-xattr
On Saturday, August 24, 2019 6:28:10 PM EDT Thomas Goirand wrote: > Hi, > > I came across python-xattr, which I know well because it's used in > Swift. I went to investigate it's reverse dependencies, and discovered > that it's py2 version is only used by calendarserver, which itself, is > py2 only upstream, and is full of py2-ism that would need to be fixed > (and the work is really non-trivial and huge). > > Since we decided to work on leaf packages only, what to do in this case, > as it doesn't look like calendarserver will be fixed anytime soon? Shall > we wait? For how long? I've of course filed a bug against > calendarserver, but I'm quite sure this wont be enough to get things moving. > > Please, let's generalize and see the whole picture. There will be A LOT > more cases like this one, and I don't think that waiting forever will > solve the situation. It is my opinion that we should set a kind of > policy (ie: wait for how long?) and then act... If it were me, I'd go ahead and file a serious bug indicating a dependency of the package is about to be removed. Scott K
Re: Python2/Qt4 removal
On Saturday, August 24, 2019 3:26:33 AM EDT Scott Kitterman wrote: > On Saturday, August 24, 2019 2:46:04 AM EDT Guðjón Guðjónsson wrote: > > Hi list > > > > QScintilla Qt4/python2 version has one reverse dependency and it is the > > tora package that is marked for autoremoval on the 5th of September. > > > > Shall I keep support for Qt4/python2 in my upgrade or is it ok to remove > > it? > You should wait until it's either upgraded or removed from unstable. It > depends directly on the library, not the python binding, so if nothing else > is using the python bindings they can be dropped now even if you keep Qt4 > support for the moment. > > I note that the new upstream release of tora supports Qt5, so I would > recommend emailing the maintainer (there's already a bug) to ask them to > either upgrade the package or file an rm request. Tora is gone now, but you're not quite there yet. reverse-depends python-qscintilla2 Reverse-Recommends == * connectomeviewer See #875494 about this. reverse-depends python-pyqt5.qsci Reverse-Depends === * tortoisehg I filed #935660 about this. Scott K
