On Thu, May 29, 2014 at 11:52:29AM +0800, Paul Wise wrote: > On Wed, 2014-05-28 at 10:21 -0700, Jonathan Nieder wrote: > > > Thanks. I also wouldn't mind co-maintaining since bugs may sometimes > > point to issues in git's remote helper code. > > Excellent, thanks. I'd also be interested in helping with this package. > > 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. > > Agreed but I think it would be best to have the transitional package > built from the git source package. Having different versions for > different binary packages created from the same source package is > possible but it is very confusing. Wheezy never shipped git-bzr, although it is present in wheezy-backports. A transitional package for something never provided in a stable release maybe seems like more trouble than it's worth, if that's the main thing blocking upload. If a transitional package is definitely needed, I'm of the opinion that it's better to ship the transitional package in the new source package, as then you don't need to coordinate uploads between two source packages when it comes time to drop the transitional package. I'd be willing to actually work on the differing versions, if needed. It seems to be a fairly straightforward package, really. Sven's packaging seemed to work fine for me. There aren't many files for copyright review. How can I help? live well, vagrant
Attachment:
signature.asc
Description: Digital signature