> I think it is fixed in "tex-team" branch.

Thank you Nicolas,

I tried out your changes, and although the "permission denied" error no
longer shows up, running context in the terminal (user home intact,
i.e. without my previous configuration hack) yields the following
message:


mtxrun          | forcing cache reload
resolvers       | resolving | configuration files already identified
resolvers       | resolving | loading configuration file 
'/gnu/store/s0xbwkg8jqhbn85rqv90g30lxn5agf88-texlive-luatex-66594/share/texmf-dist/web2c/texmfcnf.lua'
resolvers       | resolving |
resolvers       | resolving | locating list of 'home:.texlive2023/texmf-config' 
(runtime) (tree:///home:.texlive2023/texmf-config)
resolvers       | methods | resolving, method 'locators', how 'uri', handler 
'tree', argument 'tree:///home:.texlive2023/texmf-config'
resolvers       | trees | locator 'home:.texlive2023/texmf-config' not found
resolvers       | resolving | locating list of 'home:.texlive2023/texmf-var' 
(runtime) (tree:///home:.texlive2023/texmf-var)
resolvers       | methods | resolving, method 'locators', how 'uri', handler 
'tree', argument 'tree:///home:.texlive2023/texmf-var'
resolvers       | trees | locator 'home:.texlive2023/texmf-var' not found
resolvers       | resolving | locating list of 'home:texmf' (runtime) 
(tree:///home:texmf)
resolvers       | methods | resolving, method 'locators', how 'uri', handler 
'tree', argument 'tree:///home:texmf'
resolvers       | trees | locator 'home:texmf' not found
resolvers       | resolving | locating list of 'selfautoparent:texmf-local' 
(runtime) (tree:///selfautoparent:texmf-local)
resolvers       | methods | resolving, method 'locators', how 'uri', handler 
'tree', argument 'tree:///selfautoparent:texmf-local'
resolvers       | trees | locator 'selfautoparent:texmf-local' not found
resolvers       | resolving |
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-context.lua' using hash 
'lua::mtx-t-context.lua'
resolvers       | resolving | using suffix based filetype 'scripts'
resolvers       | resolving | remembering file 'mtx-t-contexts.lua' using hash 
'lua::mtx-t-contexts.lua'
resolvers       | resolving | remembered file 'mtx-t-context.lua'
resolvers       | resolving | using suffix based filetype 'scripts'
resolvers       | resolving | remembering file 'context.lua' using hash 
'lua::context.lua'
mtxrun          | unknown script 'context.lua' or 'mtx-context.lua

It seems that mtxrun fails to find either files, the same message will
also appear if invoking context through mtxrun via the --script flag.

-- 
Aziz

Reply via email to