Hello, On Wed 30 Jan 2019 at 07:24PM -0700, Sean Whitton wrote:
> When the user passes --delayed, dgit could check > https://ftp-master.debian.org/deferred/status to see whether the .orig > is already in DEFERRED, and if so, remove it from the .changes file. > > (I was able to work around this by manually qremoving the .orig from the > changes, resigning the .changes and .dsc, and uploading again; I > appreciate this kind of messing about is discouraged with dgit, but I > was keen to avoid another roundtrip with my sponsee.) Hmm. After this, with both the -1 and -2 uploads in DEFERRED, I tried to `dcut cancel` the -1 upload so that I could be sure an ftp-master would not try to review -1 in the interval before -2's DEFERRED timer ran out. This caused queued to delete the .orig.tar, such that, presumably, the -2 would be REJECTed immediately upon its DEFERRED timer elapsing. Nice. I have had to `dcut cancel` the -2 upload too and ask my sponsee for a -3 changelog entry. So maybe dgit should simply look at DEFERRED, and if the package is already there with the same upstream version number, say "you should `dcut cancel` that upload before pushing this one" to avoid the situation I got myself into. -- Sean Whitton
signature.asc
Description: PGP signature
