Re: groff 1.24.1 neqn test failure on nixpkgs Darwin

"G. Branden Robinson" <[email protected]> Sun, 15 Mar 2026 07:06:10 -0500

Newsgroups	gmane.comp.printing.groff.general
Message-ID	<20260315120610.pus2xw63ap74d4ka@illithid>

Hi Alexis,

At 2026-03-15T12:57:42+0100, Alexis (surryhill) wrote:
> I'm happy to report that yes, exporting GROFF_BIN_PATH=. into the
> nixpkgs test environment works for me and makes the neqn-smoke-test
> pass.

I'm delighted to hear it!  I'm usually nervous about recommending
remedies I haven't checked myself--it's a good way to get egg on one's
face, and mine already resembles an omelet with many ingredients.  ;-)

> If you think there is value in "enhancing" groff's test suite, I'm all
> for it, if not, your response has provided me with a very acceptable
> solution for the groff nixpkgs :)

I'd like to figure out a superior approach for the next "big" release
(planned for early July), but I don't think a spurious test failure in a
_relatively_ exotic environment like NixOS (or similar) by itself
warrants, say, a 1.24.2 release.

That said, containerized, FHS-disregarding, and other initiatives
related to build reproducibility are becoming less exotic by the day.

Regards,
Branden

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