Trent W. Buck wrote: > dh_auto_clean didn't seem to be called often enough in my real > program, so I wrote a little script to make a test package "x" and run > dpkg-buildpackage in it, twice. Attached is the script (x.sh) and the > typescript from running it (typescript). > > Note that the second invocation does not call dh_auto_clean. I > suspect this is related to the existence of the debian/x.debhelper.log > file during the second run.
I don't reproduce this problem when using your script with debhelper 7.0.15 or 7.0.16. > fakeroot debian/rules clean > dh clean > dh_testdir > dh_auto_clean > dh_clean This dh_clean removes the debian/x.debhelper.log file. > debian/rules build > dh build > fakeroot debian/rules binary > dh binary None of these call dh_auto_clean, so it does not appear in the log at the end. [EMAIL PROTECTED]:/tmp/x-0>grep clean debian/x.debhelper.log zsh: exit 1 grep clean debian/x.debhelper.log > dh clean > dh_clean [EMAIL PROTECTED]:/tmp/x-0>fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean dh_clean > dpkg-source -b x-0 > dpkg-source: info: using source format `1.0' > dpkg-source: info: building x using existing x_0.orig.tar.gz > dpkg-source: info: building x in x_0.diff.gz > dpkg-source: error: cannot represent change to > x-0/debian/x/usr/share/doc/x/changelog.gz: binary file contents changed > dpkg-source: unrepresentable changes to source dh_clean removes debian/$packagename. Your log above shows dh_clean being run, so how can debian/x exist at this point? Guess: You have DH_OPTIONS or DH_ALWAYS_EXCLUDE set in your shell's environment with a value that causes dh_clean to not delete debian/x.debhelper.log and debian/x. -- see shy jo
signature.asc
Description: Digital signature
