Andrea Pappacoda writes ("Bug#1139658: git-deborig: should look for tag without
0_ prefix"):
> Hi! For a changelog entry like "0~20260423-1", git-deborig currently
> tries to generate the orig tarball using the 0_20260423, v0_20260423,
> and upstream/0_20260423 tags.
>
> The issue with this is that the "0~" prefix in the changelog is used as
> the upstream version number is a date, which would sort newer in the
> case in which upstream changes to a regular version numbering scheme.
>
> This means that the upstream tag is actually just "20260423", without
> the "0_" prefix, and it needs to be manually supplied by the user to
> generate the tarball.
So, just to make sure I have understood correctly:
In this package upstream do make tags, but their tags are named things
like `20260423`. In Debian we have the `0~` for the reasons you
describe. What you ask is for git-deborig to guess this upstream tag
format in this situation.
> Would it make sense to special case this convention and automatically
> look for tags without "0_", like it's currently done with the "v"
> prefix?
I think this is probably too unusual to special case. Often such a
0~ means there's no upstream at all.
Instead, I think this should be handled as follows:
* Somewhere in the git tree's debian/ directory there should be a
config file that specifies the tag convention.
* git-deborig (and git-debpush and other tools) should honour it.
Currently both uscan and gbp have separate config files for this.
So, in summary, I think this would be fixed by a fix to #1105759,
CC'd.
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.
