On Thu, Feb 12, 2026 at 05:37:26PM +0000, Ian Jackson wrote:
> dgit-maint-gbp(7) is describing patches-unapplied, which is the usual
> way that people use gbp (and gbp pq etc.)
I don't know why you say that --- "gbp buildpackage" works just *fine*
for me and I'm using a patches applied workflow. In fact, that's what
I fall back to after "dgit gbp-build" fails for me.
I use gbp buildpackage because I have that set up to do a hermetic
build using sbuild and schroot. It takes care of using pristine tar
to generate the tarball, so I don't have to rely on origtargz
downloading the tarball (which is a real drag when I'm running gbp
buildpackage while on an airplane or a cruise ship).
> > I do a git cherry pick, and then manually do a "git am -o
> > debian/patches" and then edit the resulting file to meet the DEP-3
> > standards.
>
> Gosh. Don't you find that tiresome?
It's annoying, but most of the time I work on an upstream first model.
Which is to say, if there are sufficient bugs that I really need to do
a debian release, I'll do an upstream release so that non-Debian
distributions can also benefit, and then I'll do a debian release.
The only exception is when we're in a release lockdown.
> BTW IMO you should stop worrying so much about DEP-3 and just use
> git-format-patch. That's what gbp pq does - and is very common
> practice in Debian. There was some discussion somewhere recently
> about updating DEP-3 to recommend output like git-format-patch's.
Agreed, DEP-3 is pretty pointless given that all of the metadata
information is in the git repo. But it's also not *that* hard to
start with "git format-patch -o debian/patches", and then masssage the
output slightly. If did it more often, I'd create script that
automated it, but as I said, modulo release freezes, I generally use
the upstream first model anyway.
> dgit build-source
Sure, but that doesn't do a hermetic build.
> I think you probably just need to stop passing it --gbp aka
> --quilt=gbp, which is documented as follows:
I'm not passing it --quilt=gbp. I'm just running "dgit gbp-build".
Hmm... will something like "dgit --quilt=nofix gbp-build" do what I
want? And if so, I can put something like
[dgit "default"]
build-products-dir = /tmp/gbp
quilt = nofix
in my git config file? If so, you might want to document that in
git-maint-gbp, and not assume that everyone using gbp is using
patch-unapplied. I certainly don't. (In fact, I don't even know how
you can use gbp with a patch-unapplied orkflow; I didn't even know
that was a possibility, in fact.)
Cheers,
- Ted
