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 :/ On Sun, 15 Sep 2019, 11:09 am Jelmer Vernooij, <[email protected]> wrote: > > > On 15 September 2019 01:15:11 CEST, Scott Kitterman <[email protected]> > wrote: > >On Saturday, September 14, 2019 6:43:13 PM EDT Thomas Goirand wrote: > >> Hi, > >> > >> As I wrongly thought python-extras was used only by OpenStack stuff, > >I > >> removed Python 2 support for it. Then someone filed a bug against > >> python-testtools (ScottK, I believe) saying that it became RC. > >> Therefore, I went ahead and removed Python 2 support for testtools, > >but > >> now, this implies that a few packages which I didn't wish to impact > >are > >> also RC: > >> > >> * bzr-builddeb > >> * bzr-email > >> * bzr-fastimport > >> * bzr-git > >> * bzr-stats > >> * bzr-upload > >> * loggerhead > >> > >> So, basically, unfortunately, Bazaar has lost some of its build > >> dependencies. > >> > >> So, I went ahead, and looked what I could do for Bazaar. > >Unfortunately, > >> when looking at: > >> https://launchpad.net/bzr > >> > >> I can see no release since January 2016, no daily archive. The last > >> commit in the bzr repository of bzr is from 2017-03-17. > >> > >> Then I went to see how much Python 3 effort would be needed, and I > >> quickly gave up. It'd be A LOT of work, but nobody seems doing ANY > >work > >> on bzr anymore. > >> > >> So I wonder: is it time to remove bazaar from Debian? Or is there any > >> vague plan to make it work with Python 3? If we are to remove it from > >> Debian, then we'd better do it ASAP. > > > >As I understand it, bazaar (bzr) is dead and being replaced by breezy > >(brz), > >which is python3 compatible. > > > >https://www.breezy-vcs.org/ > > > >My inference is that anything bzr specific can go, but I'm not involved > >in > >either project. > > Bzr maintainer / breezy upstream here. > > I'm planning to upload transitional packages to trigger upgrades from bzr > to Breezy. > > The packages for that are not ready yet though. Can we undo the dropping > of python-testtools in the meantime? > > Jelmer > >
