On 04-10-14 00:44, Paul Wise wrote: > They are also not for > experimental, pedantic or info level issues. So all of these issues > should either be ignored or fixed but not overridden. I have seen this before and I (as a maintainer) don't understand this comment so bold as it is put here. I would say that overrides can help you to see which items you (or your sponsee¹ in case of sponsorship) already investigated. In the case of pedantic and info, you could even say that an override is allowed when the item might be still valid but for whatever reason is not going to be fixed (soon). I run the full lintian on nearly every build I do and it help me to keep track of the issue I think I still need to resolve. As long as each override has an extensive and valid explanation, I don't see anything wrong with that and I prefer it over having to scroll through items that are ignored anyways. As a sponsor, I always check all the overrides and only accept those I understand. Documenting the reason goes a long way for that (as well as it helps in the future to remember the original reasoning). Paul ¹ Sorry for my English in case this word is wrong, I mean the person that gets sponsored.
Attachment:
signature.asc
Description: OpenPGP digital signature