Package: dpkg
Version: 1.19.0.5+b1
Severity: minor
Tags: patch

Dear Maintainer,

   * What led up to the situation?

  Warnings from "groff":

<dpkg-trigger.1>:44 (macro BR): only 1 argument, but more are expected
<dpkg-trigger.1>:62 (macro BR): only 1 argument, but more are expected
<dpkg-trigger.1>:68 (macro BR): only 1 argument, but more are expected
<dpkg-trigger.1>:75 (macro BR): only 1 argument, but more are expected
<dpkg-trigger.1>:79 (macro BR): only 1 argument, but more are expected

Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z 

  ["test-groff" is a developmental version of "groff"]

####

  Summary:

  Change ".BR <one argument>" to ".B <one argument>"

  Protect ellipis on both sides, "\&...\&"

  Know the difference between "abc..." and "abc ...".
  See a manual of style.

  Use macros instead of font escapes "\f..."

  Begin each sentence on a new line

###

  Details:

Test nr. 8:

Protect a full stop (.) with "\&", if it has a blank (white-space) in
front of or (ignoring characters transparent to it) after it, and it
does not mean an end of a sentence.

25:.RI [ option "...] " trigger-name
28:.RI [ option "...] " command

#####

NOT APPLIED

Test nr. 9:

Define a string "el" for an ellipsis, to avoid problems with the
full stops (can act as a control character or indicate the end of a
sentence).
Simplifies changes around this string (character)
.ds el \&.\^.\^.\&\"
  or
.ds el \&.\|.\|.\&\"

25:.RI [ option "...] " trigger-name
28:.RI [ option "...] " command

#####

Test nr. 10:

Separate an ellipsis from the preceding string with a space
character, if it does not mean a continuation of it.

See a manual of style about the difference between "abc..." and
"abc ...".

25:.RI [ option "...] " trigger-name
28:.RI [ option "...] " command

#####

Test nr. 16:

Use the correct macro for the font change of one argument.
Split a  punctuation mark from the only argument if one is there

44:.BR \-\-check\-supported
62:.BR \-\-by\-package=\fIpackage\fR
68:.BR \-\-no\-await
75:.BR \-\-await
79:.BR \-\-no\-act

#####

Test nr. 21:

Use a macro to change to the italic font, instead of \fI [1], if
possible.
The macros have the italic corrections, but "\c" removes them
  or
add the italic corrections.
[1] man-pages(7) [package "manpages"]

60:\fI/var/lib/dpkg\fP.

#####

Test nr. 41:

Wrong distance between sentences or protect the indicator.

1) Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) [package "manpages"] and "info groff".

Or

2) Adjust space between sentences (two spaces),

3) or protect the indicator by adding "\&" after it.

The "indicator" is an "end-of-sentence character" (.!?).

36:triggers control file directive, are insufficiently rich. It can also
46:postinst). Will exit \fB0\fP if a triggers-capable \fBdpkg\fP has run,
47:or \fB1\fP with an error message to stderr if not. Normally, however,
59:Change the location of the \fBdpkg\fR database. The default location is

#####

Test nr. 45:

Add a missing italic left correction in front of \fI, or use a macro.

62:.BR \-\-by\-package=\fIpackage\fR

#####

Input file is dpkg-trigger.1
Test nr. 46:

Add a missing italic right correction after \fI, or use a macro.

60:\fI/var/lib/dpkg\fP.

#####

  Patch:

--- dpkg-trigger.1      2018-05-06 07:53:26.000000000 +0000
+++ dpkg-trigger.1.new  2018-05-25 00:13:28.000000000 +0000
@@ -22,10 +22,10 @@ dpkg\-trigger \- a package trigger utili
 .
 .SH SYNOPSIS
 .B dpkg\-trigger
-.RI [ option "...] " trigger-name
+.RI [ option " \&...\&] " trigger-name
 .br
 .B dpkg\-trigger
-.RI [ option "...] " command
+.RI [ option " \&...\&] " command
 .
 .SH DESCRIPTION
 \fBdpkg\-trigger\fP is a tool to explicitly activate triggers and check
@@ -33,7 +33,8 @@ for its support on the running \fBdpkg\f
 .PP
 This can be used by maintainer scripts in complex and conditional
 situations where the file triggers, or the declarative \fBactivate\fP
-triggers control file directive, are insufficiently rich. It can also
+triggers control file directive, are insufficiently rich.
+It can also
 be used for testing and by system administrators (but note that the
 triggers won't actually be run by \fBdpkg\-trigger\fP).
 .PP
@@ -41,10 +42,12 @@ Unrecognized trigger name syntaxes are a
 .
 .SH COMMANDS
 .TP
-.BR \-\-check\-supported
+.B \-\-check\-supported
 Check if the running \fBdpkg\fP supports triggers (usually called from a
-postinst). Will exit \fB0\fP if a triggers-capable \fBdpkg\fP has run,
-or \fB1\fP with an error message to stderr if not. Normally, however,
+postinst).
+Will exit \fB0\fP if a triggers-capable \fBdpkg\fP has run,
+or \fB1\fP with an error message to stderr if not.
+Normally, however,
 it is better just to activate the desired trigger with \fBdpkg\-trigger\fP.
 .TP
 .BR \-? ", " \-\-help
@@ -56,27 +59,28 @@ Show the version and exit.
 .SH OPTIONS
 .TP
 .BI \-\-admindir= dir
-Change the location of the \fBdpkg\fR database. The default location is
-\fI/var/lib/dpkg\fP.
+Change the location of the \fBdpkg\fR database.
+The default location is
+.IR /var/lib/dpkg .
 .TP
-.BR \-\-by\-package=\fIpackage\fR
+.BI \-\-by\-package= package
 Override trigger awaiter (normally set by \fBdpkg\fP through the
 \fBDPKG_MAINTSCRIPT_PACKAGE\fP environment variable of the maintainer scripts,
 naming the package to which the script belongs, and this will be used
 by default).
 .TP
-.BR \-\-no\-await
+.B \-\-no\-await
 This option arranges that the calling package T (if any) need not await
 the processing of this trigger; the interested package(s) I, will not be
 added to T's trigger processing awaited list and T's status is unchanged.
 T may be considered installed even though I may not yet have processed
 the trigger.
 .TP
-.BR \-\-await
+.B \-\-await
 This option does the inverse of \fB\-\-no\-await\fP (since dpkg 1.17.21).
 It is currently the default behavior.
 .TP
-.BR \-\-no\-act
+.B \-\-no\-act
 Just test, do not actually change anything.
 .
 .SH EXIT STATUS


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

Kernel: Linux 4.9.88-1-u1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-8.1
ii  libc6        2.27-3
ii  liblzma5     5.2.2-1.3
ii  libselinux1  2.7-2+b2
ii  tar          1.30+dfsg-2
ii  zlib1g       1:1.2.11.dfsg-1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt            1.6.1
pn  debsig-verify  <none>

-- no debconf information

-- 
Bjarni I. Gislason

Reply via email to