Sean Whitton writes ("Bug#1105759: Bug#1139658: git-deborig: should look for
tag without 0_ prefix"):
> I think there are probably many similar conventions that would have just
> as much an argument for being looked for by git-deborig as this 0~ one.
>
> It *is* more convenient for people if we support them and they don't
> have to edit gbp.conf. On the other hand, requiring the user to edit
> gbp.conf removes ambiguity, and we won't let git-deborig proceed unless
> the situation is unambiguous anyway.
I'm not sure there is a way to remove the 0_ at the start using
gbp.conf? I experimented with
[export-orig]
upstream-tag = %(version)s
in android-udev-rules and
$ gbp export-orig
gbp:error: 0_20260423 is not a valid treeish
I've implemented reading gbp.conf in git-deborig (and therefore
git-debpush) apropos #1105759. It honours [export-orig]'s
`upstream-tag` setting because (empirically) that's what you have to
set to make Salsa CI work.
If anyone has ideas about how this 0_-stripping should be configured,
please LMK.
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.