* 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 ' $' <file>" to find 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>:1: style: .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0")
an.tmac:<stdin>:1: style: .TH missing fifth argument and second argument '1' not a recognized manual section; specify its title
troff:<stdin>:11: warning: trailing space in the line
troff:<stdin>:13: warning: trailing space in the line
troff:<stdin>:27: warning: trailing space in the line
troff:<stdin>:30: warning: trailing space in the line
troff:<stdin>:32: warning: trailing space in the line
troff:<stdin>:33: warning: trailing space in the line
troff:<stdin>:41: warning: trailing space in the line
troff:<stdin>:49: warning: trailing space in the line

   * What outcome did you expect instead?

     No output (no warnings).

-.-

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

On 31.12.24 Bjarni Ingi Gislason (bjarniig@simnet.is) wrote:

Hello,
The patch does not apply to the current upstream at [1].

Please be so kind to create a new patch or (even better) do a pull
request. If you are not familiar with github, send me the patch and
I'll do the PR.

https://raw.githubusercontent.com/pdfjam/pdfjam/refs/heads/master/pdfjam.1

Thiw would be more helpful than (temporarily) patching an outdated
version.

Happa new year,
  Hilmar

[1] https://github.com/pdfjam/pdfjam

Hi

  I do not send e-mails to upstream if I have to acquire an account.

  New patch in an attachment.

Then your patches will just end up in the bit nirvana.

It is not the job of the Debian TeX team to track down up-up-stream and
forward patches. Hilmar has already forwarded the patches to our
upstream, which is TeX Live. And they take what their upstream authors
provide.

It is your decision.

Norbert

As an upstream maintainer, I’ve now had several of these bug reports, and
I’m a bit ambivalent about them.

On the one hand, they seem to be accurate and well-intentioned.

On the other, they are close to trivial, yet involve diffs that require
careful reading if one is worried about what the changes may introduce.

Also, I have had several reports that don’t apply to my project, because the
faulty markup was generated by help2man.

Since a PR was opened on GitHub for this issue, I have applied it upstream,
but I’m not sure it’s really a good use of maintainer time in general, when
the issues seem mostly to be trivial. I would be happier if this sort of
issue were brought to my attention by a linting pass when building the man
pages, e.g. if it were a standard part of the GNU build system.

On 01.01.25 22:42, Bjarni Ingi Gislason wrote:

Hello Bjarni,
I don't like too, to have thousand accounts for every kind of
bugtracker, but I wouldn't think so much about an account on github.
Anyway: your decision.
The patch has been accepted, I tag your bug as fixed in upstream.

H.

Hi Norbert,
They do not, but the processing can be delayed heavily (years if one is
unlucky). So directly speaking to the upstream author raises drastically
the chance that you have a fix soon.

Let me know if this was the wrong way to address the issue. I'm willing
to speak to upstream authors, but this may take time...

Hilmar

On 02.01.25 23:38, Reuben Thomas wrote:

Hello,
In this case I did not find a mark in the manual page "generated by
xyz", hence I could forward the patch.
 >

The lintian quality checker has already some kind of checking for manual
pages, but this could (probably) be extended. I'll keep this in mind,
but the lintian people have a heavy workload too, so don't expect
automated checks soon.

Hilmar

Hi Hilmar,

Yes, that is what I meant. The patches of course remain somewhere in the
BTS forever.

All fine from your side. For the patches that concern TeX Live internal
man pages, Karl will apply them. For those coming from third-party
sources, one needs to talk to up-upstream.

Best regards, and Happy New Year!

Norbert

On 31.12.24 Bjarni Ingi Gislason (bjarniig@simnet.is) wrote:

Hello,

The patch was applied upstream [1]. Tagging.

Hilmar

[1] https://github.com/pdfjam/pdfjam/commit/d9f4395ae2146870c54a74ae91261852e5b5c101

We believe that the bug you reported is fixed in the latest version of
texlive-extra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1091785@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilmar Preuße <hille42@debian.org> (supplier of updated texlive-extra package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 28 May 2026 21:43:45 +0200
Source: texlive-extra
Architecture: source
Version: 2026.20260527-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Task Force <debian-tex-maint@lists.debian.org>
Changed-By: Hilmar Preuße <hille42@debian.org>
Closes: 974724 1091785 1124347
Changes:
 texlive-extra (2026.20260527-1) unstable; urgency=medium
 .
   * New upstream snapshot.
     * Overhauled documentation / manual page for pdfjam (Closes: #974724),
       (Closes: #1091785).
     * Improvements for show-pdf-tags.1 applied (Closes: #1124347).
   * Add patch for arara.1
Checksums-Sha1:
 cb94be99c34321c8ab9fc4e88d945f2014b1973c 3435 texlive-extra_2026.20260527-1.dsc
 a2740efc0dc636328436ffafe90d1d9192f3ae99 19032 texlive-extra_2026.20260527.orig-tex4ht.tar.xz
 b2e5e4f991e4432f8837fb98831dbd5ec8fea664 3208067332 texlive-extra_2026.20260527.orig.tar.xz
 5e878a6acc94172da546abc90db8c5573bb72268 212124 texlive-extra_2026.20260527-1.debian.tar.xz
 9ec3b072ab753dbe73b3e4b158f74cbf77a74861 4972 texlive-extra_2026.20260527-1_source.buildinfo
Checksums-Sha256:
 f509d8c470807c954c28c0c1e4b64d3b40c0105b9512e2aa446d13513bce30ef 3435 texlive-extra_2026.20260527-1.dsc
 2a6f7dc265cd85af11d95403666b07a6d78f113c2365ac873d6f8d83d921f531 19032 texlive-extra_2026.20260527.orig-tex4ht.tar.xz
 7d9c1349eafdad690dab5f41d13e182784150f6f7eddc76e70de4eece47fb345 3208067332 texlive-extra_2026.20260527.orig.tar.xz
 bf8e8631a8159a9d16891a0edfacb083af090fd764e361959babfa6a0c9bbe96 212124 texlive-extra_2026.20260527-1.debian.tar.xz
 f7b85be7e19d822fb1ce0174887be077853942dad235cad84f42be106102890f 4972 texlive-extra_2026.20260527-1_source.buildinfo
Files:
 0338ba94575d46980c3cd8a3c4b63f3c 3435 tex optional texlive-extra_2026.20260527-1.dsc
 1d93a016a36fb2a424b9de72a8109e0b 19032 tex optional texlive-extra_2026.20260527.orig-tex4ht.tar.xz
 87650a28ad31f2fae7f756369b7f5bad 3208067332 tex optional texlive-extra_2026.20260527.orig.tar.xz
 9887c6c93604bd495129884a4c8e42c8 212124 tex optional texlive-extra_2026.20260527-1.debian.tar.xz
 64c056375a50713272a39650dcbd413c 4972 tex optional texlive-extra_2026.20260527-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iNUEARYKAH0WIQRKnq6Z0VRDf4bMmAn98EQ6ARgcNAUCahit3F8UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0NEE5
RUFFOTlEMTU0NDM3Rjg2Q0M5ODA5RkRGMDQ0M0EwMTE4MUMzNAAKCRD98EQ6ARgc
NDB1APsGp1xi68Cs3I9dB4ReTp2yca/D/iYaI1n2fteb/rhWGQD/bNdWtOI3sRZ1
LovrmGNvkX4xy7OS+/tXaQWTZLkrEg8=
=3hmW
-----END PGP SIGNATURE-----