Sean Whitton writes ("Bug#903392: want support for packaging-only maintainer
views"):
> On Sun 19 May 2019 at 11:24PM +01, Ian Jackson wrote:
> > dgit will look for the corresponding upstream source tag with an
> > algorithm like git-deborig's. In case that doesn't work there will
> > have to be an option to specify it explicitly.
>
> I previously modified git-deborig to expose the results of its algorithm
> if you pass --just-print, but there was some further blocker to having
> gdr start using that algorithm instead of reimplementing it.
It occurs to me that dgit has a further strategy available, which
would not be available (nor reasonable) for gdr, nor for git-deborig.
dgit will probably have to construct the tree corresponding to the
.orig in order to detect .orig discrepancies early enough to generate
a reasonable error message. (It has code for this already.)
Having got such a thing, it could hunt through upstream/master or
maybe other branch refs for a commit that has exactly that tree. If
(exactly one?) such a thing is found, it could use it.
dgit could even fetch from Vcs-Git and grobble around in there...
Whether any of this would be useful (or, indeed, sane) depends a lot
on maintainer workflows, about which we seem to know very little. I
definitely think that the right plan is for me to make dgit use the
existing git-deborig tag algorithm and then see if that is enough.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
