While I have fixed this bug in git, I just want to point out a few things about your bug report.
Pavel Reznicek wrote:
> after upgrade of debhelper from 7.4.11 to 7.4.13, the dh_auto_clean stopped
> building a package due to errors like these:
"a package" -- It would be helpful to say *what* package.
> dh clean
> dh_testdir
> dh_auto_clean
> make -j1 distclean
> make[1]: Entering directory
> `/home/reznicek/deb/root/install/root-system-5.26.00b-1'
I had to read it a second time to see that I could figure out the
package name from this.
> Obviously, with a clean source, there does not exist Makefile yet
Except that, when I actually looked at the current source for the
current version of your package in the archive, the first thing I saw
was a Makefile.
> PS: There is a simple workaround by overriding dh_auto_clean to run a dummy
> ./configure first.
I actually think this is the correct thing to do for your package even
after this is fixed. The Makefile does an evil thing that prevents any
testing of whether targets exist from working, since it always prints
out a message, no matter what target is being run, if it has not yet
been configured.
config config/Makefile.:
ifeq ($(BUILDING_WITHIN_IDE),)
@(if [ ! -f config/Makefile.config ] || \
[ ! -f config/Makefile.comp ]; then \
echo ""; echo "Please, run ./configure first"; echo ""; \
exit 1; \
fi)
Debhelper 7.4.11 only happened to do the right thing by accident, since
it only looked at the first, empty line of this message. Arguably, it did
the *wrong* thing in general.
Since any upstream change to this Makefile could easily break debhelper's
heuristic, and since I can't guarantee that debhelper will be able to retain
bug-compatability with its test in the future, you should work around it
somehow in your package. Not running dh_auto_clean may be the best thing.
--
see shy jo
signature.asc
Description: Digital signature
