On 2025-04-05, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:pygopherd package: > > #1036521: pygopherd: reproducible-builds: Garbled pygopherd.txt /bin/sh -> > dash ... > pygopherd (3.0.1-2) unstable; urgency=medium > . > * Build pygopherd.txt with bash. Closes: #1036521. ... > The first attached patch fixes this by adjusting the upstream Makefile > to explicitly call groff with bash. > > And... for good measure, a second patch switches to using utf8; this is > 2023 after all!
It looks like the issue was partially fixed, but there may be issues resulting from generating ascii text rather than UTF-8, at least, back when I filed the bug that seemed to be important enough to include as a patch, though that was long enough ago that it is not fresh in my mind... > From be277736b9fc85a7df1d76318e931ae289bc3034 Mon Sep 17 00:00:00 2001 > From: Vagrant Cascadian <vagr...@reproducible-builds.org> > Date: Sun, 21 May 2023 14:00:30 -0700 > Subject: [PATCH 2/2] Makefile: Generate pygopherd.txt with utf8. > > --- > Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Makefile b/Makefile > index e2416e2..256e3eb 100644 > --- a/Makefile > +++ b/Makefile > @@ -58,4 +58,4 @@ doc/pygopherd.pdf: doc/pygopherd.ps > mv pygopherd.pdf doc > > doc/pygopherd.txt: > - bash -c "groff -Tascii -man doc/pygopherd.8 | sed $$'s/.\b//g' > > doc/pygopherd.txt" > + bash -c "groff -Tutf8 -man doc/pygopherd.8 | sed $$'s/.\b//g' > > doc/pygopherd.txt" > -- > 2.39.2 Thanks! live well, vagrant
signature.asc
Description: PGP signature
