Andreas Tille writes ("How is the original tarball obtained in tag2upload"):
> just a question which I hope was not addressed before in this long
> thread I have no chance to follow completely. If it was just answered
> simply point me to the archive (or alternatively the tag2uplod doc is
> its described there): In many teams we keep the metadata about the
> orig.tar.$COMPRESSION tarball in pristine-tar branch. In most cases
> this works flawlessly but I've observed some exceptions and read about
> potential problems with pristine-tar. How is the problem to get the
> original tarball solved in tag2upload?
Firstly, if there is an orig in the archive, the t2u robot will use
that. Failing that, it will use "git-deborig" which will call
"git-archive". Currently there isn't any support for pristine-tar;
that would be possible in principle.
Note however: right now you can't do a source-only upload of a new
upstream version, and tag2upload only supports source-only uploads.
So this situation generally won't arise: someone will have had to
upload the orig.tar.gz the old way.
This isn't brilliant. If source-only uploads of new upstream versions
become supported, it would probably be worth t2u supporting
pristine-tar for origs.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> 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.
