Bug#1042428: qa.debian.org: Missing description for lintian warning tags (https://udd.debian.org/lintian/?packages=)

[Christian Buhtz]

Package: qa.debian.org
Severity: wishlist

Dear Maintainer,
I'm not sure if I'm at the right place here. I know not much about Debians
infrastructure.

This is about

https://udd.debian.org/lintian/?packages=backintime

There are two Issues, one with "groff-message" tag and one with "dbus-policy-
in-etc" tag.

To less experienced users it is not clear what this tags do mean. The
explanation should be linked somehow.

This would improve the workflow for new contributors and also attract potential
new contributors who are not familiar with Debian.

Kind
Christian

[Sebastiaan Couwenberg]

On 7/28/23 09:09, Christian Buhtz wrote:
> To less experienced users it is not clear what this tags do mean. The
> explanation should be linked somehow.

You can get the tag description from lintian-explain-tags:

$ lintian-explain-tags -t groff-message
N:
W: groff-message
N:
N: A manual page provoked warnings or errors from the man program.
Here are some common ones:
N:
N: "cannot adjust" or "can't break" are issues with paragraph filling.
They are usually related to long lines. Justifying text on the left hand
side can help with adjustments. Hyphenation can help with breaks.
N:
N: For more information, please see "Manipulating Filling and
Adjusting" and "Manipulating Hyphenation" in the Groff manual (see info
groff).
N:
N: "can't find numbered character" usually means that the input was in
a national legacy encoding. The warning means that some characters were
dropped. Please use escapes such as \[:a] as described on the groff_char
manual page.
N:
N: Other common warnings are formatting typos. String arguments to .IP
require quotes. Usually, some text is lost or mangled. See the groff_man
(or groff_mdoc if using mdoc) manual page for details on macros.
N:
N: The check for manual pages uses the --warnings option to man to
catch common problems, like a . or a ' at the beginning of a line as
literal text. They are interpreted as Groff commands. Just reformat the
paragraph so the
N: characters are not at the beginning of a line. You can also add a
zero-width space (\&) in front of them.
N:
N: Aside from overrides, warnings can be disabled with the .warn
directive. Please see "Debugging" in the Groff manual.
N:
N: You can see the warnings yourself by running the command used by
Lintian:
N:
N: LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 \
N: man --warnings -E UTF-8 -l -Tutf8 -Z <file> >/dev/null
N:
N: Please refer to the groff_man(7) manual page and the groff_mdoc(7)
manual page for details.
N:
N: Visibility: warning
N: Show-Always: no
N: Check: documentation/manual
N: Renamed from: manpage-has-errors-from-man
N:

Kind Regards,

Bas

--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

[c.b...@posteo.jp]

Dear Sebastiaan,

thanks for reporting back.

Am 28.07.2023 10:00 schrieb Sebastiaan Couwenberg:
> You can get the tag description from lintian-explain-tags:

I know that. The bug report wasn't a support question but a feature
request.

The infos about the meaning of the tags need to be part of the linked
website or somehow should linked there.

[Debian Bug Tracking System]

Your message dated Sat, 18 Nov 2023 15:43:04 +0100
with message-id <ZVjNeAS6...@grub.nussbaum.fr>
and subject line Re: Bug#1042428: lintian.debian.org off ?
has caused the Debian Bug report #1042428,
regarding qa.debian.org: Missing description for lintian warning tags (https://udd.debian.org/lintian/?packages=)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


--
1042428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[Lucas Nussbaum]

On 19/11/23 at 23:49 -0700, Otto Kekäläinen wrote:
> > > This issue still exists. I would now have the need to send the url
> > > https://lintian.debian.org/tags/service-file-is-not-a-file to upstream
> > > developers to learn about this Lintian issue, but the URL does not
> > > serve any contents nor does it redirect to a new location.
> > >
> > > I am still willing to contribute the Apache/Nginx rewrite rules if
> > > somebody can point me to a code repository where I can read/contribute
> > > at like I announced on September 27th in this thread.
> >
> > I finally fixed this. Sorry for the delay.
> >
> > https://udd.debian.org/lintian?packages=entr has a link for each lintian
> > tag, that points to (e.g.) https://udd.debian.org/lintian-tag.cgi?tag=superfluous-file-pattern
> > That page includes a description of the tag as well as all packages
> > affected by the tag.
>
> Thanks!
>
> Could you consider setting up also redirects from old url, as it seems
> that search engines had it indexed pretty well and tend to offer links
> to lintian.debian.org as the primary result on on searches for various
> Lintian errors?
>
> https://lintian.debian.org/tags/([a-z-]*)/?$
> ->
> https://udd.debian.org/lintian-tag.cgi?tag=$1

That would be something for DSA to do.

@DSA: alternatively, maybe you could setup lintian.debian.org as served
by an apache on ullmann.debian.org, and managed by the uddadm group?
Then I could handle redirects myself.

Lucas