On 9/15/19 2:26 PM, Mattia Rizzolo wrote: > Considering that this is bzr we are talking about, a package that is > already entering the graveyard, I think it would be easiest to just > disable the test suite and move on. > > But I would be happier it Thomas at least checked the rdeps before > dropping packages, at least evaluating if breaking things is alrightif > he really likes to break packages :/
You mean check *better*. Because I do carefully check each time, as much as I can, but in this occurrence, it looks like I didn't check well enough. Mistakes unfortunately do happen when you work on a lot of packages. Moreover, the current tooling we have at our disposal is kind of broken. reverse-depends takes sometimes forever in Sid for a reason I can't figure out. And if I'm not mistaking, that's the only tool we have that can check reverse dependencies in a meaningful way. Or is there a better way? I've read others using a dak command, how? On 9/15/19 5:17 PM, Jelmer Vernooij wrote: > It's not just bzr, it's also a bunch of plugins for bzr that we'd have > to disable the testsuite for - as well as a bunch of other non-bzr-related packages - python-subunit, python-fixtures, python-testscenarios, python-daemon, python-fastimport. I've already removed Python 2 support from subunit, python-fixtures, and python-testscenarios. Now, as I wrote in the bug report, what worries me aren't these, but the other packages that are depending on python-daemon: Packages without Python 3 support upstream: - bcfg2 doesn't seem to have Python 3 support upstream, neither the Debian package. - nss-pam-ldapd isn't Python 3 ready upstream. Note that the debian maintainer the same person as upstream. - There's been zero upstream work on this repository: https://github.com/Yubico/python-pyhsm so the package has no change to be Python 3 ready anytime soon. Packages that simply need an upgrade from latest upstream release: - lavapdu-daemon should be upgraded to latest upstream release to have Python 3 support. - mini-buildd in Experimental has been converted to Python 3, while the version in Sid is still Python 2. - I haven't been able to tell for lava-coordinator. So, for bcfg2, nss-pam-ldapd, and python-pyhsm, I'm really not convinced that waiting for longer will help. That's a general problem that we btw need to address: how are we going to deal with this? There's going to be a lot of it, and we need to find a way out if we really are going to get Python 2 out. For the other 3, I shouldn't be hard to address by the current maintainers. I've raised the severity of #936189 #937165 #938069 #936819 #937049 #936818 to serious, and included them as Cc to this reply, in order to warn the maintainers. I haven't done it for the BZR stuff, as obviously, the package maintainer is aware now. Again, sorry that it happened this way. Cheers, Thomas Goirand (zigo)
