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_desktop_plasma-20200109-062024 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * clang: clang version 9.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/9/bin llvm: 9.0.1 Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.40.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.14.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Wed, 15 Jan 2020 18:46:09 +0000 emerge -qpvO media-gfx/gimp [ebuild N ] media-gfx/gimp-2.10.14 USE="alsa mng udev -aalib (-altivec) (-aqua) -debug -doc -gnome -heif -jpeg2k -openexr -postscript -python -test -unwind -vector-icons -webp -wmf -xpm" CPU_FLAGS_X86="mmx sse" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7"
it is still an issue at unstable amd64 tinderbox image 17.1_desktop_plasma-20200109-062024 (see bug 698526)
Created attachment 603412 [details] emerge-info.txt
Created attachment 603414 [details] emerge-history.txt
Created attachment 603416 [details] etc.portage.tbz2
Created attachment 603418 [details] logs.tbz2
Created attachment 603420 [details] media-gfx:gimp-2.10.14:20200115-192522.log.bz2
Created attachment 603422 [details] sandbox-4.log
If this is similar to https://bugs.gentoo.org/69852 then it seems that this time media-fonts/x11fonts-jmk-3.0-r3 causes the issue: the ebuild doesn't inherit font.eclass therefore there is no call of font_src_install within custom src_indtall() and no call of font_pkg_postinst (because no inherit font.eclass) to update cache. I assign it to gentoo fonts project (with CC myself) and will try to reproduce it locally.
Sorry, I re-assigned bug before renaming of it and now haven't access to do it. @Toralf, thank you for mentioning similar issue.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9431fc73243d4b58d3f3e07e20136e7b62874a98 commit 9431fc73243d4b58d3f3e07e20136e7b62874a98 Author: Sergey Torokhov <torokhov-s-a@yandex.ru> AuthorDate: 2020-01-17 23:18:16 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2020-01-18 06:28:09 +0000 media-fonts/x11fonts-jmk: fix Updating global fontcache Without inheritance of font.eclass the pkg_postinst() phase doesn't update the global fontcache causing media-gfx/gimp sandbox install() phase issue. Closes: https://bugs.gentoo.org/705502 Signed-off-by: Sergey Torokhov <torokhov-s-a@yandex.ru> Closes: https://github.com/gentoo/gentoo/pull/14372 Signed-off-by: Joonas Niilola <juippis@gentoo.org> .../x11fonts-jmk/x11fonts-jmk-3.0-r4.ebuild | 36 ++++++++++++++++++++++ 1 file changed, 36 insertions(+)
