Hello, On Mon 19 May 2025 at 11:31am +01, Ian Jackson wrote:
> Package: dgit > Version: 13.0 > > Currently the upstream tag is not used by dgit, but it is used by > git-deborig or origtargz if the usere asks to make an orig tarball. > With tag2upload, the tag is typically present on the builder. > > In neither case, does this tag end up in a formally archived location > on Debian infrastructure. (It typicaly *is* on salsa.) > > Ideally the tag would end up on dgit-repos. There is a problem, > though: the git tag namespace is global (and there is no standardised > name for upstream tags). So dgit-repos cannot (and doesn't) allow > arbitrary tags to be pushed. > > We need to define a git representation for upstream tags which isn't > "put them under refs/tags/<upstream-tag-name>". Maybe a new subtree > under refs/. > > 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. This is indeed quite tricky. I think it's probably useful for dgit-repos to be doing this as part of Debian's mission to preserve upstream source code in a way that's easily accessible, if we can resolve the many edge cases relating to what the archive allows. -- Sean Whitton
signature.asc
Description: PGP signature
