Hi Niels, Niels Thykier wrote:
> Package: lintian > Version: 2.2.14 > Severity: minor > > Hi > > Looking at junitperf's lintian warnings/errors[1] I noticed that lintian > said "debhelper-compat-not-a-number", followed by deprecated compat > version 4. It turns out that the compat file had a trailing whitespace, > which triggered this. > > I think lintian should either have a separate tag for this or at least > have the tag info updated to include that whitespaces triggers this error. > > Alternatively lintian should simply ignore whitespaces in compat during > this test (this is what it does on the deprecated compat version test > anyway). Lintian is following debhelper's behaviour here, so if a package triggers debhelper-compat-not-a-number it means that debhelper's behaviour might not be the one expected either (depends mostly on how perl turns a string with non numeric characters into a number). I guess the right thing to do here is to add a bit more details to the tag info. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-lint-maint-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org