Control: severity -1 normal On Fri, 28 Oct 2016 12:27:09 +0100 Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: > Package: git-phab > Version: 1.0.0-2 > Severity: serious
Well, I disagree it’s serious, at least, it’s not a serious bug in git-phab packaging. > You've told me you're going to stop using dgit. I really like some things about dgit, but the fact it doesn’t forgive people’s mistakes makes me uneasy about using it. > That's fine, of > course, but the current state of the dgit-repos and the archive are > not consistent. Even if a new version is uploaded, anyone doing > archaeology will probably find that their attempts to use `dgit > import-dsc' on git-phab 1.0.0-2 will fail. Honestly, keeping that state might have proven my point, but, well, I tried to convince you yesterday and I failed, and I don’t wish to continue the argument. > You requested that I rewind history on the dgit git server, or delete > the git-phab repository there. I have declined to do this on the > grounds that this history should continue to be available to dgit > users; that deleting or rewinding there is contrary to the design and > therefore to the promises made to downstreams, so there may exist > downstreams or mirrors which would break or signal an exception; and > that either of these proposals would cause `dgit import-dsc' to fail > on historical git-phab .dscs (from snapshot.d.o). > > Having slept on it, I still think that is the right decision. > > I think the best way to sort this out is for me to do a dgit-based > no-change NMU, of a branch which is descended from the commit named in > 1.0.0-2's .dsc as well as from 1.0.0-1. This will ensure that the > commits referenced by all previously-uploaded git-phab .dsc's will be > findable. > > For this to work it is not necessary for my NMU to actually make it to > the archive. So unless you object I intend to make this NMU to > DELAYED-14. You may then use dcut, or upload a later version. If you wish to fix the dgit repository, feel free to do so, but please make sure that whatever you upload doesn’t end up in the archive. > If you object before I actually make the NMU I can arrange to simulate > the effect of my uploading to DELAYED-14 and you running dcut, by > making my NMU and pushing it only to the dgit git server but arranging (the rest of the email’s got cut off when replying via a browser link — is that a limitation of the BTS?) > I intend to use the version number 1.0.0-2+nmu0dgit but I'm happy to > use a different version number if you prefer - just say. I don’t have an opinion on what version number it should have, as I don’t plan to use dgit for this package anymore. I’m not sure about other packages, but the dgit repo for git-phab is borken to the point of no return, and as you refuse to unbork it properly (for my definition of ‘properly’) I don’t care too much about the exact way you are going to make it internally consistent. -- Cheers, Andrew
