Created attachment 470622 [details]
Occurs when trying to emerge libreoffice-22.214.171.124 with PYTHON_SINGLE_TARGET="python3_5 -python2_7 -python3_4" PYTHON_TARGETS="python2_7 python3_4 python3_5")
build.log can be seen in build.log
Created attachment 470624 [details]
emerge --info =libreoffice-126.96.36.199
Possibly affect bug #615474.
Meanwhile we have 188.8.131.52 and 184.108.40.206 in tree, do you still have that issue?
I have sandbox violation with libreoffice-220.127.116.11, unrelated to Java or Python:
checking for fc-match... /usr/bin/fc-match
checking font mapping for 'Calibri'... * ACCESS DENIED: mkostemp: /usr/share/fonts/util/.uuid.TMP-XXXXXX
checking font mapping for 'DejaVuSans'... * ACCESS DENIED: mkostemp: /usr/share/fonts/util/.uuid.TMP-XXXXXX
/usr/share/fonts/util/ directory does not have .uuid and fc-match surely as hell tries to create one.
Not sure how this dir ended up without .uuid but runnig fc-match outside of portage creates this uuid and emerge problem goes away.
In this bug case situation is quite similar - Python interpreter surely as hell tries to pythoncompile some own modules that just happen to be used during libreoffice configure phase and for some reason are not pythoncompiled yet.
Now, why does Python interpreter actually thinks it has permissions to create/write any files? Doesn't portage use own portage user that has no affiliation to root? Or it's just expected for all site-packages/* to be pythoncompiled and in reporter's case, due to some perhaps bug in Python post-install phase, it was not the case?
That's unrelated, update fontconfig and it is fixed.
(In reply to Andreas Sturmlechner from comment #3)
> Meanwhile we have 18.104.22.168 and 22.214.171.124 in tree, do you still have that issue?