On Sun, Feb 2, 2020 at 6:51 AM Adrian Bunk <b...@debian.org> wrote: > > On Tue, Jan 28, 2020 at 04:06:28PM -0500, Sandro Tosi wrote: > >... > > python-txsocksx -> foolscap -> tahoe-lafs > > > > both foolscap and tahoe-lafs were removed from testing, so to my > > script python-txsocksx appears as a leaf package (as its removal wont > > break already broken/RC packages not in testing). not sure what we > > want to do here, none of the 2 other packages will get fix anytime > > soon and may get removed from debian entirely at some point. > >... > > The latter statement is not true. > > Both tahoe-lafs and foolscap have substantial upstream activities > towards Python 3 porting,
my statement says "none of the 2 other packages will get fix anytime soon and may get removed from debian entirely at some point" -- what do you find un-true about it? i did not say those projects python3 port is not being worked on, but i say that they are not close to finishing it, which includes both porting the code *and* testing it and finally release a version that has the python3 port. for tahoe-lafs the effort is tracked at https://tahoe-lafs.org/trac/tahoe-lafs/milestone/Support%20Python%203 which is currently marked at 89% completed; it was marked to be completed by Dec 1, 2019, so they are 2 months behind their own schedule (again, no blaming, just stating facts) for foolscape the effort is tracked at https://github.com/warner/foolscap/issues/48 which received some attention at the beginning on 2020 (holiday break?) and none since Jan 5. So, can you explain what you find misrepresented in my statement? > the reasonable way forward would be to close > this RM bug and watch how it all will get resolved in a few months with > new upstream versions. We've been known the end of python2 support would be in 2020 since years, i'm not sure it's fair for the projects that took the time earlier and to the debian maintainers to ask to keep supporting python2 packages for (relatively) old software for additional *few months*. Please also note that txsocksx is not python3 ready yet, nor there's any progress in porting it. How keeping the old python2 package in Debian is gonna help with that port? It would the py2removal effort in debian by removing an old package with no py3k port available, Happy to hear what your thoughts are on this. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
