* Soren Stoutner <[email protected]> [2024-10-09 20:57]: > I believe a bunch of these were answered by Jeroen, but I will answer them as > well in care you still have any questions.
> > About bugs #885467, #937175 and #773201: they were closed when the
> > package was removed, should I re-open them before the upload, or is
> > it handled at upload time?
> You should reopen them after the upload, but only if you think they
> still apply. For example, #937175 won’t apply, because anything you
> build in unstable right now has to work with Python 3.
Following Jeroen advice, I reopened them. I will see if they are closed
properly once package is accepted. As the package name has changed… it
could go wrong, I don’t know.
> > 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. »
> [...]
> 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.
Thanks for your kind review,
Nicolas.
signature.asc
Description: PGP signature
