Re: groff 1.25.0.rc1 on Ubuntu 26.04

"G. Branden Robinson" <[email protected]> Sun, 26 Jul 2026 00:18:18 -0500
Newsgroups gmane.comp.printing.groff.general
Message-ID <20260726051818.5v77u4y2oq72r72g@illithid>
--prrtdixa4t5vy5z7
Content-Type: text/plain; protected-headers=v1; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Re: groff 1.25.0.rc1 on Ubuntu 26.04
MIME-Version: 1.0

Hi Bruno,

At 2026-07-24T00:38:10+0200, Bruno Haible wrote:
> G. Branden Robinson wrote:
> > Here's the "real failure", I believe.
> >=20
> > > ../../../../../doc/groff.dvi.t2d/doc!groff.t2d/dvi/src/groff.texi:131=
56:
> > > epsf.tex not found, images will be ignored.
>=20
> Yes, that's my understanding as well.
>=20
> > > My recommendation regarding epsf.tex is to take it from Gnulib, as
> > > described in
> > > https://lists.gnu.org/archive/html/bug-bison/2025-07/msg00004.html
> > > .

Filed as <https://savannah.gnu.org/bugs/?68566>.

> > Not saying that this isn't good advice, but the root cause of this
> > problem, I believe, was my failure to properly manage "maintainer mode".
> > ...
> > Building from the distribution archive should _not_ prompt a rebuild of
> > any of the rendered forms of groff's Texinfo manual.
>=20
> While this is a good guideline, in order to reduce the necessary build
> steps for people who build from a tarball, you can't really rely on
> the time stamps to be correct, in my experience. 20 years ago this was
> true because of HP-UX 'make'; nowadays it is true because of Haiku
> (which does not implement time stamps as required by POSIX). Also, the
> way I do multi-platform testing of tarballs sometimes, is to unpack
> the tarball, commit the unpacked files into git, and have the CI check
> them out from git; and this process kills the time stamps.

If I understand Make correctly, unreliable time stamps are not a threat
the way I've (post-rc2) applied "maintainer mode" to this scenario.

diff --git a/doc/doc.am b/doc/doc.am
index edf136697..774e9ab45 100644
--- a/doc/doc.am
+++ b/doc/doc.am
@@ -875,8 +875,7 @@ EXTRA_DIST +=3D \
   $(DOC_LINE_LAYOUT_EPS) \
   $(DOC_LINE_LAYOUT_PNG)
=20
-# maintainer mode targets
-
+if MAINTAINER_MODE
 $(DOC_GNU_EPS): doc/gnu.xpm
        $(AM_V_GEN)$(MKDIR_P) `dirname $@` \
        && if test "$(XPMTOPPM)" !=3D found; then \
@@ -926,6 +925,19 @@ $(DOC_LINE_LAYOUT_EPS): doc/line-layout.roff pic groff=
=20
troff grops \
 $(DOC_LINE_LAYOUT_PNG): $(DOC_LINE_LAYOUT_EPS)
        $(AM_V_GEN)$(MKDIR_P) `dirname $@` \
        && convert -density 300 $< PNG24:$@
+else
+$(DOC_GNU_EPS) \
+  $(DOC_GNU_PNG) \
+  $(DOC_LINE_LAYOUT_EPS) \
+  $(DOC_LINE_LAYOUT_PNG):
+       @:
+endif # MAINTAINER_MODE
+
+MAINTAINERCLEANFILES +=3D \
+  $(DOC_GNU_EPS) \
+  $(DOC_GNU_PNG) \
+  $(DOC_LINE_LAYOUT_EPS) \
+  $(DOC_LINE_LAYOUT_PNG)
=20
 # Local Variables:
 # fill-column: 72

If the files are out of date, a non-maintainer-mode build--as from a
distribution archive--will now simply leave the files alone.

https://lists.gnu.org/archive/html/groff-commit/2026-07/msg00154.html

Regards,
Branden

--prrtdixa4t5vy5z7
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAmplmJMACgkQ0Z6cfXEm
bc53tA//RkBi/mboeUPSoemK9EnG+FVzm4x5DCODuaAgBNyBdMEibZgGZJ1TCsg4
rHrhmc7JTEF7fibXTFXyiMdGZb23JhVKsGkPTbmKLZcDbgYnQ48/DWHU6BqKmdfv
qX2ipGLptHEkTnZAmMt+lgj6aff46waC1+jjaFcEZ2HuhKKGf+FiVHW44/ViCTSV
4HqT0YnzNMgRmfeuw+P/51oSKBcrtmM6K3yO+GlguctV1itUfkJLnUg7/VbzY+87
5+n0VsdiRSr47ZHTs0py7ZwDrBLvrKcgoPZVOTt6hHJx+0Rfc19NytLLxnZYgpJT
jSuVBvUS2RFNSPVbZwhAjo6BQZmrVIRPrqYSDOlGolgSXTLXvEBnYTfWhzhkY5Mz
V0ctU2cjs2JuhuObuh+2vJ9ay7uZ5MGwRuM/ESlxFZKv5Bmw5Ruysw0lj/8FvXZs
qDnwJrtaHtWVZVIfDBpNRw4LtZzz5+fcGOZzjL7rs2QOXNhdmd1uEXHXbz677IB7
hjThatP1gXe2AeK/iSC3/TW4zj86aKBp3FVAykKcw9L4EF7AM3no2dIG4Lv/4dNF
5JkMlhTTU3kB7Nxy6FARteLLe/XBlBf45MnOvOYjCZGT8WiGA6eCLYwplSwbnv1r
AqiKbOLsFoIQ+0uUEVXWzf1rtc6yPrpsL6zNakefDeliNvXxdbg=
=LZkq
-----END PGP SIGNATURE-----

--prrtdixa4t5vy5z7--