From: "Ludovic Courtès" <ludo@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 49640@debbugs.gnu.org
Subject: [bug#49640] [PATCH core-updates] gnu: ghostscript: Improve reproducibility of PDF document generation
Date: Mon, 19 Jul 2021 16:35:18 +0200 [thread overview]
Message-ID: <87k0lmnzh5.fsf@gnu.org> (raw)
In-Reply-To: <87eebucyt8.fsf@kitej> (Guillaume Le Vaillant's message of "Mon, 19 Jul 2021 11:45:07 +0000")
Hi Guillaume,
Guillaume Le Vaillant <glv@posteo.net> skribis:
> When trying to solve a reproducibility issue when generating the
> PDF documentation of the txr software (see [1]), Paul Patience noticed
> that ghostscript writes a creation date in the PDF even when the
> GS_GENERATE_UUIDS environment variable is set to "0".
>
> The attached patch updates 'ghostscript-no-header-creationdate.patch' to
> fix this issue.
>
> Given the amount of rebuilds caused by modifying ghostscript, this
> should go to core-updates, but is core-updates in freeze state already,
> or can I push this patch right now?
[...]
> From db5962c68099f835350c24c8a3f889b9fa1f8a8e Mon Sep 17 00:00:00 2001
> From: Guillaume Le Vaillant <glv@posteo.net>
> Date: Mon, 19 Jul 2021 11:48:12 +0200
> Subject: [PATCH] gnu: ghostscript: Improve reproducibility of PDF document
> generation
>
> * gnu/packages/patches/ghostscript-no-header-creationdate.patch: Disable
> writing "xmp:ModifyDate" and "xmp:CreateDate" if GS_GENERATE_UUIDS is set to
> "0" or "no".
LGTM, you can push to ‘core-updates’. Was this submitted upstream?
Note: when ‘core-updates’ is frozen, we’ll fork ‘core-updates-frozen’ so
that people can happily keeping messing up on ‘core-updates’. This was
suggested some months ago during the Guix Days and I think it can make
things smoother!
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-07-19 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 11:45 [bug#49640] [PATCH core-updates] gnu: ghostscript: Improve reproducibility of PDF document generation Guillaume Le Vaillant
2021-07-19 14:35 ` Ludovic Courtès [this message]
2021-07-19 15:23 ` bug#49640: " Guillaume Le Vaillant
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0lmnzh5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=49640@debbugs.gnu.org \
--cc=glv@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).