gnulib update and groff release plans (was: isfinite-no-c++: Make more C++ safe)

"G. Branden Robinson" <[email protected]> Thu, 19 Feb 2026 19:36:32 -0600

Newsgroups	gmane.comp.lib.gnulib.bugs,gmane.comp.printing.groff.general
Message-ID	<20260220013632.oju5iil4fqf7l2uh@illithid>

Hi Bruno,

At 2026-02-03T18:11:41+0100, Bruno Haible wrote:
> G. Branden Robinson wrote:
> > > This patch now fixes it, by ensuring REPLACE_ISFINITE = 0 instead
> > > of = 1.
> > 
> > Thanks for the heads-up.  Are you planning to cherry-pick this fix
> > over to the stable-202601 branch?
> 
> Yes.
> 
> The next update of the stable branches is due on 2026-02-15. Does this
> fit with your planned groff release schedule?

I haven't noticed an update of the stable-202601 branch this calendar
month.  Maybe I'm using a stale mirror?[0]

In any case, groff's Savannah ticket for "1.24.0 release goals and
gates" has all green dependencies now.[1]

(Or did last I checked...just this second I'm getting HTTP 502 errors
from savannah.{non,}gnu.org.  :-/ )

My plan is to refresh gnulib from the stable branch to pick up this fix
for building a C++ project on FreeBSD 14, tag groff 1.24.0.rc4, see what
eventuates, and if it's as little feedback as I got on rc3,[2] tag that
1.24.0 and call it a release.

Thanks for all your help getting groff release-worthy!

Regards,
Branden

[0] https://savannah.nongnu.org/support/?111374

[1] I punted on one item that I filed myself in August 2024.

    https://lists.gnu.org/archive/html/bug-groff/2026-02/msg00142.html
    https://lists.gnu.org/archive/html/bug-groff/2024-08/msg00248.html
    https://savannah.gnu.org/bugs/?66126

[2] https://lists.gnu.org/archive/html/groff/2026-02/msg00044.html

signature.asc (application/pgp-signature, 833 B)