Simon Josefsson writes ("Bug#1124438: git-debpush should do something better
about baredebian+tarball"):
...
> As a user I really prefer if it didn't, but I don't know what the
> concerns are. I thought git-debpush was stateless wrt earlier upload
> history of the git repository, if that isn't the case I'll have to
> reclibrate my intuition.
See Sean's reply. One reason for doing it this way is that passing
a wrong quilt mode can't always be detected. With this history-based
automation, you don't normally have to pass --quilt so you don't have
the opportunity to make a slip and pass the wrong option.
> I don't think one should have to specify that: is there a reason
> tag2upload should not ALWAYS use the tarball from the archive, if one
> exists, instead of synthesizing one?
It does in fact indeed do that. If it can obtain the tarball from the
archive it will do so. And if there is a tarball in the archive
which it can't obtain (sadly this is possible), it generally fails
rather than synthesising and uploading a differeent tarball.
The issue is that our tag format has no way to say "there should be an
orig tarball" without also providing instructions for how to make it.
> I still have to test if 'git-debpush --quilt=baredebian+git' actually
> works for this package. Do you have any guess? Hopefully I can find
> some nit in the latest upload and test it.
If dgit build-source --quilt=baredebian+git works then tag2upload
should work too. Obviously the point of tag2upload is to avoid doing
all that tarball and dgit stuff locally but, since you ask, that's
the way to test things :-).
Regards,
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
