Package: libcap-dev
Version: 1:2.66-5+b1
Severity: minor
Tags: patch

   * 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 "groff -e ' $' -e '\\~$' <file>" to find obvious 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>:4: style: .TH missing fourth argument; consider package/project 
name and version (e.g., "groff 1.23.0")
troff:<stdin>:31: warning: trailing space in the line
troff:<stdin>:59: warning: trailing space in the line
an.tmac:<stdin>:74: misuse, warning: .BR is for at least 2 arguments, got 1
        Use macro '.B' for one argument or split argument.


   * What outcome did you expect instead?

     No output (no warnings).

-.-

  General remarks and further material, if a diff-file exist, are in the
attachments.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.10-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libcap-dev depends on:
ii  libc6    2.40-6
ii  libcap2  1:2.66-5+b1

libcap-dev recommends no packages.

Versions of packages libcap-dev suggests:
ii  manpages-dev  6.9.1-1

-- no debconf information
Input file is cap_init.3

Output from "mandoc -T lint  cap_init.3": (shortened list)

      3 whitespace at end of input line

-.-.

Output from "test-groff -mandoc -t -ww -z cap_init.3": (shortened list)

      1         Use macro '.B' for one argument or split argument.
      1 .BR is for at least 2 arguments, got 1
      2 trailing space in the line

-.-.

Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

Number of lines affected is

3

-.-.

Use the correct macro for the font change of a single argument or
split the argument into two.

74:.BR EINVAL

-.-.

Trailing space in a macro call.

52:.IR cap_p , 

-.-.

Output from "test-groff  -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z 
":

an.tmac:<stdin>:4: style: .TH missing fourth argument; consider package/project 
name and version (e.g., "groff 1.23.0")
troff:<stdin>:31: warning: trailing space in the line
troff:<stdin>:59: warning: trailing space in the line
an.tmac:<stdin>:74: misuse, warning: .BR is for at least 2 arguments, got 1
        Use macro '.B' for one argument or split argument.
--- cap_init.3  2025-01-30 19:09:15.743818351 +0000
+++ cap_init.3.new      2025-01-30 19:13:51.036618632 +0000
@@ -28,7 +28,7 @@ the capability state.  The initial value
 caller should free any releasable memory, when the capability state in
 working storage is no longer required, by calling
 .BR cap_free ()
-with the 
+with the
 .I cap_t
 as an argument.
 .PP
@@ -49,14 +49,14 @@ function.
 .BR cap_dup ()
 returns a duplicate capability state in working storage given by the
 source object
-.IR cap_p , 
+.IR cap_p ,
 allocating any memory necessary, and returning a
 pointer to the newly created capability state.  Once duplicated, no
 operation on either capability state affects the other in any way.
 When the duplicated capability state in working storage is no longer required,
 the caller should free any releasable memory by calling
 .BR cap_free ()
-with the 
+with the
 .I cap_t
 as an argument.
 .SH "RETURN VALUE"
@@ -71,7 +71,7 @@ returns zero on success, and \-1 on fail
 On failure,
 .I errno
 is set to
-.BR EINVAL
+.B EINVAL
 or
 .BR ENOMEM .
 .SH "CONFORMING TO"
  Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)

[gn]roff -mandoc -t -ww -b -z -K utf8  <man page>

  The same goes for man pages that are used as an input.

  For a style guide use

  mandoc -T lint

-.-

  Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.

  It should also check its input files for too long (> 80) lines.

  This is just a simple quality control measure.

  The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.

  Common defects:

  Not removing trailing spaces (in in- and output).
  The reason for these trailing spaces should be found and eliminated.

  Not beginning each input sentence on a new line.
Line length should thus be reduced.

  The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.

  See man-pages(7), item "semantic newline".

-.-

The difference between the formatted output of the original and patched file
can be seen with:

  nroff -mandoc <file1> > <out1>
  nroff -mandoc <file2> > <out2>
  diff -u <out1> <out2>

and for groff, using

\"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - \"

instead of 'nroff -mandoc'

  Add the option '-t', if the file contains a table.

  Read the output from 'diff -u ...' with 'less -R' or similar.

-.-.

  If 'man' (man-db) is used to check the manual for warnings,
the following must be set:

  The option \"-warnings=w\"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT=\"-ww -b -z\"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-

Reply via email to