Andrea Pappacoda writes ("Re: Bug#1139658: git-deborig: should look for tag
without 0_ prefix"):
> On Wed Jun 10, 2026 at 8:39 PM CEST, Ian Jackson wrote:
> > 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>.
That's something subtly broader. That lint covers also cases where
upstream don't make tags at all. TBH, I don't have a strong feeling
about a special case for this, but I think we should focus our efforts
on the general solution:
> > Currently both uscan and gbp have separate config files for this.
...
> 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?).
Yes, in gbp, upstream-vcs-tag. Weirdly, gbp import-ref doesn't seem
to support it. (As you know, in our opinion, one should generally not
use gbp-import-orig, common practice in Debian notwithstanding.)
In uscan this is
mode=git
matching-pattern=refs/tags/...
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.
