17 Mar
2016
17 Mar
'16
11:18 p.m.
On Tue, 15 Mar 2016 22:26:29 +0300
Fat-Zer <fatzer2(a)gmail.com> wrote:
2016-03-15 22:25 GMT+03:00 Fat-Zer
<fatzer2(a)gmail.com>om>:
Thanks, Fat-Zer--you knocked loose the detail I'd forgotten (the existence of
the environment file). It looks like it's trying to write to either TDEHOME or
TDEROOTHOME, since setting those lets the build go through.
I clearly haven't been working with ebuilds enough lately.
E. Liddell
2016-03-13 0:09 GMT+03:00 E. Liddell
<ejlddll(a)googlemail.com>om>:
Please provide some common info like "emerge --info
'=trinity-base/libtdepim-14.0.0'" and
/var/tmp/portage/trinity-base/libkcal-14.0.0/temp/environment and what
exactly overlay
are you using.
Haven't finished the path... Sorry for noise... The short version: some auxiliary build commands
are trying to touch
directories the package manager doesn't want them to touch, resulting
in sandbox violation failures of the following format:
===
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: mkdir
S: deny
P: /root/.trinity
A: /root/.trinity
R: /root/.trinity
C: /usr/trinity/14/bin/tdeconfig_compiler
/var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfg
/var/tmp/portage/trinity-base/libkcal-14.0.0/work/tdepim/libkcal/htmlexportsettings.kcfgc
Portage should hook HOME to
${PORTAGE_TMPDIR}/portage/${CATEGORY}/${PF}/homedir. I believe there
is something wrong about your configuration...
I've just tried — libtdepim-9999 build well for me.
Please provide some common info like "emerge --info
'=trinity-base/libtdepim-14.0.0'" and
/var/tmp/portage/trinity-base/libkcal-14.0.0/ and what exactly overlay
are you using.