From: Guillaume Le Vaillant <glv@posteo.net>
To: "Paul A. Patience" <paul@apatience.com>
Cc: Kaz Kylheku <kaz@kylheku.com>, 49517-done@debbugs.gnu.org
Subject: bug#49517: [PATCH] gnu: txr: Build documentation and update to 265.
Date: Tue, 20 Jul 2021 09:07:20 +0000 [thread overview]
Message-ID: <87eebtbbg7.fsf@kitej> (raw)
In-Reply-To: <xQ_yTx179628lqq3-8xk3URI4VHQ7-DR2NR_maHbTOy4ej4MjGI6EiO0m7adJguFkPzYpNSVxIyyjzH3KQm-6DKWBFQXcnJ6iY2qOCkEBAE=@apatience.com>
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
Paul A. Patience <paul@apatience.com> skribis:
> I've updated the first patch to fix this by setting GS_GENERATE_UUIDS
> to 0, which seems to be the standard Guix way to patch groff's use of
> Ghostscript.
> It removes most of the date (i.e., the hours, minutes and seconds) and
> the UUID, but leaves the year, month and day:
>
> $ xxd /gnu/store/h94iilsa2xsp2ymn3k9x3ckmvfjha731-txr-266/share/doc/txr-266/txr-manpage.pdf | grep -C 1 Date
> 00231430: 702f 312e 302f 273e 3c78 6d70 3a4d 6f64 p/1.0/'><xmp:Mod
> 00231440: 6966 7944 6174 653e 3230 3231 2d30 372d ifyDate>2021-07-
> 00231450: 3138 3c2f 786d 703a 4d6f 6469 6679 4461 18</xmp:ModifyDa
> --
> 00231470: 6174 653e 3230 3231 2d30 372d 3138 3c2f ate>2021-07-18</
> 00231480: 786d 703a 4372 6561 7465 4461 7465 3e0a xmp:CreateDate>.
> 00231490: 3c78 6d70 3a43 7265 6174 6f72 546f 6f6c <xmp:CreatorTool
>
> Is this acceptable?
> Otherwise we may have to resort to a variation of the method Kaz
> mentioned, though it's probably better to fix the Ghostscript patches
> implementing GS_GENERATE_UUIDS, because otherwise any package relying on
> groff to make PDFs will suffer from this very problem.
Hi Paul,
I pushed your patches as 75922458af60081bf6964006d5b9c180ff9ec8ca and
following with some modifications. I added a phase replacing the
hardcoded "/bin/sh" by the real path to bash in "/gnu/store/...", which
makes all the tests pass.
For now the PDF documentation still has the "ModifyDate" and
"CreateDate" fields. The fix for this is in the core-updates branch, so
when core-updates gets merged into master, the PDF should become
reproducible.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-07-20 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 0:37 [bug#49517] [PATCH] gnu: txr: Build documentation and update to 265 Paul A. Patience
2021-07-12 1:01 ` Paul A. Patience
2021-07-13 23:45 ` Paul A. Patience
2021-07-17 9:57 ` Guillaume Le Vaillant
2021-07-17 22:51 ` Kaz Kylheku
2021-07-18 3:43 ` Kaz Kylheku
2021-07-18 10:36 ` Guillaume Le Vaillant
2021-07-18 12:59 ` Paul A. Patience
2021-07-20 9:07 ` Guillaume Le Vaillant [this message]
2021-07-18 20:27 ` Kaz Kylheku
2021-07-18 21:28 ` Paul A. Patience
2021-07-19 12:08 ` Guillaume Le Vaillant
2021-07-19 21:31 ` Kaz Kylheku
2021-07-20 9:18 ` Guillaume Le Vaillant
2021-07-19 3:23 ` Kaz Kylheku
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eebtbbg7.fsf@kitej \
--to=glv@posteo.net \
--cc=49517-done@debbugs.gnu.org \
--cc=kaz@kylheku.com \
--cc=paul@apatience.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.