VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: mkostemp S: deny ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_developer-abi32+64-20190810-161025 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.12.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO media-sound/lilypond [ebuild N ] media-sound/lilypond-2.19.80-r1 USE="-debug -emacs -guile2 -profile -vim-syntax" PYTHON_TARGETS="python2_7"
Created attachment 586632 [details] emerge-info.txt
Created attachment 586634 [details] emerge-history.txt
Created attachment 586636 [details] environment
Created attachment 586638 [details] etc.portage.tbz2
Created attachment 586640 [details] logs.tbz2
Created attachment 586642 [details] media-sound:lilypond-2.19.80-r1:20190812-132218.log
Created attachment 586644 [details] sandbox-6.log
Created attachment 586646 [details] temp.tbz2
This is probably due to the fact that the lilypond configure script uses fc-list to search for installed URW-fonts. fontconfig however maintains .uuid files and when fc-list is executed it also silently generates or updates these files. This leads to a sandbox violation during configuration phase. A workaround for me was to execute "fc-list C059:fontformat=CFF file" as root before emerging lilypond so all .uuid files where generated beforehand. Is this an upstream issue? Should the build system of a tool better not depend on a program that silently writes to the disk somewhere in the filesystem?
Still happens on media-sound/lilypond-2.21.1
This should be marked as blocking https://bugs.gentoo.org/223077 And https://github.com/gentoo/gentoo/pull/16568 fixes it
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bd80db217c847c1b4c9d7bccc906610e66fb4b36 commit bd80db217c847c1b4c9d7bccc906610e66fb4b36 Author: Alexey Sokolov <sokolov@google.com> AuthorDate: 2020-07-03 11:07:26 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2020-07-05 09:33:21 +0000 media-sound/lilypond: fix sandbox violation Package-Manager: Portage-2.3.99, Repoman-2.3.23 Signed-off-by: Alexey Sokolov <alexey+gentoo@asokolov.org> Closes: https://bugs.gentoo.org/692010 Closes: https://github.com/gentoo/gentoo/pull/16568 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> media-sound/lilypond/lilypond-2.21.1.ebuild | 1 + media-sound/lilypond/lilypond-9999.ebuild | 1 + 2 files changed, 2 insertions(+)
