On Saturday, May 23, 2026 12:49:39 PM Mountain Standard Time Holger Levsen wrote: > On Sat, May 23, 2026 at 08:28:14PM +0200, Bill Allombert wrote: > > > 3.) should I override the lintian warning in dev-ref? > > > > Please don't. Override should be reserved to pathological cases where a > > package is a policy exception, not to hide lintian false postive. > > I disagree. (But I also think this is the least interest aspect of this bug > report.)
When lintian has a false-positive that can be corrected in the logic of the lintian check, I usually file a lintian bug report and override the false positive with a link to the bug report while I am waiting for it to be fixed. When lintian has a false-positive that is not possible for the lintian check to detect (there are lots of these, for example the tag very-long-line-length- in-source-file) then I override the lintian false positive with an explanation of why it doesn’t apply. Checks like these are valuable lintian tags because they help me find problems in the source code, like minified JavaScript. But they can also flag files that aren’t problems, and it is important to be able to mark those as overridden after they have been manually reviewed. Note that this isn’t a comment on the best way to handle this situation, just a note that overriding lintian false-positives is indeed the correct behavior in many cases. -- Soren Stoutner [email protected]
signature.asc
Description: This is a digitally signed message part.
