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

Re: Status on Lintian 2.5.0~rc3



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

On 2011-04-19 23:49, Steve Langasek wrote:
> Hi Niels,
> 
> [..]
> 
> Sorry for the delays getting this to you.  The attached patches take care of
> the most critical multiarch checks.  Along the way I found that
> data/binaries/multiarch was being used to incorrectly suppress warnings
> about files forbidden by policy, so the first patch removes this wrong file;
> and that data/files/triplets is already used for per-architecture filesystem
> paths, so I've updated this to use the final multiarch paths based on
> DEB_HOST_MULTIARCH instead of DEB_HOST_GNU_TYPE (second patch).
> 
> The third patch in the series adds the new check for multiarch-support, the
> one we need in place to make sure developers aren't breaking the world as
> they upload libraries.  I strongly believe this should be an archive check,
> fwiw.
> 
> The fourth patch fixes up the test suite for binaries-multiarch - since
> i486-linux-gnu is no longer treated as a multiarch directory (because it
> isn't), the test case fails to trigger the error.  We may want an additional
> test case later to warn about /usr/lib/i486-linux-gnu in general, but that's
> a lower priority.
> 
> I'm sorry to say I haven't included a test suite change yet to go with patch
> #3.  I'll work on that, but can't promise when I'll have it done.
> 

Yay, committed - I will hit the release button tomorrow [1] unless
anyone has any comments/objections to the patches.
  Steve, have you communicated the request to make
missing-pre-dependency-on-multiarch-support an auto-reject to the FTP
masters?

~Niels

[1] Probably between 15 to 24 hours from this message.

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

iQIcBAEBCAAGBQJNrwAWAAoJEAVLu599gGRCi7QP/03uW4PNeeLWZhDt8qeyN/kz
qB0qvmARBC0yERH3LvqZ6JLlxYu9xaUTzXBkySuerlZUloFECx+dLkqvllwBDFVI
dSbvZ9783ZKjzVfMw8bMHTUXOmIXCxTWoJtBbJOAZtone+UHRQO0R0HElaBPX0tM
L2kBPwkZ07vB6ia8E8Gjx2RlrMatfqkpTwdagF8SKQXESUUr3C3QpG6D2987lsks
agOGxsKRnYGDVN8HR1NDpewzfvGiS9bUDcUI9TsZ9yWUQ7D/o2XZFqvIOr4u3uwC
o9RDleZw1DUVJYgFK2zRJkIgOAsszY706Vd7eId7oSew9gfMq7+5bBU11dtQEtV0
2sFh8vaj3nXmIPR5llXlLk22FnDACq8Sn3fi9Pc/l3ZoI7VtN9JxDASP7UbebSal
zBpDQnidBUTnqS8eMwmtRd3OE0QtoBdTB61ydgGwxL94N1HR48GFCCJk1YAQOUvA
jftzPImtlREXvUL5eYsfBB/XM6kV7RgFylO0lM22Mbv3Kctwy1jii/V5dHGNwtbd
EvcjxZjODr4RJtHz9AzAvA0GaTf+6sjQ5JADU3MdB7H0+eZ2JWWL5Eja+PlmQiMl
S1yTE57A1xq7SVxHFfm9fOKZLsWLqi706KwtC6ganx0WD5t2SRYjChZ4U1zLbCBB
/RBBhpLoziIlD8dv6fkc
=Rrbx
-----END PGP SIGNATURE-----


Reply to: