Joey Hess <jo...@debian.org> writes: > Gergely Nagy wrote: >> I had a similar issue a couple of days ago. For me, putting dh's >> catch-all rule (%) last in my debian/rules file worked around the >> problem. > > If you have a test case for this I would be happy to receive it in a > separate bug report.
Hrm, I tried to come up with a simple test case, but couldn't. And apparently, the package in which I did this apparently does not exhibit the problem anymore, either. So must have been something fishy in my environment. But for the record, my problem was that upstream had a build/ directory, and debian/rules build wasn't building, since it found the dir and considered it up-to-date. As a quick workaround, I wanted to add a build-stamp phony target as a dependency to build, and when I put that after the % rule, it didn't work at that time (read: it still didn't build, but considered the directory up-to-date), so I moved it before the cathc-all rule, and voila. However, when I moved the stamp-foo to the end now, it still behaves properly now. So either I fixed something in the packaging that I did not notice, or there was an issue with my environment which went away sometime during the past week. In any case, sorry for the noise. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
