Hi Sven, Sven Joachim wrote: > On 2014-05-21 23:20 +0200, Jonathan Nieder wrote:
>> Now git-remote-bzr has graduated to its own upstream. Reopening as a >> reminder to package it. (Or if someone else gets to it before me, I >> won't mind.) > > Well, it would have been _a little bit_ more user friendly to prepare a > package *before* removing git-bzr, wouldn't it? You're saying I should have done a lot of packaging work and waited for the result to go through the NEW queue, and blocked all updates to git in the meantime? I have to say I disagree, and I don't think that is a more friendly approach. Keep in mind that by request of the git-remote-bzr maintainer, git-remote-bzr was removed from contrib/ in the upstream git package. The code is not there in v2.0.0-rc4. What should the git-bzr package contain now? I continue to believe stable and testing have a purpose different from unstable. If you're saying that you'd like to block this version of git from graduating to testing until someone steps up to package git-remote-bzr, I won't stop you from filing an RC bug to block it. [...] > If anybody wants to maintain it, that person will certainly not be me. Okay. Alas, there's no easy answer for software that people use but no one wants to maintain. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140522193719.gv12...@google.com
