Running `context` fails with TeX Live 2023: mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'

[Vítek Novotný]

On Mon, Mar 27, 2023 at 03:29:45PM -0600, Karl Berry wrote:
> Hi Vit,
> 
>     resolvers       | resolving | warning: no lua configuration files found
>     resolvers       | resolving | no texmf paths are defined (using TEXMF)
> 
> This would seem to be the problem. Do you have a texmfcnf.lua file?
> There should be the distributed one in texmf-dist/web2c/texmfcnf.lua 
> and also generated by the installer in (by default)
> /usr/local/texlive/2023/texmfcnf.lua.
> Both are alongside a texmf.cnf file.

Dear Karl,

I do:

    $ ls -lh /usr/local/texlive/2023/texmfcnf.lua
    -rw-r--r-- 1 root root 524 Mar 27 12:17 /usr/local/texlive/2023/texmfcnf.lua

> Can you run the luametatex binary (luametatex --version) on its own?

I can:

    $ luametatex --version
    This is LuaMetaTeX, Version 2.10.07

    Execute 'luametatex --credits' for credits and version details.

    There is NO warranty. Redistribution of this software is covered by the terms
    of the GNU General Public License, version 2 or (at your option) any later
    version. For more information about these matters, see the file named COPYING
    and the LuaMetaTeX source.

    Functionality : level 20230310
    Support       : context at ntg.nl
    Copyright     : The Lua(Meta)TeX Team(s) (2005-2023+)

    The LuaMetaTeX project is related to ConTeXt development. This macro package
    tightly integrates TeX and MetaPost in close cooperation with Lua. Updates will
    happen in sync with ConTeXt and when needed. Don't be fooled by unchanged dates:
    long term stability is the objective.

> Other than that, maybe you have some envvar set? I do not know how
> luametatex looks up files or how to debug it. It doesn't use kpathsea
> and I don't know what "(using TEXMF)" really means.  Maybe Hans or Mojca
> or Siep or some other lmtx-savvy person can provide some clues.

I believe Max Chernoff commented on this bit.

> For additional information, you could try running context --generate
> --luatex, which generates the cache for the luatex-based context mkiv
> (as I understand it). (install-tl also runs this.) Maybe that will
> succeed or fail in a different way, providing more information. --best, karl.

It does fail in new interesting ways:

    $ sudo context --generate --luatex
    mtxrun          | forcing cache reload
    resolvers       | resolving | looking for regular 'texmfcnf.lua' on given path '/root/texmf/web2c' from specification 'home:texmf/web2c'
    resolvers       | resolving | looking for regular 'texmfcnf.lua' on given path '/usr/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c'
    resolvers       | resolving | looking for regular 'texmfcnf.lua' on given path '/usr/texmf-context/web2c' from specification 'selfautoparent:/texmf-context/web2c'
    resolvers       | resolving | looking for regular 'texmfcnf.lua' on given path '/usr/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c'
    resolvers       | resolving | looking for regular 'texmfcnf.lua' on given path '/usr/texmf/web2c' from specification 'selfautoparent:/texmf/web2c'
    resolvers       | resolving | looking for fallback 'contextcnf.lua' on given path '/root/texmf/web2c' from specification 'home:texmf/web2c'
    resolvers       | resolving | looking for fallback 'contextcnf.lua' on given path '/usr/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c'
    resolvers       | resolving | looking for fallback 'contextcnf.lua' on given path '/usr/texmf-context/web2c' from specification 'selfautoparent:/texmf-context/web2c'
    resolvers       | resolving | looking for fallback 'contextcnf.lua' on given path '/usr/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c'
    resolvers       | resolving | looking for fallback 'contextcnf.lua' on given path '/usr/texmf/web2c' from specification 'selfautoparent:/texmf/web2c'
    resolvers       | resolving |
    resolvers       | resolving | warning: no lua configuration files found
    resolvers       | resolving | no texmf paths are defined (using TEXMF)
    resolvers       | resolving |
    mtxrun          | the resolver databases are not present or outdated
    resolvers       | resolving | using suffix based filetype 'scripts'
    resolvers       | resolving | remembering file 'mtx-context.lua' using hash 'lua::mtx-context.lua'
    resolvers       | resolving | using suffix based filetype 'scripts'
    resolvers       | resolving | remembering file 'mtx-contexts.lua' using hash 'lua::mtx-contexts.lua'
    resolvers       | resolving | remembered file 'mtx-context.lua'
    resolvers       | resolving | using suffix based filetype 'scripts'
    resolvers       | resolving | remembering file 'mtx-t-mtx-context.lua' using hash 'lua::mtx-t-mtx-context.lua'
    resolvers       | resolving | using suffix based filetype 'scripts'
    resolvers       | resolving | remembering file 'mtx-t-mtx-contexts.lua' using hash 'lua::mtx-t-mtx-contexts.lua'
    resolvers       | resolving | remembered file 'mtx-t-mtx-context.lua'
    resolvers       | resolving | remembered file 'mtx-context.lua'
    mtxrun          | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'

> P.S. mtxrun --generate does work for me, and others. So it's not just a
> global failure.

As stated, I can reproduce this on two different binary platforms and on
both a netinstall of TeX Live and the texlive/texlive:latest Docker
image. Seems global to me.

Best,
Vit
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://tug.org/pipermail/tex-live/attachments/20230329/bd3a467c/attachment.sig>