Paul Wise wrote: > On Fri, 2014-05-23 at 21:03 +0200, Sven Joachim wrote:
>> I wanted a package now, so I created one, Debian tarball is >> attached. It's probably not perfect, but it works for me. Anyone who >> volunteers for maintaining git-remote-bzr could use it as a starting >> point. > > I would be happy to sponsor you if you want to maintain it. If not I > guess I will have to maintain it since I really need these packages. Thanks. I also wouldn't mind co-maintaining since bugs may sometimes point to issues in git's remote helper code. >> It might be better to make git-bzr a transitional package and create a >> git-remote-bzr package which does not need an epoch. > > Jonathan, do you have any comments on how the transition should be done? What Sven said makes sense to me: a single source package with a transitional git-bzr package that depends on the main git-remote-bzr package. Then only the git-bzr package would need an epoch. git-bzr was never part of a stable release so it would just be needed for a little while for people using sid, testing, or stable-backports. It's not necessarily needed in the jessie release. I can add a Recommends to the git-all package to make the package more discoverable if you like. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
