From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 51252@debbugs.gnu.org
Subject: bug#51252: [core-updates-frozen] lualatex needs additional setup
Date: Sun, 17 Oct 2021 15:25:11 +0000 [thread overview]
Message-ID: <OEeidAceWLbJcLHC0q3L-6Lm6opZ41cpE5uSV3K88dIxQeUydodwhmFVnYVOFMKwF-vFC-g--S9uXYwGrrdKgGWXBHgaLEhEjuAdNoKiw_w=@protonmail.com> (raw)
Hello,
This is my first time trying out TeX on Guix, but ran into a problem trying to run lualatex on core-updates-frozen. Since I wasn't sure what I needed, I tried the huge full texlive package in case that solved the problem I was seeing. It did not.
Running lualatex on anything gives the output
This is LuaTeX, Version 1.13.0 (TeX Live 2021/GNU Guix)
restricted system commands enabled.
kpathsea: Running mktexfmt lualatex.fmt
/gnu/store/cpflshy9z2yzd8dybm0j9a7i0bscpxa2-texlive-bin-20210325/share/texmf-dist/scripts/texlive/fmtutil.pl: Unexpected non-option argument(s): lualatex.fmt
Try "fmtutil --help" for more information.
I can't find the format file `lualatex.fmt'!
xelatex on the same file and environment worked fine. After some digging, I could get the lualatex.fmt file by installing texlive-tex-ini-files and running
lualatex -ini /gnu/store/skznnf2n2f4dwg44gm8bvcn78157z69p-texlive-tex-ini-files-59745/share/texmf-dist/tex/generic/tex-ini-files/lualatex.ini
With this lualatex.fmt file present, lualatex runs and produces the correct output. I'm guessing this is not the expected procedure, though I haven't been able to test on master to compare yet. I wasn't sure if I missed a texlive- package, but xelatex working as is makes me think not.
John
next reply other threads:[~2021-10-17 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 15:25 John Kehayias via Bug reports for GNU Guix [this message]
2021-10-17 16:05 ` bug#51252: [core-updates-frozen] lualatex needs additional setup Robin Templeton
2021-10-17 16:05 ` John Kehayias via Bug reports for GNU Guix
2021-10-20 21:45 ` Ricardo Wurmus
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='OEeidAceWLbJcLHC0q3L-6Lm6opZ41cpE5uSV3K88dIxQeUydodwhmFVnYVOFMKwF-vFC-g--S9uXYwGrrdKgGWXBHgaLEhEjuAdNoKiw_w=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=51252@debbugs.gnu.org \
--cc=john.kehayias@protonmail.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).