Ian Jackson writes ("Bug#1106073: dgit should convey upstream git tags to
dgit-repos"):
> Should it be indexed by the Debian package version, to allow different
> revisions of the "same upstream version" to be based on different git
> tags? That's an anomaly which is current permitted (I think, by
> accident) in the Debian archive and therefore by the current system.
I thought of another question.
For an upload which reuses existing origs, we typically don't
regenerate those origs nor check them against any git information
(except as part of quilt fixup). In particular, we don't check them
against any git tag(s).
We should only archive an upstream git tag if we know that it
corresponds to the package. With tag2upload, that could be done by
archivng the tag iff we used it with git-deborig.
When using dgit on the uploader's system, dgit already looks at the
archive to tell whether the orig needs to be included in the .changes.
It could archive the tag under the same circumstances. But it doesn't
know what "the tag" is - and there may not even *be* one.
The interactions with pristine-tar are also interesting. Presumably
we'd want to archive all the pristine-tar data? See #1106071.
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.
