Hi Jari, Sorry to comment on an old bug, but this is still an issue.
If there's no way for package maintainers to automatically ignore false positives, this tremendously reduces the usefulness of blhc, by causing a form of alarm fatigue: People and processes (like CI) will ignore blhc failing, assuming it is a known false positive, and will miss new issues being flagged. On Fri, Oct 21, 2016 at 08:50:32AM +0300, Jari Aalto wrote: > I think the request is for reading configuration file at startup: > > <current directory>/.blhc-ignore OR if not exists, search ... > $HOME/.blhc-ignore I don't think expecting a local file works very well: - ~/.blhc-ignore wouldn't allow using different rulesets for different packages, and doesn't work for collaborative packaging workflows (where we would want to keep the overrides for a package in its repository) - ./debian/blhc-ignore works for (most?) collaborative packaging workflows, but doesn't work with the build logs checks done on [qa.d.o/bls] (also exposed on tracker.d.o) [qa.d.o/bls]: https://qa.debian.org/bls/ Would it be possible to embed the overrides into the build log itself? Best, nicoo
signature.asc
Description: PGP signature
