Nicolas,
On Friday, October 11, 2024 6:04:09 AM MST Nicolas Schodet wrote:
> > > About lintian report, I would like to have some advice on how to handle
> > > it rather than going directly with an override:
> > >
> > > I: nxt-python source: built-using-field-on-arch-all-package (in section
> > > for
> > > python3-nxt) Built-Using ${sphinxdoc:Built-Using}, [debian/control:34]
> > >
> > > I think this is a bug in lintian as this is required by sphinx, see
> > > https://bugs.debian.org/999785
> >
> > Just override the tag with a comment explaining why it doesn’t apply.
Note
> > that I haven’t spent the time to ascertain that you are correct about it
not
> > applying, but I trust your knowledge of the situation.
>
> I followed the advice here
> (file:///usr/share/doc/lintian/lintian.html#overrides):
>
> « Please do not override bugs in lintian, they should rather be fixed
> than overridden. »For tags Info and higher, I typically report the bug (or find the bug report) and then override the tag with a link to the bug report in the comments. That way, I can tell what I haven’t yet dealt with (I have lintian programmed to display Info and higher tags by default). When the bug is finally fixed, lintian will warn you that you have an override that no longer applies, so it is easy to remember to go back and remove it. > > [...] > > Don’t even worry about overriding pedantic or experimental lintian tags. > > Just ignore them if they are incorrect or not helpful. > > [...] > > Thanks, I will try to have a look at lintian to see if I can contribute > a fix for the .ico files and the setup.py long line. I think this should > falsely trigger too many times. That would be very good of you. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
