* [gentoo-user] Sandbox violations when installing a Python package
@ 2017-12-06 14:08 99% Helmut Jarausch
0 siblings, 0 replies; 1+ results
From: Helmut Jarausch @ 2017-12-06 14:08 UTC (permalink / raw
To: gentoo-user
Hi,
I hope somebody can help me.
I've written a new ebuild for "dev-python/imapclient-1.1.0" (the
latest version in the tree is version 0.13)
I've just copied dev-python/imapclient-0.13.ebuild and remove a patch
which is no longer needed.
Ebuilding this packages dies of a Sandbox Violation:
>>> Compiling source in
>>> /var/tmp/portage/dev-python/imapclient-1.1.0/work/IMAPClient-1.1.0
>>> ...
* python3_6: running distutils-r1_run_phase
distutils-r1_python_compile
>>> snip <<<
File "/usr/lib64/python3.6/site-packages/setuptools/sandbox.py",
line 411, in _violation
raise SandboxViolation(operation, args, kw)
setuptools.sandbox.SandboxViolation: SandboxViolation:
mkdir('/var/tmp/portage/dev-python/imapclient-1.1.0/work/IMAPClient-1.1.0-python3_6/lib/sphinx',
511) {}
I have used "FEATURES=-sandbox" and I've added addpredict and addread
in
python_prepare_all() {
addpredict "/var/tmp/portage/dev-python/${P}/work"
addread "/var/tmp/portage/dev-python/${P}/work"
distutils-r1_python_prepare_all
}
but it still raises a Sandbox Violation.
What can I do about this?
How can I debug this.
How to stop 'setuptools' to check for a Sandbox Violation,
particularly as /var/tmp/portage/dev-python/imapclient-1.1.0/work/...
isn't critical.
Many thanks for any hints,
Helmut
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2017-12-06 14:08 99% [gentoo-user] Sandbox violations when installing a Python package Helmut Jarausch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox