<beerman>
ukky not sure, it happend rather randomly i'd like to say
<ukky>
root might own log file: find /home/pkgmk/work/mesa -type f -name '*ninja_log*' -ls
<beerman>
i am not using fakeroot, so i wonder which other user it should be
<jaeger>
I use fakeroot but I can give it a test
<beerman>
the holy grail of temporary fixes: chmod 777
<ukky>
I just rebuilt mesa, with fakeroot, and meson install doesn't complain
<beerman>
yeah, next port built was another using meson/ninja, worked flawlessly as well
<beerman>
this is weird...
<ukky>
are you building as user 'pkgmk'?
<beerman>
no
<beerman>
i am root, the log is owned by root:root and had 644 permissions
<beerman>
so i really wonder whats the actual problem
<beerman>
also it was working a day ago, nothing actually changed 😄
<ukky>
rebeuilt with 'pkgmk --keep-work'. Log file src/build/.ninja_log is owned by 'pkgmk:pkgmk', mode 0644, and this doesn't trigger any permission error.
<ukky>
s/rebeuilt/rebuilt
<jaeger>
no problems with fakeroot in my container