Phil Wyett <philip.wy...@kathenas.org> writes: > On Tue, 2024-08-27 at 12:31 -0700, Phil Hagelberg wrote: >> Phil Wyett <philip.wy...@kathenas.org> writes: >> >> > The Fail To Build From Source (FTBFS) still remains. >> >> As far as I can tell, that problem is happening because you're on a >> machine that doesn't have git installed, despite the fact that >> debian/control declares a Build-Depends on git. > > I only build with pbuilder and sbuild. > > What are you using for your builds?
I use `gbp buildpackage' to do my builds. I tried using pbuilder at one point, but it failed with a rather incomprehensible error: $ gbp buildpackage --git-pbuilder gbp:info: Building with (cowbuilder) for sid gbp:info: Performing the build Base directory /var/cache/pbuilder/base.cow does not exist gbp:error: 'git-pbuilder' failed: it exited with 1 Web searches and documentation were not helpful in my attempts to solve or even understand the problem, so I gave up on it and just used gbp on its own, since that works fine. I didn't do the initial packaging work; I've just been taking it over since the original packager hasn't been active. So I don't have a lot of context beyond the notes they left. Is it a requirement to make the package pbuilder-compatible, and if so, does the build-dependency on git not work under pbuilder? Why is it that you use it? If pbuilder is the right choice for this package, how can we ensure pbuilder installs git? The upstream release as it exists today does depend on git in order for its test suite to run, which is why I consider declaring that dependency to be the simplest solution, but if that doesn't work reliably, removing it from the test suite would also be easy. thanks, Phil
signature.asc
Description: PGP signature
