From: Marco van Hulten <marco@hulten.org>
To: help-guix@gnu.org
Subject: Re: TeX Live issues
Date: Sun, 19 Jan 2020 21:17:14 +0100 [thread overview]
Message-ID: <20200119211714.18fbdfdd@jasniac.instanton> (raw)
In-Reply-To: <20200119173421.19839e02@jasniac.instanton>
Je 19 jan 17:34 skribis Marco:
> I had GUIX_LOCPATH set but did not have glibc-locales installed.
> Installing this packages solved the issue and I can now compile TeX
> files with success. Thanks for the help!
>
> To recap, to reduce the damage of going off-topic, compiling a TeX file
> with {,lua}latex works when only texlive-base is installed. I had to
> do this:
>
> guix pull --branch=core-updates
> guix package -r texlive texlive-bin texlive-latex-base -i texlive-base
I've done all these things (locales, installed only texlive-base from
core-updates branch, removed any other texlive* packages and removed
~/.texlive*), now under a different user, same Guix system. I have
issues again:
```
$ lualatex apen
This is LuaTeX, Version 1.10.0 (TeX Live 2019)
restricted system commands enabled.
kpathsea: Running mktexfmt lualatex.fmt
mktexfmt: mktexfmt is using the following fmtutil.cnf files (in precedence order):
mktexfmt: mktexfmt is using the following fmtutil.cnf file for writing changes:
mktexfmt: /home/otheruser/.texlive2019/texmf-config/web2c/fmtutil.cnf
mktexfmt [INFO]: writing formats under /home/otheruser/.texlive2019/texmf-var/web2c
mktexfmt [INFO]: did not find entry for byfmt=lualatex, skipped
mktexfmt [INFO]: Total formats: 0
mktexfmt [INFO]: exiting with status 0
I can't find the format file `lualatex.fmt'!
```
Given the similarity of the issue (except for that this does not now
relate to the package texlive-bin-20180414 as it is not installed), the
fact that I won't have a lot of time at the moment and don't want to
waste other people's time, and that there will be a next staging branch
soon, would it be best to wait when the latter happens and switch to
that one?
Of course, if there is still an actual issue (instead of user error) it
may actually be relevant to look at this more closely (but I don't know
anymore!), so here is at least some info:
$ guix package -I | grep texlive
texlive-base 51265 out /gnu/store/iccw4cdkcgmccl5svndji830k55v9cxy-texlive-base-51265
—Marco
prev parent reply other threads:[~2020-01-19 20:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 7:48 TeX Live issues Marco van Hulten
2020-01-17 7:51 ` Marco van Hulten
2020-01-17 12:02 ` Ricardo Wurmus
2020-01-17 9:03 ` Ricardo Wurmus
[not found] ` <20200117124027.50e7287d@gfi063209.klientdrift.uib.no>
2020-01-17 12:05 ` Ricardo Wurmus
2020-01-18 15:08 ` Marco van Hulten
2020-01-18 15:12 ` Ricardo Wurmus
2020-01-18 17:29 ` Marco van Hulten
2020-01-19 8:59 ` Ricardo Wurmus
2020-01-19 10:16 ` Marco van Hulten
2020-01-19 13:42 ` Ricardo Wurmus
2020-01-19 14:57 ` Marco van Hulten
2020-01-19 15:01 ` Ricardo Wurmus
2020-01-19 16:34 ` Marco van Hulten
2020-01-19 20:17 ` Marco van Hulten [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=20200119211714.18fbdfdd@jasniac.instanton \
--to=marco@hulten.org \
--cc=help-guix@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.
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).