#1102281 Lintian::Deb822.3: Some remarks and a patch with editorial changes for this man page

Package:
lintian
Source:
lintian
Submitter:
Bjarni Ingi Gislason
Date:
2026-03-06 23:33:01 UTC
Severity:
normal
Tags:
#1102281#5
Date:
2025-04-07 08:15:37 UTC
From:
To:
   * What led up to the situation?

     Checking for defects with a new version

test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man page"

  [Use

grep -n -e ' $' -e '\\~$' -e ' \\f.$' -e ' \\"' <file>

  to find (most) trailing spaces.]

  ["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).

  [The fate of "test-nroff" was decided in groff bug #55941.]

   * What was the outcome of this action?

an.tmac:<stdin>:83: style: use of deprecated macro: .PD
an.tmac:<stdin>:90: style: use of deprecated macro: .PD
troff:<stdin>:110: warning: trailing space in the line
an.tmac:<stdin>:122: style: use of deprecated macro: .PD
an.tmac:<stdin>:125: style: use of deprecated macro: .PD
an.tmac:<stdin>:150: style: use of deprecated macro: .PD
an.tmac:<stdin>:155: style: use of deprecated macro: .PD


   * What outcome did you expect instead?

     No output (no warnings).

-.-

  General remarks and further material, if a diff-file exist, are in the
attachments.
#1102281#10
Date:
2025-04-08 18:30:40 UTC
From:
To:
Hello,

Thanks for opening these manpage bugs.

Lintian generates these manpages via perldoc. Could it be possible the
problem spawns from perldoc itself and not our manpages? These files
have not changed recently on our side.

Otherwise, would it be possible to propose patches (preferably on Salsa
:D) for the Perl files themselves? At the moment, the patches proposed
are not really useful, as they don't exist in the source code.

For example, for this bug, the file that's used to generate the man3
page is lib/Lintian/Deb822.pm

Cheers,
#1102281#17
Date:
2026-03-06 23:23:45 UTC
From:
To:
Hi,

  I do not know perldoc.

  For the input file, it can be made better by

1) removing trailing spaces

2) beginning each sentence on a new line

3) start each markup on a new line

  as long as the translator accepts that.

  The main culprit is the translator.

  So the natural way is to send the maintainers of it the input file and
the content of my e-mail, showing the defects of the translation.

  Another possibility is to try other implementations of the translator.