all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaz Kylheku <kaz@kylheku.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: "Paul A. Patience" <paul@apatience.com>, 49517@debbugs.gnu.org
Subject: [bug#49517] [PATCH] gnu: txr: Build documentation and update to 265.
Date: Sat, 17 Jul 2021 15:51:51 -0700	[thread overview]
Message-ID: <3ae1061ea0a61b579c48f9ea7b4f4832@mail.kylheku.com> (raw)
In-Reply-To: <87o8b1p8k1.fsf@kitej>

On 2021-07-17 02:57, Guillaume Le Vaillant wrote:
> Hi,
> 
> When testing the patch to build the HTML and PDF documentation,
> I noticed that the 'share/doc/txr-263/txr-manpage.pdf' file is not
> reproducible. There are some timestamps and UUIDs in it that change at
> each build (diffoscope output attached).
> 
> Could you take a look at that and see if there's a way to make it
> reproducible?
> Thanks.

Hi Guillaume,

Thank you for your report. I don't see anything in the pdfroff 
documentation
about getting rid of this. I might use a program similar to this one
to just overwrite the UUIDs and dates:

(let* ((pdf (file-get-string "txr-manpage.pdf"))
        (start (search-str pdf "<?xpacket begin="))
        (end (if start (search-str pdf "<?xpacket end" start)))
        (xml (if end [pdf start..end]))
        (orig-len (len xml)))
   (unless xml
     (format *stderr* "XML block not found in PDF")
     (exit nil))
   (upd xml
     (regsub #/uuid:........-....-....-....-............/
             "uuid:00000000-0000-0000-0000-000000000000")
     (regsub #/Date>....-..-..T..:..:..-..:../
             "Date>1970-01-01T00:00:00-00:00"))
   (assert (eql (len xml) orig-len))
   (set [pdf start..end] xml)
   (file-put-string "txr-manpage.pdf.temp" pdf)
   (rename-path "txr-manpage.pdf.temp" "txr-manpage.pdf"))


I have some questions.

1. When, for the sake of reproducible binary builds,
    we replace date stamps with fixed dates, is there a preference for
    what date to use? I used the Unix epoch, as you can see.

    I'm aware of the convention involving the environment
    variable SOURCE_DATE_EPOCH.

    Should I use that?

2. Is there some recommended practice with regard to some
    ./configure option or environment/make variable to react to
    for ensuring reproducible builds? So that is to say, suppose
    I don't wish to do the above embedded XML cleaning, except
    when building for a distro that strives for reproducibility.

    For opting in to reproducibilty, should I again rely on
    SOURCE_DATE_EPOCH and have the build react to it?


Thanks ...




  reply	other threads:[~2021-07-18  9:34 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 [this message]
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               ` bug#49517: " Guillaume Le Vaillant
2021-07-18 20:27             ` [bug#49517] " 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=3ae1061ea0a61b579c48f9ea7b4f4832@mail.kylheku.com \
    --to=kaz@kylheku.com \
    --cc=49517@debbugs.gnu.org \
    --cc=glv@posteo.net \
    --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.