ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Carlos via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
Date: Sat, 25 Mar 2023 23:09:18 +0100	[thread overview]
Message-ID: <7d13a3bf-1d5e-582c-0e76-82339ec28209@xs4all.nl> (raw)
In-Reply-To: <20230325213606.in7yiyshriehm2me@gmail.com>

On 3/25/2023 10:36 PM, Carlos via ntg-context wrote:
> On Sat, Mar 25, 2023 at 09:45:25PM +0100, Hans Hagen via ntg-context wrote:
>> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
>>
>>>           ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in upvalue 'walk_tree'
>> Maybe your OSFONTDIR is pointing to empty. Does
> 
> Good call. Thank you for the reminder Hans. But no. That variable was set long ago . Even appended it to both the bash initialization file and also under /etc/profile (just in case here). Alpine uses ash so shells must be changed
> 
>>
>>    mtxrun --script font --reload
>>
> fonts           | names | 3092 afm files checked,   okay
> fonts           | names | identifying tree font files with suffix 'AFM'
> fonts           | names | scanning path '/home/ce/.texlive2023/texmf-config' for AFM files
> fonts           | names | 0 AFM files checked,   okay
> fonts           | names | scanning path '/home/ce/texmf' for AFM files
> fonts           | names | 0 AFM files checked,   okay
> fonts           | names | scanning path '/usr/local/texlive/2023/texmf-config' for AFM files
> fonts           | names | 0 AFM files checked,   okay
> fonts           | names | scanning path '/usr/local/texlive/2023/texmf-var' for AFM files
> fonts           | names | 0 AFM files checked,   okay
> fonts           | names | scanning path '/usr/local/texlive/2023/texmf-local' for AFM files
> fonts           | names | 24 AFM files checked,   okay
> fonts           | names | scanning path '/usr/local/texlive/2023/texmf-dist' for AFM files
> fonts           | names | 3092 AFM files checked,   okay
> fonts           | names | 6232 tree files identified,  14 skipped,  14 duplicates,  6218 hash entries added,  runtime 8.458 seconds
> fonts           | names | identifying system font files with suffix 'otf'
> fonts           | names | variable 'OSFONTDIR' specifies path '/home/ce'
> fonts           | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts'
> fonts           | names | globbing path '/home/ce/**.otf'
> 
> lua error : function call: /usr/local/texlive/2023/bin/x86_64-linuxmusl/mtxrun.lua:649: cannot open /home/ce/cache/headers/imaps:@gmail.com@imap.gmail.com/[Gmail]/.: Permission denied

hm, but is home/ce/cache a path where there are fonts to be found? 
something sets that path to be a fully recursive font dir

can you set OSFONTDIR to '/usr/share/fonts'

(personally i never use system fonts, i always put copies in 
texmf-fonts/fonts/data becasue system fonts can change or disappear)

> Recall that the other folders owned by root had to be moved out of the way
> 
> So it seems it wasn't enough, nope. Now it wants access elsewhere
> 
> bottom line: it wants root permissions or else fails flat out

well, it's not entirely clear what generates the permission denied; i 
can check for the home/ce being readable but doing that for every 
regular file below that would add lots of slow checks and i'm not even 
sure if it would fix it; i can try to check nested dirs but that then 
also obscures possible issues

Hans
  -----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2023-03-25 22:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25 19:55 Carlos via ntg-context
2023-03-25 20:26 ` Hans Hagen via ntg-context
2023-03-25 20:46   ` Carlos via ntg-context
2023-03-26 23:25   ` Carlos via ntg-context
2023-03-27 13:31   ` Carlos via ntg-context
2023-03-27 13:43     ` Hans Hagen via ntg-context
2023-03-28 17:05       ` Carlos via ntg-context
2023-03-28 22:48         ` Hans Hagen via ntg-context
2023-03-31 11:40           ` Carlos via ntg-context
2023-03-31 14:40             ` Hans Hagen via ntg-context
2023-03-31 20:08               ` Carlos via ntg-context
2023-03-31 20:22                 ` Hans Hagen via ntg-context
2023-04-01 21:21                   ` Carlos via ntg-context
2023-04-02  8:41                     ` Hans Hagen via ntg-context
2023-04-05  9:28                       ` Carlos via ntg-context
2023-03-25 20:45 ` Hans Hagen via ntg-context
2023-03-25 21:36   ` Carlos via ntg-context
2023-03-25 22:09     ` Hans Hagen via ntg-context [this message]
2023-03-25 22:42       ` Carlos via ntg-context
2023-03-26 11:04         ` Henning Hraban Ramm via ntg-context
2023-03-26 13:08           ` Carlos via ntg-context
2023-03-26 13:21             ` Hans Hagen via ntg-context
2023-03-26 19:50               ` Carlos via ntg-context
2023-03-26 23:38           ` Carlos via ntg-context

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=7d13a3bf-1d5e-582c-0e76-82339ec28209@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).