[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#534940: lintian: inconsistent reporting of affected files



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2011-01-18 03:23, Russ Allbery wrote:
> Niels Thykier <niels@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 following patches on the infra-513663 branch and I
>> intend to apply them on the master branch as well.  The patches will
>> remove ./ and / prefixes on file names in some of the checks.  If I
>> missed any checks let me know.
>>   I chose the "\.?/"-less prefix for two reasons; I believed most of our
>> checks does not use it (particularly checks/files, which is rather huge)
>> and secondly because Lintian::Collect tends to return the file names
>> without this prefix.
> 
> Thank you for doing this!  I'm in favor, and had just been holding off due
> to the amount of work involved.
> 
> We will probably want to bump the minor version for this change, since it
> will break a few existing overrides that will need the obvious updates.
> 

Hey,

I found out that ocaml and menu-format also suffered from this, so I
added those.  All of it has been pushed to the infra branch (except the
version bump, I figured we should wait until we apply the changes to the
master branch)

~Niels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJNNY/rAAoJEAVLu599gGRC29YP/2v9JfvOjdhHq78qVI+pMzzT
3vV4NEid2F5Ng0Z611bQGGXAQqaoHkvFrBW36N/nLGSMzQs38GMGOr3M97T7avZX
eZq5mc3oYPTS7pJ2Pox4cGblTvZeMmBjYcz7m7BVZk2eWsgfzKa+c+yh96CIk5aA
Si5rcSsn5YJONhF6eSPaMx45wNFvhbEtuj5eMT2p3B3F58ruEY0kR4BE8dcehnwi
j08q7lfFyskfCF5bBGKMAjDTrWq9vtJvaJtxkYHT4+/d7D2JcgEBNAw9F+h8QB1B
7AwYjDRh96ejmZos8dbO/twMrWIclxfcqm8Xq2y6rg3337ZBc7fqlowiIH1xKLZZ
iuudArOm2H2A2ZGEX/S+j334a4FbnebD2pHq53Y7GdsiZeZrW7sNbOB2emltSaGm
soJNkhSpvXyNQtumHfCuQzwvO/qVG5e/F9+aYVoQuRvqgiuIADMwcphmX3UDQKYL
WYtGocilGUEgc2BmPh+c6rP1BJtUsQPsKkHxpmzEvNLUP65bmE6jcnVJ3MDXs5jP
lmTNuznd01hb8gkBs8aZyMW8LAORlgdD8xv6dHK00/tGwqB18fHTdArDCq5CyE7X
WjxLKIcNTCbkX3WsMIfbce1hN7lZt0WGzDZRDRsLEpkMxjUy0OD/0TuAumT/qRru
gUU3i9Yq8ZNxaHKqhRxJ
=OzfW
-----END PGP SIGNATURE-----



Reply to: