TeX font maps are not reproducible

  • Open
  • quality assurance status badge
Details
3 participants
  • Konrad Hinsen
  • Ludovic Courtès
  • Nicolas Goaziou
Owner
unassigned
Submitted by
Konrad Hinsen
Severity
important
K
K
Konrad Hinsen wrote on 16 Sep 15:59 +0200
(address . bug-guix@gnu.org)
m1ttefwvgl.fsf@fastmail.net
Hi everyone,

The font maps generated during profile creation (procedure
texlive-font-maps in guix/profiles.scm) are not reproducible: the order
in which the files are listed in the ls-R file is not deterministic.

As a consequence, files generated from profiles, such as Docker or
Singularity containers, are not reproducible.

I suspect that the culprit is the mktexlsr utility which generates the
non-deterministic ls-R files. It's worth exploring if it can be patched.

Cheers,
Konrad.
N
N
Nicolas Goaziou wrote on 16 Sep 20:02 +0200
(name . Konrad Hinsen)(address . konrad.hinsen@fastmail.net)(address . 73295@debbugs.gnu.org)
87bk0nzdc7.fsf@nicolasgoaziou.fr
Hello,

Konrad Hinsen <konrad.hinsen@fastmail.net> writes:

Toggle quote (4 lines)
> The font maps generated during profile creation (procedure
> texlive-font-maps in guix/profiles.scm) are not reproducible: the order
> in which the files are listed in the ls-R file is not deterministic.

Unfortunately, I think there are other parts not reproducible in TeX
Live (e.g., formats).

Toggle quote (3 lines)
> I suspect that the culprit is the mktexlsr utility which generates the
> non-deterministic ls-R files. It's worth exploring if it can be patched.

There is a sort option in the "mktexlsr" executable. It doesn't seem to
be accessible from the command line, tho. My Perl-fu is too weak to know
how to proceed from there.

Regards,
--
Nicolas Goaziou
L
L
Ludovic Courtès wrote on 26 Sep 15:27 +0200
control message for bug #73295
(address . control@debbugs.gnu.org)
87cykqo893.fsf@gnu.org
severity 73295 important
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 73295@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 73295
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch