Package: git-buildpackage Version: 0.6.0~git20120415 Severity: normal Hello,
I saw #471581 before filling this bug but I believe that this design choice is counter-productive. Let me add some new elements to the discussion based on my personal experience: 1/ many packages remove files in their clean rules (because those upstream-provided files are updated/regenerated at build-time and would generate noise in the debian diff) 2/ if you have a clean tree and run "debian/rules clean" with such a package, the tree will no longer be clean from the git-buildpackage point of view because of those removed files. This means that you can't "git-buildpackage" twice in a row. I don't see what the "clean" call buys you since you already export the source tree and since you already complain when you have local changes. I would thus like to argue to change this design decision. If you don't agree I would like to have more explanations of what problems you're trying to avoid with this "debian/rules clean" call. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (150, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-2-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 Versions of packages git-buildpackage depends on: ii devscripts 2.11.6 ii git 1:1.7.10-1 ii python 2.7.2-10 ii python-dateutil 1.5-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 Versions of packages git-buildpackage recommends: ii cowbuilder 0.69 ii pristine-tar 1.24 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-3 ii unzip 6.0-6 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
