On Fri, Dec 30, 2022 at 01:52:28PM +0100, Hilmar Preuße wrote:
> Am 30.12.2022 um 12:50 teilte Patrice Dumas mit:
>
> Hi,
>
> > I tried to reproduce the issue from the sources, both in the release and
> > the dev branch and I can't. My guess is that it is indeed an issue with
> > help2man as the headers shows:
> >
> > .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.3.
> >
> > I use a debian testing.
> >
> > This issue seems to be in the sources tarball. My wild guess is that
> > Gavin uses an older help2man with that issue.
> >
> He does. Here the header of the manual page in the tar ball:
>
> .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.13.
> .TH TEXI2DVI "1" "November 2022" "texi2dvi 7.0.1)" "User Commands"
>
I hadn't installed this version on purpose. I have downloaded and installed
the newest version (1.49.3) and now texi2dvi.1 is generated starting
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.3.
.TH TEXI2DVI "1" "December 2022" "texi2dvi (GNU Texinfo 7.0dev)" "User Commands"
.SH NAME
texi2dvi \- convert Texinfo documents to DVI or PDF
.SH SYNOPSIS
and "lexgrog texi2dvi.1" outputs
texi2dvi.1: "texi2dvi - convert Texinfo documents to DVI or PDF"
The help2man ChangeLog has some entries that may be relevant:
help2man (1.47.14) unstable; urgency=medium
* Revert --version parsing change from 1.47.13, which had unintended
consequences for some version strings. In short, it is not possible
to unambiguously determine the split between the package/program name
and version in some of the supported formats. Multi-word package
names are supported only in the "program (GNU package) version"
variant (closes: #958345).
-- Brendan O'Dea <b...@debian.org> Fri, 24 Apr 2020 23:58:17 +1000
I've added a note to README-hacking to pay attention to the help2man
version when making a release.
