>>> Compiling source in /var/tmp/portage/net-fs/minio-2019.02.26.19.51.46/work/minio-2019.02.26.19.51.46 ... /var/tmp/portage/net-fs/minio-2019.02.26.19.51.46/work/minio-2019.02.26.19.51.46/src/github.com/minio/minio /var/tmp/portage/net-fs/minio-2019.02.26.19.51.46/work/minio-2019.02.26.19.51.46 failed to initialize build cache at /root/cache/go-build: mkdir /root/cache: permission denied failed to initialize build cache at /root/cache/go-build: mkdir /root/cache: permission denied failed to initialize build cache at /root/cache/go-build: mkdir /root/cache: permission denied * ERROR: net-fs/minio-2019.02.26.19.51.46::gentoo failed (compile phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl_20190226-081914 ------------------------------------------------------------------- Please see the tracker bug for details. gcc-config -l: [1] x86_64-pc-linux-gnu-8.3.0 * 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) [3] ruby26 (with Rubygems) * Available Rust versions: [1] rust-1.32.0 * emerge -qpvO net-fs/minio [ebuild N ] net-fs/minio-2019.02.26.19.51.46
Created attachment 566954 [details] emerge-info.txt
Created attachment 566956 [details] emerge-history.txt
Created attachment 566958 [details] environment
Created attachment 566960 [details] etc.portage.tbz2
Created attachment 566962 [details] net-fs:minio-2019.02.26.19.51.46:20190228-121358.log
Does it happen that you are running emerge as `sude emerge <stuff>` ?
(In reply to Mikle Kolyada from comment #6) > Does it happen that you are running emerge as `sude emerge <stuff>` ? no, emerge is called by root - pls see the blocker for background.
(In reply to Toralf Förster from comment #7) > (In reply to Mikle Kolyada from comment #6) > > Does it happen that you are running emerge as `sude emerge <stuff>` ? > > no, emerge is called by root - pls see the blocker for background. BTW it might be forced to be seen now much more often since gcc-8.3 appeared ?
(In reply to Toralf Förster from comment #8) > (In reply to Toralf Förster from comment #7) > > (In reply to Mikle Kolyada from comment #6) > > > Does it happen that you are running emerge as `sude emerge <stuff>` ? > > > > no, emerge is called by root - pls see the blocker for background. > > BTW it might be forced to be seen now much more often since gcc-8.3 appeared > ? Unlikely (compiled fine by me with the version). The only thing I can think of is your image missconfiguration, as no major changes have been done since previous release, and also. What is interesting, golang only tries to create files in a homedir if neither different defaults was set, nor set defaults were ignored. This looks like your GOCACHE settings are ignored.
Here're 2 examples how to solve such issues: https://bugs.gentoo.org/679110 https://bugs.gentoo.org/678974
(In reply to Toralf Förster from comment #10) > Here're 2 examples how to solve such issues: > > https://bugs.gentoo.org/679110 > https://bugs.gentoo.org/678974 well, GOCACHE is irrelevant her as being inherited from the eclass. unset XDG_CACHE_HOME seems to be the right one
(In reply to Mikle Kolyada from comment #11) > (In reply to Toralf Förster from comment #10) > > Here're 2 examples how to solve such issues: > > > > https://bugs.gentoo.org/679110 > > https://bugs.gentoo.org/678974 > > well, GOCACHE is irrelevant her as being inherited from the eclass. > > unset XDG_CACHE_HOME seems to be the right one It is forced in https://github.com/toralf/tinderbox/blob/master/bin/job.sh#L1361 to catch short comings - as stated in the blocker bug.
FWIW this issue appears first at 20190115-043743 AFAICT - atr all images from that time on.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3c5e0c076526ad1baf92e56493ddb0e5ba299d19 commit 3c5e0c076526ad1baf92e56493ddb0e5ba299d19 Author: Mikle Kolyada <zlogene@gentoo.org> AuthorDate: 2019-03-12 16:02:15 +0000 Commit: Mikle Kolyada <zlogene@gentoo.org> CommitDate: 2019-03-12 16:04:43 +0000 net-fs/minio: fix sandbox issue Closes: https://bugs.gentoo.org/679060 Signed-off-by: Mikle Kolyada <zlogene@gentoo.org> Package-Manager: Portage-2.3.62, Repoman-2.3.11 net-fs/minio/minio-2019.01.10.00.21.20.ebuild | 2 ++ net-fs/minio/minio-2019.01.16.21.44.08.ebuild | 2 ++ net-fs/minio/minio-2019.01.23.23.18.58.ebuild | 2 ++ net-fs/minio/minio-2019.01.31.00.31.19.ebuild | 2 ++ net-fs/minio/minio-2019.02.06.21.16.36.ebuild | 2 ++ net-fs/minio/minio-2019.02.12.21.58.47.ebuild | 2 ++ net-fs/minio/minio-2019.02.14.00.21.45.ebuild | 2 ++ net-fs/minio/minio-2019.02.20.22.44.29.ebuild | 2 ++ net-fs/minio/minio-2019.02.26.19.51.46.ebuild | 2 ++ net-fs/minio/minio-2019.03.06.22.47.10.ebuild | 2 ++ 10 files changed, 20 insertions(+)
