From: "Ludovic Courtès" <ludo@gnu.org>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: Ricardo Wurmus <rekado@elephly.net>,
John Kehayias <john.kehayias@protonmail.com>,
51252-done@debbugs.gnu.org, Robin Templeton <robin@terpri.org>,
52268-done@debbugs.gnu.org
Subject: bug#52268: [PATCH core-updates-frozen] gnu: Add texlive-latex-luatex.
Date: Sun, 05 Dec 2021 16:40:33 +0100 [thread overview]
Message-ID: <871r2rukjy.fsf@gnu.org> (raw)
In-Reply-To: <20211204021611.80688-1-bauermann@kolabnow.com> (Thiago Jung Bauermann's message of "Fri, 3 Dec 2021 23:16:11 -0300")
Hello,
Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:
> When TeX Live was updated to version 2021 the ‘lualatex’ format started
> being generated with the LuaHBTeX engine, but the ‘lualatex’ command still
> uses the LuaTeX engine. This causes the command to fail:
>
> user@popigai:~$ lualatex hello.tex
> This is LuaTeX, Version 1.13.0 (TeX Live 2021/GNU Guix)
> restricted system commands enabled.
>
> ---! lualatex.fmt was written by luahbtex
> (Fatal format file error; I'm stymied)user@popigai:~$
>
> The correct way to fix this problem would be either to change texlive-bin
> to make ‘lualatex’ use the LuaHBTeX engine, or to change texlive-latex-base
> to generate ‘lualatex.fmt’ with LuaTeX. Both options would rebuild large
> parts of the world.
>
> Ricardo Wurmus suggested creating a new package to provide ‘lualatex.fmt’
> for LuaTeX as a workaround. This is what this package does.
>
> Fixes https://issues.guix.gnu.org/51252.
>
> * gnu/packages/tex.scm (texlive-latex-luatex): New variable.
Applied, thanks!
I don’t fully understand the issue but it looks like a reasonable and
non-intrusive fix.
Ludo’.
next prev parent reply other threads:[~2021-12-05 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 2:16 [bug#52268] [PATCH core-updates-frozen] gnu: Add texlive-latex-luatex Thiago Jung Bauermann via Guix-patches via
2021-12-05 15:40 ` Ludovic Courtès [this message]
2021-12-06 22:53 ` bug#51252: bug#52268: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871r2rukjy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=51252-done@debbugs.gnu.org \
--cc=52268-done@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=john.kehayias@protonmail.com \
--cc=rekado@elephly.net \
--cc=robin@terpri.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 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.