> On Tue, Oct 01, 2019 at 05:42:56PM +0200, Sebastiaan Couwenberg wrote: > > We shouldn't block removal of Python 2 support on badly and unmaintained > > packages.
you can make your case to debian-python@ , but calling networkx or any of its rdeps "badly and unmaintained packages" it's borderline insulting. if you want to know the impact of breaking python-networkx have a look at http://sandrotosi.me/debian/py2removal/python-networkx_2.svg (and that's just 2 levels of dependencies, the tree is much deeper than that) > we should. as some people didnt respect this, piuparts is now broken in > testing. you're right Holger, this has happened and when i noticed, i asked the uploader to revert and that usually happened pretty quickly (it is easy to get over-excited and not noticing the real impact). i think you can ask to revert the removal of whatever package broke piuparts > i do however agree, that it doesnt make much sense to have rules if > people can just break them. I'm afraid that's always the case: we can upload RC buggy packages to unstable, we can introduce regressions, and violate the Debian Policy anytime (willingly or no) so the rule is there to say "people with some experience on the topic thought about it and come up with this rule you should probably follow", at least that's my take. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
