registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied

* registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
@ 2023-03-25 19:55 Carlos via ntg-context
  2023-03-25 20:26 ` Hans Hagen via ntg-context
  2023-03-25 20:45 ` Hans Hagen via ntg-context
  0 siblings, 2 replies; 24+ messages in thread
From: Carlos via ntg-context @ 2023-03-25 19:55 UTC (permalink / raw)
  To: ntg-context; +Cc: Carlos

Hello list:

This is under a fresh TeXLive installation. Sort as to put aside any texlive prepackaged issues.

And the followign lines is the output of the error I've been having with the call of context on a recent texlive installation by both mtxrun --generate and luatools --generate right after.

mtxrun --script cache --erase has also been called out to no avail

registered function call [1160]: ...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied
stack traceback:
        [C]: in upvalue 'func'
        ...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: in function 'lfs.dir'
        .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:139: in upvalue 'glob_pattern_table'
        .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table'
        .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table'
        .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table'
        .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table'
        .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:180: in function <.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:169>
        (...tail calls...)
        ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in upvalue 'walk_tree'
        ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1190: in local 'method'
        ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1152: in local 'traverse'
        ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1200: in upvalue 'analyzefiles'
        ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1286: in field 'identify'
        ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1311: in field 'load'
        ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1322: in field 'load'
        ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1588: in field 'getfilename'
        ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:835: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:828>
        (...tail calls...)
        ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:378: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:366>
        (...tail calls...)
        ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:485: in field 'read'
        ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1377: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1234>
        (...tail calls...)
51         ;definetypeface[MyLucida][rm][serif][lucida][default][encoding=texnansi]
52      \definetypeface[MyLucida][ss][sans][lucida][default][encoding=texnansi]
53      \definetypeface[MyLucida][tt][mono][lucida][default][encoding=texnansi]
54     \stoptypescript
55     
56     
57     \starttext
58     
59     \usetypescriptfile[type-lucida]
60     \usetypescript[Lucida][texnansi]
61 >>  \setupbodyfont[MyLucida, 10pt] 
62     
63     \input zapf
64     
65     \input tufte
66     
67     
68     \stoptext
69     
mtx-context     | fatal error: return code: 1

it doesn't matter either whatever the typescript name goes and whether is type-lucida from texnansi-lucida-map file as it has been previously advised to change the name from . makes no difference.

Is LuaLaTeX behaving the same way? 

Answer: no.

The permission denied message happened first with folders whose permeissions were not owned by the user, but the root, so I moved the files out of harm's way to another folder . Anothr folder, NOT a subfolder. 

Then the problem persisted to read folders and even subfolders (directories, subdirectories) with cache filenames and headers that follow

So let's not get to apprehensive, It's understandable that say, not reasonable, but understandable maybe? that mtxrun or lua for that matter will stop right before.

So the folders were moved right after. Gone out of the binaries. But what I can't understand is why would it try to access cache folders unrelated with anything TeX or header folders for that matter????

This is perhaps more serious than I thought at first. 

And Let's not blame the TeXLive pre-packaged running under Alpine Linux. To put it in laymans' terms and If anything is clear to me, is that Alpine ir not letting Lua running beserk on the system and its folders, owned by whatever/whoever else, and with pesmissions set elsewhere. 

It's out of the question. Or it rather be. This is all writh a fresh TeX Live Installation. 

I mentioned the problem that may arise by questioning the Alpine installation because there were some problems with some binaries from the prepackaged TeX Live put out by Alpine devs. But this is not prepackaged.   Nope. 

-- 

"We are on the verge: Today our program proved Fermat's next-to-last theorem."
		-- Epigrams in Programming, ACM SIGPLAN Sept. 1982

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 24+ messages in thread