On Thu, Feb 12, 2026 at 09:40:25AM -0500, Theodore Tso wrote:
On Tue, Feb 10, 2026 at 09:32:29AM -0800, Russ Allbery wrote:
I have been using dgit with pristine-tar for years. It works fine with
pristine-tar. People have told you this repeatedly. Please listen to us
and stop repeating this blatantly misleading statement in every discussion
about dgit.
I use dgit with pristine-tar, but if I need to add patches in between
formal e2fsprogs releases, dgit is *painful*. If I need to upload to
stable backports, dgit just did't work.
I hear you that you found it difficult to get to work, but I literally
do these things every day that I'm working on Debian (well OK, I don't
upload to stable backports every day, but I have done it with dgit and
it was fine). To me, dgit is basically orthogonal to applying patches
in between formal upstream releases anyway; I do that sort of thing with
other tools such as "gbp pq", and dgit is just the way that I get them
into the archive.
If you've given up then I understand, but if you want to have another go
then feel free to email me (off-list) for help getting it working.
Part of this is because my workflow uses dgit plus gbp plus schroots,
with patches applied. Which is something dgit seems to only
incidently support, but the advantage of my setup is that if dgit does
blow up, and I can easily fall back to a pre-dgit workflow.
I think dgit intentionally supports all those things, not incidentally.
--
Colin Watson (he/him) [[email protected]]
