Please wait with release

Chris, Please wait with the next Lintian release until we have had time to hone the new and timely tag for Unicode trojans. It is hitting many false positives but I cannot make it any lower in visibility than experimental and pedantic. Jeremy and whoever else is interested should have a chance to

Re: suggestion for checking unicode characters against "trojan source attacks"

Dear Jérémy, > grep -r > $'[\u061C\u200E\u200F\u202A\u202B\u202C\u202D\u202E\u2066\u2067\u2068\u2069]' I implemented this in Perl both for file names, which I think may be more important, and the contents of all files that identify as text via file(1). The tag is called 'unicode-trojan'. [1] You

Bug#995492: lintian: Broken --fails-on=none as default never got reverted

Hi Guillem, On Fri, Oct 1, 2021 at 6:57 PM Guillem Jover wrote: > > Unamused, I am sorry that happened. Did I not accept your patch in full? [1] Kind regards Felix Lechner [1] https://salsa.debian.org/lintian/lintian/-/commit/3758bfafd5dd742c327f2312dac8e3a71b1f036e

Processed: avogadrolibs: b-d on python3-all-dev, but not built for all supported Python3 versions

Processing control commands: > affects 995981 src:avogadrolibs Bug #995981 {Done: Chris Lamb } [lintian] rules-require-build-prerequisite gives bogus advice Added indication that 995981 affects src:avogadrolibs -- 995981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995981 998469: https://