groff 1.25 status (was: groff 1.25.0.rc1 on Ubuntu 26.04)
"G. Branden Robinson" <[email protected]> Thu, 23 Jul 2026 20:39:04 -0500
| Newsgroups | gmane.comp.printing.groff.general |
|---|---|
| Message-ID | <20260724013904.r2b37obifqvlyomr@illithid> |
--brij7l2tdwzpaq4h
Content-Type: text/plain; protected-headers=v1; charset=us-ascii
Content-Disposition: inline
Subject: groff 1.25 status (was: groff 1.25.0.rc1 on Ubuntu 26.04)
MIME-Version: 1.0
[adding Deri since I have a question for him below]
At 2026-07-23T17:07:22-0500, G. Branden Robinson wrote:
> An rc2 is now looking more likely to me than not for 1-2 C++ code
> reasons upon which I'll elaborate soon.
I'm pleased to retract this ominously allusive statement.
Neither of those problems appears to be of release-critical impact.
https://savannah.gnu.org/bugs/?68544
https://savannah.gnu.org/bugs/?68552
My pessimism is bruised this day.
It might still be worth rolling an RC2 this weekend, especially since
Bruno prefers to use a distribution archive and has such a nice panoply
of build environments.
And there is still the Manjaro URW fonts test failure.
Deri,
I notice from Bruno's report on that[1] that the "URW" fonts come from a
directory with "ghostscript" in its name. Is it possible some kind of
old, stupefied, or quasi-broken fonts are present there, and we failed
to detect their unuseful state for gropdf's full service level?
Is there some way can test for such stupefaction without increasing our
build-dependency burden?
I do not have a Manjaro Linux environment readily available to explore;
maybe you don't either. Can you suggest a test procedure to Bruno that
might help us to improve our URW font detection macro?[2]
Regards,
Branden
[1] https://lists.gnu.org/archive/html/groff/2026-07/msg00029.html
https://lists.gnu.org/archive/html/groff/2026-07/msg00034.html
https://lists.gnu.org/archive/html/groff/2026-07/msg00036.html
[2] https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/m4/groff.m4?h=1.24.1#n323
(Sorry for the old tag; cgit.git.savannah.gnu.org is, for me, served
by a stale mirror that is ~20 days out of date, and so it knows
nothing of the '1.25.0.rc1' tag.)
--brij7l2tdwzpaq4h
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAmpiwjEACgkQ0Z6cfXEm
bc5w2w//aD3jO6hMoVp30U9+Bhf2QahSum5sK0F6NyyGmNaOPeaveGP3u04Fn4QX
biWujxYKdsUJwLsTxqt0xoD/VJEIrYrO+JqZ5+Xgl9DtMuvGvMgCUcY/g7/5poky
W9tDSxH7HNR/RKGqODAT6zEl0rr/1WKV+EvTSK6hzmV9pGmwsF0JOjt2d7zEJkg8
3PaSuwCTA6bkDkEOfEaIBCN6uZnW5UGkA7xnld/RgZXBTDA2MTcyP8w3zp4kF/kG
egpcPHqOGq+g2dFfzrLKuD3JXNWPf3UEEoTTg2D+XrSLtGn6KrxL07RVQ2mSIb8O
qb34jeaklqC5UybGLjKOzH0Lrz9t0tgehDiy5zeClTOPfac/uKtgUkIE/KQp4X7m
VZ12XcoksNn9ykpYXXSjNWrTcspvNxowMyWMSIbEHMZ9PrCpyrplzz6jU9Ia8F6z
xHdEnQvKDXM/j8cmmwkuNlQznBPdxOLKiRu4cCie72F24WGARfBQ01H9mDCo2tOa
WtlN6vNrEYuwq4MtZl06YA3YhwdzNmWD2Gmwvk8f2FYqiimBrmndrnqSdTthjUd+
SQBvmuOgmgdk/IITPZXxzcVX6FsF9Mb08wvKxWNeKouPb7IWev4esN+sOgp98+Ke
K5+uhxSPwx1oE05/0+hrDNyFzmOusGnV3eGfnz8v5r86y/p7CEU=
=a49j
-----END PGP SIGNATURE-----
--brij7l2tdwzpaq4h--