Re: Override paths for the very latest lintian.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2011-04-28 01:02, David Kalnischkies wrote:
> On Wed, Apr 27, 2011 at 23:59, Mats Erik Andersson
> <mats.andersson@gisladisker.se> wrote:
>> This potentially could make fairly many override instances
>> inapplicable for present day packaging, so I hope to hear
>> an initiated voice here, stating that the new behaviour is
>> intended. I am not able to get the altered behaviour verified
>> in the changelog of lintian, so I send this message instead.
>
> Please have a look at: 201102232247.30644.geissert@debian.org
> http://lists.debian.org/debian-devel-announce/2011/02/msg00009.html
>
>
> The change in question seems to be in version 2.5.0~rc1 btw:
> + [NT] All checks now report files without any "./" or "/" prefix.
> This may break existing overrides. (Closes: #534940)
>
>
> Best regards
>
> David Kalnischkies
>
>
Hi
A quick side note to this; if the tag in question is a non-fatal
auto-reject tag[1], you may still need the old override (with the
initial slash). Last I heard (16th of April[2]) the machine processing
uploads still had Lintian 2.4.3.
~Niels
[1] One of the tags that will cause your package to be auto-rejected on
upload unless it has been overridden.
[2]
http://nthykier.wordpress.com/2011/04/14/lintian-2-5-0rc1-and-newer-breaks-overrides/#comment-11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJNuRToAAoJEAVLu599gGRC8CwP/j0dXMEinFAbTzX5HghQH7Ik
gGnbtalnKsIPUgO/8xwta1cp5HenR6OrJ0nvZhJRdTPpoIk9SxcfNInOBElnM2Ak
jPsI/Lz0csjEWhO6riRrcOl2Ud+AkHqlAvW7MdElPLVwuqJOkpW4OgC0473j+y2F
/GTR8Nn3CJCClJ2T/K+TF5MtZ65OrV+ETpVxEvR3yCjK1slu7UscSTmu7dUzUwWQ
33kUabC+ZDFGafZYQShMq4jGl0uP9Jvjb5xGWP4HcpZb5e8cYxsp/6hdMSR/7iTg
M+n8T1hQrzh7rJH6MA4F/ZmFOXXSrps1ODUacN/SrFKRa2fXjfz7v3tmdPPhE1aM
M2VFttWGfb1CUohqpgbbvd01If6bjlesxPCfVPm10tj1Zsl6O1ASJKzKiwvbIHyW
2uoIRt5JrjODSb3Xy/yVgT5AJ3yjkSBsEZBqQktitxIyK9kpCNTAyW5dtykdrOki
6pKQGeXSigjknaIzpSVPGEF2uZImU/X8ixq1nXkoHqBRfRrddppWtf1R+E5RwPgC
bxhr1Ps6f+Kb03yhO+CnHBQOO2Q2bXchfx4HRhjPGAIBYrtkdBNMQTyckYgjHFrt
3Sb2S7kTtSsQF7c5XOkZrrQLxoaxwDOB8SdRiyQIb9oZNMpGygJtoXug6saw2cMg
xQAkcpMcf7qr0xGExdlO
=yxen
-----END PGP SIGNATURE-----
Reply to: