Package: git-debpush
Version: 12.12

Hello,

I had thought that the way tag2upload passes --trust-changelog to dgit
would mean that it would overwrite an unacknowledged NMU, like how dput
does.  It turns out I had forgotten some subtleties of how
--trust-changelog works and in fact what will happen is that the upload
will fail before it reaches gideon.

When we designed the basics of tag2upload we considered it important to
minimise the ways in which an upload might fail, that git-debpush would
not detect.  That's one core reason for always using split view.  The
idea is that if the maintainer has already pushed their tag to salsa
then we should only fail if we discover a really serious problem.

I'm not sure that an unacknowledged NMU counts.  Indeed, it's fairly
user unfriendly to have a debian/1.1-1 tag on salsa but the archive
still has debian/1.0-9.1 and therefore your upload doesn't happen.
It's not how Debian usually works.

It seems worth noting that the NMU will still be on dgit-repos so we do
preserve it in some sense even if we switch to unconditionally
overwriting it.  WDYT, Ian?

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply via email to