"Theodore Tso" <[email protected]> writes: > Are you really certain everyone who uses gbp also uses "gbp pq"? > [Citation needed.]
You are the first person I've heard of who uses git-buildpackage with patches applied, as a data point. I'm sure you're not the only person doing that! But I also thought the "standard" way to use it is patches unapplied. That doesn't necessarily mean using gbp pq. I used git-buildpackage with quilt for years before gbp pq was written. Everyone wants very simple Debian tools with very simple documentation (I do too!), but the problem with simple tools and even more so with simple documentaiton is that we have almost as many workflows as we have Debian contributors, and every one of them thinks their workflow is just the normal one. :) > No, I want to make sure that I am building the package in a hermetic > build environment. Which is to say, I want to build using sbuild so I > can make sure it builds correctly in the latest unstable environment > and using the minimal set of patches so I can make sure the > Build-Depends line in debian/control is correct, *before* I do an upload. Have you tried just running dgit sbuild? That invokes sbuild directly rather than git-buildpackage, so maybe that skips something that you're relying on, but that worked fine for me when I started moving away from git-buildpackage. Anyway, I think you are running into problems because you thought you needed to use all the gbp options because you're using git-buildpackage, but all those options do complicated things to handle patches-unapplied trees. Since you have a patches-applied tree, I don't think you need any of that and adding gbp- and --gbp and whatnot may just be breaking things for you. -- Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
