Package: dgit
Version: 1.9
Severity: normal
Running dgit git-build on my git checkout of bugs-everywhere commits a
patch into quilt that include a file that is in .gitignore.
The git repo:
git+ssh://git.debian.org/git/dgit-repos/repos/bugs-everywhere.git
The .gitignore:
*.pyc
build
dist
doc/man/*.1
doc/.build/
doc/libbe/
.be/id-cache
libbe/_version.py
How to reproduce:
apt-get install bugs-everywhere
apt-get source bugs-everywhere # to get the tarball (?)
git clone git+ssh://git.debian.org/git/dgit-repos/repos/bugs-everywhere.git
cd bugs-everywhere
be list # make the cache of bugs generated
dgit git-build
Expected result:
the package is built as usual
Actual result:
the package quilt series has an extra entry for .be/id-cache.
$ diffstat
debian/patches/auto-1.1.1-3-3caf93f13fc59943cc6162949b57ffdf57daad25-1386434682
.be/id-cache | 411 +++++++++++++++++++
interfaces/web/static/scripts/GPL-LICENSE.txt | 278 +++++++++++++
interfaces/web/static/scripts/MIT-LICENSE.txt | 20
interfaces/web/static/scripts/jquery.corners.html | 465 ++++++++++++++++++++++
interfaces/web/static/scripts/jquery.corners.js | 405 +++++++++++++++++++
5 files changed, 1579 insertions(+)
The latter 4 are okay, the first one is wrong, as it is in my .gitignore.
Of course, maybe it's my mistake in the first place to run commands on
the source tree, making it unclean, but it took me a while to notice
this file was there because git status wouldn't show it to me, because
it's in .gitignore. Furthermore, I was expecting git-build to build
the package in a separate checkout, the way git-buildpackage usually
does... In fact, git-buildpackage uses cowbuilder to build the package
in a chroot normally, so I am not sure what is going on here.
-- System Information:
Debian Release: 7.2
APT prefers stable
APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
