>> To not have a chance of too many false positives, I would suggest
>> looking directly into the diff, so avoid upstream source. And do not
>> count the error as soon as you find that filename anywhere in the rules
>> file (that assumes the Maintainer takes care of it somehow).
> This is fairly trivial to do if we don't look in debian/rules and a bit
> harder to do if we do. Before I write the code to scan debian/rules,
> though, I wanted to check if you think there's some legitimate case where
> someone would create or modify this file in the diff and then remove it in
> debian/rules. I can't think of one, and hence am leaning towards just
> always flagging it as an error if that file is present in the diff.
I cant think of any, as you simply cant do anything with this file
besides removing it or you end up with an FTBFS...
--
bye, Joerg
graphviz (old license)
[...]
Changes
* Burn it! Burn it all!!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
