Hi Gavin, On Wed, Apr 05, 2017 at 04:56:21AM +0000, Gavin Lambert wrote: > Package: git-buildpackage > Version: 0.8.12.2 > Severity: minor > > Dear Maintainer, > > "man gbp-buildpackage" seems to imply that "gbp buildpackage" will issue > "debuild clean" by default. It doesn't actually do so; it calls > /bin/true instead. > > Also, according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846016 > this is no longer valid syntax and needs to be changed to "debuild -- clean". > > When it doesn't clean by default, two successive calls to "gbp buildpackage" > with default configuration results in the second call failing due to dpkg > output files left behind by the first call (resulting in a "git status" > error output), unless the repository already contains .gitignore files that > cover those files. Is it assumed that this is always the case?
Having a cleaner by default would force people to set up two things if they want to switch builders (with the exception of --git-pbuilder which does this for you). Since most people use either sbuild, pbuilder or --export-dir there's no point in running "debuild -- clean" or any other builder. We should have a better default for --git-builder (which can happen once git-pbuilder is clever enough to build the chroot if missing). Cheers, -- Guido
