unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 51252@debbugs.gnu.org
Subject: bug#51252: [core-updates-frozen] lualatex needs additional setup
Date: Wed, 20 Oct 2021 21:45:35 +0000	[thread overview]
Message-ID: <87r1cf9xl9.fsf@elephly.net> (raw)
In-Reply-To: <OEeidAceWLbJcLHC0q3L-6Lm6opZ41cpE5uSV3K88dIxQeUydodwhmFVnYVOFMKwF-vFC-g--S9uXYwGrrdKgGWXBHgaLEhEjuAdNoKiw_w=@protonmail.com>

“texlive-latex-base” provides that file.  We disable a whole bunch 
of formats that we cannot build that early in the process, and 
then we run fmtutil-sys on the patched file.
The cause for trouble lies in texlive-kpathsea, which provides 
share/texmf-dist/web2c/fmtutil.cnf 
.  That file states how to build the various fmt files.

The file in the earlier version of Tex Live contains this line for the lualatex format:

    lualatex luatex language.dat,language.dat.lua lualatex.ini

the new file (on core-updates-frozen) says this:

    lualatex luahbtex language.dat,language.dat.lua lualatex.ini

i.e. it will try to build the lualatex fmt file with luahbtex 
instead of luatex.  I suppose at this point in the build we don’t 
actually have a working luahbtex, so fmtutil-sys doesn’t generate 
the correct lualatex.fmt.

I’m not sure how to fix this, but I guess we can avoid a world 
rebuild by adding an extra package that installs a working 
lualatex.fmt file.

-- 
Ricardo




  parent reply	other threads:[~2021-10-20 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-17 15:25 bug#51252: [core-updates-frozen] lualatex needs additional setup John Kehayias via Bug reports for GNU Guix
2021-10-17 16:05 ` Robin Templeton
2021-10-17 16:05 ` John Kehayias via Bug reports for GNU Guix
2021-10-20 21:45 ` Ricardo Wurmus [this message]
2021-11-23  1:40   ` Thiago Jung Bauermann via Bug reports for GNU Guix

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=87r1cf9xl9.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=51252@debbugs.gnu.org \
    /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).