Marco d'Itri writes ("Re: Bug#1105759: git-debpush upstream tag confusion"):
> On May 14, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
> >Maybe we could talk to the gbp maintainer and ask if there could be a
> >common *git* config option (set with `git config`) for this question.
>
> This is not very useful, because the tags format is an intrinsic
> property of the repository and hence it should come with the repository
> itself: or else users would need to set it every time a source package
> is cloned.
I think you are pointing out that the tag format is a property of the
upstream project and should be represented in-tree. Since there isn't
an upstream standard, we should havwe a standard in debian/.
And...
> Until we will have a more neutral standard mechanism to declare this
> kind of things then I think that git-debpush and git-deborig using
> debian/gbp.conf would help a lot since many packages use it.
... that gpb.conf is that standard.
This might involve a dependency on git-buildpackage so that we can run
gbp-config. I doubt we want git-debpush to pull in the
git-buildpackage package. git-buildpackage has a *lot* of
dependencies.
Maybe gbp-config could be factored into its own package or we could
reimplement its algorithm. We should possibly consult with the gbp
maintainer.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> 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.
