Hi Ian,
On Wed Jun 10, 2026 at 8:39 PM CEST, Ian Jackson wrote:
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.
Yes.
I think this is probably too unusual to special case. Often such a
0~ means there's no upstream at all.
It's not *that* unusual, as a lintian tag exists for this:
<https://lintian.debian.org/tags/new-package-uses-date-based-version-number.html>.
Still, it's nowhere near as common as the "v" prefix for version
numbers, so it's fair not to special case this.
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.
That makes more sense! I guess you are talking about gbp-import-orig's
upstream-vcs-tag option, but I don't get the uscan reference (maybe you
mean d/upstream/metadata?).
Feel free to close or merge this bug :)
