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? -- System Information: Debian Release: 9.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-70-generic (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages git-buildpackage depends on: ii devscripts 2.17.2 ii git 1:2.11.0-2 ii man-db 2.7.6.1-2 ii python-dateutil 2.5.3-2 ii python-pkg-resources 33.1.1-1 ii python-six 1.10.0-3 pn python:any <none> Versions of packages git-buildpackage recommends: ii cowbuilder 0.85 ii pbuilder 0.228.6 ii pristine-tar 1.38 ii python-requests 2.12.4-1 Versions of packages git-buildpackage suggests: pn python-notify <none> ii sudo 1.8.19p1-1 ii unzip 6.0-21 -- no debconf information
