Bug#534940: lintian: inconsistent reporting of affected files

2011-01-18 Thread Niels Thykier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2011-01-18 03:23, Russ Allbery wrote: Niels Thykier ni...@thykier.net writes: I guess I am biting the bullet now. It turns out that with the pre-sorting stuff, some of the checks (e.g. checks/binaries) now modify the list when they add

Bug#534940: lintian: inconsistent reporting of affected files

2011-01-17 Thread Russ Allbery
Niels Thykier ni...@thykier.net writes: I guess I am biting the bullet now. It turns out that with the pre-sorting stuff, some of the checks (e.g. checks/binaries) now modify the list when they add their ./ prefix, causing other checks (e.g. checks/shared-libs) to fail. I have made the

Bug#534940: lintian: inconsistent reporting of affected files

2009-06-29 Thread Russ Allbery
Andreas Beckmann deb...@abeckmann.de writes: the way affected files are reported by linitian is inconsistent, some tags report them with a leading './', others don't. E.g. shared-lib-without-dependency-information ./usr/lib/libfoo.so.1.2.3 shlib-with-non-pic-code

Bug#534940: lintian: inconsistent reporting of affected files

2009-06-28 Thread Andreas Beckmann
Package: lintian Version: 2.2.12 Severity: normal Hi, the way affected files are reported by linitian is inconsistent, some tags report them with a leading './', others don't. E.g. shared-lib-without-dependency-information ./usr/lib/libfoo.so.1.2.3 shlib-with-non-pic-code