Control: retitle 936618 RM: git-remote-bzr -- removal triggered by the Python2 removal Control: reassign 936618 ftp.debian.org
On 2019-08-31, Jelmer Vernooij wrote: > On Sun, Mar 03, 2019 at 01:39:32PM -0800, Vagrant Cascadian wrote: >> On 2019-02-24, Jelmer Vernooij wrote: >> > bzr has long been dormant upstream. It will be replaced in Debian (in >> > buster+1) with Breezy (www.breezy-vcs.org), which is actively >> > maintained and has a Python 3 port. Breezy has a command-line that is >> > backwards compatible with Bazaar. >> > >> > Please consider porting git-remote-bzr to the 'breezy' Python module >> > instead of using Bazaar's 'bzrlib'. Most of the porting process should >> > be a matter of running s/bzrlib/breezy/ on your code. >> >> Given that git-remote-bzr provides a git frontend to a bzr repository, >> I'm not sure the backwards compatible command-line interface sounds too >> exciting... :) >> >> I don't personally work with many bzr repositorys anymore, so I would be >> inclined to orphan git-remote-bzr to someone with a more vested interest >> if bzr/bzrlib was dropped for buster+1. >> >> Upstream on git-remote-bzr hasn't been terribly active either: >> >> https://github.com/felipec/git-remote-bzr >> >> Though it's largely continued to work, which isn't a bad sign. > Bazaar will be removed with the Python 2 transition, with transitional > packages being added to upgrade users to Breezy. > > git-remote-bzr is the only remaining blocker for the Bazaar to Breezy > transition (and various plugin packages). Per the guidance in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936618, what are > your plans for the package? I don't use it anymore myself, as everything I was using it with switched to git... so, let's remove it. With both the planned removal of bzr and python2, and I don't see much recent activity upstream to switch to breezy or python3, it should probably just be removed from Debian. Thanks everyone, it was a fun ride! live well, vagrant
signature.asc
Description: PGP signature
