unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 73613@debbugs.gnu.org
Subject: bug#73613: texlive-luatex is not reproducible
Date: Sun, 20 Oct 2024 10:40:45 +0200	[thread overview]
Message-ID: <87r08b6ub6.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87wmipfkfu.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 03 Oct 2024 21:19:17 +0900")

Hello,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> This was discovered building texlive-luatex twice (--rounds=2 -K);
> diffoscope shows that:
>

[...]

> These are apparently time stamps as well as UUIDs.  Debian [0, 1] and
> NixOS [1] have patched some of them using faketime and substitute [0].
>
> We should follow suite.
>
> [0]  https://salsa.debian.org/live-team/live-build/-/blob/master/examples/hooks/reproducible/2006-reproducible-texlive-binaries-fmt-files.hook.chroot
> [1]  https://github.com/NixOS/nixpkgs/pull/227873

This is difficult to follow, because Debian and NixOS do not seem to
apply the same fixes. For example, the former wraps "faketime" around
"tex -ini tex.ini" call whereas the latter wraps it around
"fmtutil-sys --all" call.

By the way, how do you call "faketime" from (guix build-system texlive)?
It is not possible to use (gnu packages check) module from there, isn't
it?

Note that Guix never runs "mtxrun --generate", so I don't think UUIDs
are a problem in our case.

Regards,
-- 
Nicolas Goaziou






      reply	other threads:[~2024-10-20  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 12:19 bug#73613: texlive-luatex is not reproducible Maxim Cournoyer
2024-10-20  8:40 ` Nicolas Goaziou via Bug reports for GNU Guix [this message]

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=87r08b6ub6.fsf@nicolasgoaziou.fr \
    --to=bug-guix@gnu.org \
    --cc=73613@debbugs.gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=maxim.cournoyer@gmail.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 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).