From: Damien Thiriet <damien@thiriet.web4me.fr>
To: ntg-context@ntg.nl
Subject: fatal error: there is no valid writable cache path defined
Date: Fri, 15 Nov 2019 21:20:16 +0100 [thread overview]
Message-ID: <20191115202016.GA6365@maroilles.home> (raw)
Hi,
I ran into trouble with caches. First I updated the new binaries
and they compiled fine under OpenBSD6.6-amd64.
Then I uploaded some binaries Hans asked me to test, moved this
luametatex to /usr/local/context/tex/texmf-openbsd6.6-amd64/bin/,
deleted files inside /usr/local/context/tex/texmf-cache (but not
texmf-cache itself, since I understand whipe as cleaning inside it)
and ran mtx-run --generate then context --auto.
When I tried afterwards to compile those new binaries, I get this
error
This is LuaMetaTeX, Version 2.01.0
resolvers > caches > fatal error: there is no valid writable cache
path defined
Running mtx-run --generate on my user account did not solve the problem.
I certainly did something wrong.
I tried to revert to the standard lmtx binaries running install.sh
but those errors are still here.
Regards,
Damien Thiriet
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2019-11-15 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 20:20 Damien Thiriet [this message]
2019-11-16 9:00 ` Hans Hagen
2019-11-15 20:52 Damien Thiriet
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=20191115202016.GA6365@maroilles.home \
--to=damien@thiriet.web4me.fr \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).