On Mon, Jan 16, 2017 at 05:38:30PM +0100, Fabian Greffrath wrote: > I think that nowadays this is even triggered by e.g. updating the > compiler.
Ah, good. Without looking I thought it might have been a clever hack added to the chocolate-doom autofoo, but I'm happier if it's more widely used. > "make distclean" should remove */Makefile.in, if I remember correctly. > There is also "make mrproper" which remove even more stuff. I think that suggests that a make distclean might be needed on the "debian/rules clean" chain, if it isn't there already. > > Let me try from a totally clean checkout. > > Or maybe try "git reset --hard HEAD" first. Clean checkout works (of course), git reset --hard does not fix this for my existing checkout. So in summary, I think it is possible, using only a sequence of "supported" steps (make, make clean, etc.) to get the package tree into a state where "debian/rules clean" will fail, and the package won't continue to build. But I can't say for sure what those steps actually were. It's still possible I am just being an idiot, but I think there is probably a (minor) bug somewhere and squashing it would prevent this from happening. I'll keep this package tree around to poke at further in the future, but I wouldn't treat this as a high priority issue (and I don't intend to work on it further just yet, higher priority things :))
signature.asc
Description: Digital signature
