--- Begin Message ---
Package: texlive-base
Version: 2026.20260328-4
Severity: minor
Tags: patch
16.05.2026 00:00:15 Bjarni Ingi Gislason <[email protected]>:
Package: texlive-base
Version: 2026.20260328-4
Severity: minor
Tags: patch
I am not subscribed.
Additional remarks.
Mails from me to "[email protected]" are no longer acknowledged. A
Debian maintainer told me, that he would contact the mail administrator
about me not wanting to send bugs upstream.
-.-
Dear Maintainer,
> From "/usr/share/doc/debian/bug-reporting.txt.gz":
Don't file bugs upstream
If you file a bug in Debian, don't send a copy to the upstream software
maintainers yourself, as it is possible that the bug exists only in
Debian. If necessary, the maintainer of the package will forward the
bug upstream.
-.-
For forwarding bug reports to upstream see:
https://www.debian.org/Bugs/Developer#forward
-.-
"Handling bug reports" in
http://people.debian.org/~enrico/dcg/ch03s02.html
-.-
I do not send reports upstream if I have to get an account there.
The Debian maintainers have one already.
If I get a negative (or no) response from upstream, I send henceforth
bugs to Debian.
-.-
* 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=0 -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?
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
Output from "test-nroff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
troff:<stdin>:262: warning [page 1, line 251]: cannot adjust line in b adjust
mode; overset by 6n [-w break]
* 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: forky/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 7.0.4+deb14-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 texlive-base depends on:
ii debconf [debconf-2.0] 1.5.92
ii libpaper-utils 2.2.5-0.3+b3
ii sensible-utils 0.0.26
ii tex-common 6.20
ii texlive-binaries 2026.20260303.78225+ds-3
ii ucf 3.0053
ii xdg-utils 1.2.1-2
Versions of packages texlive-base recommends:
ii lmodern 2.005-1
Versions of packages texlive-base suggests:
ii ghostscript [postscript-viewer] 10.07.0~dfsg-2
ii gv [postscript-viewer] 1:3.7.4-3.2
ii mupdf [pdf-viewer] 1.27.0+ds1-5
pn perl-tk <none>
ii xpdf [pdf-viewer] 3.04+git20260220-1
pn xzdec <none>
Versions of packages tex-common depends on:
ii bzip2 1.0.8-6+b2
ii ucf 3.0053
Versions of packages tex-common suggests:
pn debhelper <none>
Versions of packages texlive-base is related to:
ii tex-common 6.20
ii texlive-binaries 2026.20260303.78225+ds-3
-- debconf information excluded
--- fmtutil.1 2026-05-15 20:17:53.518621108 +0000
+++ fmtutil.1.new 2026-05-15 21:10:29.651762901 +0000
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.3.
-.TH FMTUTIL "1" "February 2026" "TeX Live" "User Commands"
+.TH FMTUTIL 1 "February 2026" "TeX Live" "User Commands"
.SH NAME
fmtutil \- manage TeX formats and Metafont bases, per-user
.br
@@ -8,13 +8,13 @@ fmtutil-sys \- manage TeX formats and Me
mktexfmt \- create a TeX format or Metafont base
.SH SYNOPSIS
.B fmtutil
-[\fI\,-user|-sys\/\fR] [\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
+[\fI\,\-user|\-sys\/\fR] [\fI\,OPTION\/\fR] ...\& [\fI\,COMMAND\/\fR]
.br
.B fmtutil-sys
-[\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
+[\fI\,OPTION\/\fR] ...\& [\fI\,COMMAND\/\fR]
.br
.B fmtutil-user
-[\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
+[\fI\,OPTION\/\fR] ...\& [\fI\,COMMAND\/\fR]
.br
.B mktexfmt
\fI\,FORMAT.fmt|BASE.base|FMTNAME\/\fR
@@ -114,10 +114,10 @@ create all missing format files
(re)create formats that depend on HYPHENFILE
.TP
\fB\-\-enablefmt\fR
-FORMAT[/ENGINE] enable FORMAT, as built with ENGINE
+FORMAT[/ENGINE] enable FORMAT, as built with ENGINE
.TP
\fB\-\-disablefmt\fR FORMAT[/ENGINE]
-disable FORMAT, as built with ENGINE
+disable FORMAT, as built with ENGINE.
If multiple formats have the same name and
.IP
different engines, \fI\,/ENGINE\/\fP specifier is required.
@@ -135,7 +135,6 @@ show version information and exit
\fB\-\-help\fR
show this message and exit
.SH ENVIRONMENT
-.PP
Explanation of trees and files normally used:
.IP
If \fB\-\-cnffile\fR is specified on the command line (possibly multiple
@@ -235,7 +234,7 @@ the file \fI\,$TEXMFCONFIG/web2c/fmtutil
\fB\-\-no\-error\-if\-no\-engine\fR option exists, since luajittex cannot be
compiled on all platforms. So this is not needed.)
.PP
-fmtutil\-user (fmtutil \fB\-user\fR) vs. fmtutil\-sys (fmtutil \fB\-sys\fR):
+fmtutil\-user (fmtutil \fB\-user\fR) vs.\& fmtutil\-sys (fmtutil \fB\-sys\fR):
.IP
When fmtutil\-sys is run or the command line option \fB\-sys\fR is used,
TEXMFSYSCONFIG and TEXMFSYSVAR are used instead of TEXMFCONFIG and
Input file is fmtutil.1
Output from "mandoc -T lint fmtutil.1": (shortened list)
3 STYLE: input text line longer than 80 bytes
2 STYLE: input text line longer than 80 bytes:
1 WARNING: skipping paragraph macro
-.-.
Show if help2man generated this.
A patch to a generated man page is to show where the generator
failed to make a "clean" man page rendering (that is without warnings) and
sometimes to show a better format for it.
1:.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.3.
Latest version in Debian testing: GNU help2man 1.49.3
-.-.
Reduce space between words.
fmtutil.1:117:FORMAT[/ENGINE] enable FORMAT, as built with ENGINE
-.-.
Change a HYPHEN-MINUS (code 0x2D) to a minus(-dash) (\-),
if it
is in front of a name for an option,
is a symbol for standard input,
is a single character used to indicate an option,
or is in the NAME section (man-pages(7)).
N.B. - (0x2D), processed as a UTF-8 file, is changed to a hyphen
(0x2010, groff \[u2010] or \[hy]) in the output.
11:[\fI\,-user|-sys\/\fR] [\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
-.-.
Wrong distance (not two spaces, not a new line character (\n)) between
sentences in the input file.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
Mark a final abbreviation point as such by suffixing it with "\&".
Some sentences (etc.) do not begin on a new line.
Split (sometimes) lines after a punctuation mark; before a conjunction.
Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.
Use
#!/usr/bin/sh
sed -e '/^\./n' \
-e 's/\([[:alpha:]]\)\. */\1.\n/g' $1
to split lines after a sentence period.
Check result with the difference between the formatted outputs.
See also the attachment "general.bugs"
25:"formats" here. (MetaPost no longer uses the past\-equivalent "mems".)
223:#! <fmtname> <enginename> <hyphen> <args>
225:The #! must be at the beginning of the line, with at least one space
232:#! luajitlatex luajittex language.dat,language.dat.lua lualatex.ini
236:compiled on all platforms. So this is not needed.)
242:TEXMFVAR, respectively. This is the primary difference between
-.-.
Split lines longer than 80 characters (fill completely
an A4 sized page line on a terminal)
into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
[List of affected lines removed.]
Longest line is number 262 with 103 characters
Executable location:
../../../../texk/texlive/../../../../Master/texmf\-dist/scripts/texlive/fmtutil.pl
-.-.
Remove quotes when there is a printable
but no space character between them
and the quotes are not for emphasis (markup),
for example as an argument to a macro.
fmtutil.1:2:.TH FMTUTIL "1" "February 2026" "TeX Live" "User Commands"
-.-.
Add "\&" after an ellipsis, when it does not end a sentence.
11:[\fI\,-user|-sys\/\fR] [\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
14:[\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
17:[\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
-.-.
Output from "test-nroff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
troff:<stdin>:262: warning [page 1, line 251]: cannot adjust line in b adjust
mode; overset by 6n [-w break]
-.-
Spelling (codespell):
formts ==> formats, forms
that is
formts ==> formats
-.-
Abbreviation:
vs. ==> vs.\&
-.-
Add an end of sentence to
disable FORMAT, as built with ENGINE
-.-
Generally:
Split (sometimes) lines after a punctuation mark; before a conjunction.
Use a two-fonts macro ".IR "instead of using "\fI...\fR
Use a two-fonts macro ".XY" instead of using "\fX...\fY, where X and Y are
one of B, I, or R.
-.-
Tables:
Use the preprocessor 'tbl' to make tables.
Put data, that are wider than the header in the (centered) last column,
in a "T{...\nT}" block(, when the table gets wider than the output line).
Table headers, that are wider than any data in the corresponding column,
do not need to be centered, so left adjustment (l, L) is sufficient.
--- fmtutil.1 2026-05-15 20:17:53.518621108 +0000
+++ fmtutil.1.new 2026-05-15 21:10:29.651762901 +0000
@@ -1,5 +1,5 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.3.
-.TH FMTUTIL "1" "February 2026" "TeX Live" "User Commands"
+.TH FMTUTIL 1 "February 2026" "TeX Live" "User Commands"
.SH NAME
fmtutil \- manage TeX formats and Metafont bases, per-user
.br
@@ -8,13 +8,13 @@ fmtutil-sys \- manage TeX formats and Me
mktexfmt \- create a TeX format or Metafont base
.SH SYNOPSIS
.B fmtutil
-[\fI\,-user|-sys\/\fR] [\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
+[\fI\,\-user|\-sys\/\fR] [\fI\,OPTION\/\fR] ...\& [\fI\,COMMAND\/\fR]
.br
.B fmtutil-sys
-[\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
+[\fI\,OPTION\/\fR] ...\& [\fI\,COMMAND\/\fR]
.br
.B fmtutil-user
-[\fI\,OPTION\/\fR] ... [\fI\,COMMAND\/\fR]
+[\fI\,OPTION\/\fR] ...\& [\fI\,COMMAND\/\fR]
.br
.B mktexfmt
\fI\,FORMAT.fmt|BASE.base|FMTNAME\/\fR
@@ -114,10 +114,10 @@ create all missing format files
(re)create formats that depend on HYPHENFILE
.TP
\fB\-\-enablefmt\fR
-FORMAT[/ENGINE] enable FORMAT, as built with ENGINE
+FORMAT[/ENGINE] enable FORMAT, as built with ENGINE
.TP
\fB\-\-disablefmt\fR FORMAT[/ENGINE]
-disable FORMAT, as built with ENGINE
+disable FORMAT, as built with ENGINE.
If multiple formats have the same name and
.IP
different engines, \fI\,/ENGINE\/\fP specifier is required.
@@ -135,7 +135,6 @@ show version information and exit
\fB\-\-help\fR
show this message and exit
.SH ENVIRONMENT
-.PP
Explanation of trees and files normally used:
.IP
If \fB\-\-cnffile\fR is specified on the command line (possibly multiple
@@ -235,7 +234,7 @@ the file \fI\,$TEXMFCONFIG/web2c/fmtutil
\fB\-\-no\-error\-if\-no\-engine\fR option exists, since luajittex cannot be
compiled on all platforms. So this is not needed.)
.PP
-fmtutil\-user (fmtutil \fB\-user\fR) vs. fmtutil\-sys (fmtutil \fB\-sys\fR):
+fmtutil\-user (fmtutil \fB\-user\fR) vs.\& fmtutil\-sys (fmtutil \fB\-sys\fR):
.IP
When fmtutil\-sys is run or the command line option \fB\-sys\fR is used,
TEXMFSYSCONFIG and TEXMFSYSVAR are used instead of TEXMFCONFIG and
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>
To find most trailing space use
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
The same goes for man pages that are used as an input.
-.-
For a style guide use
mandoc -T lint
-.-
For general input conventions consult the man page "nroff(7)" (item
"Input conventions") or the Texinfo manual about the same item.
-.-
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.
"git" has a "tool" to point out whitespace,
see for example "git-apply(1)" and git-config(1)")
-.-
Not beginning each input sentence on a new line.
Line length and patch size should thus be reduced when that has been fixed.
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 -d -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 -d -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)
-.-
--- End Message ---
pgpMmojqdPCw3.pgp
