public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Helmut Jarausch <jarausch@skynet.be>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Sandbox violations when installing a Python package
Date: Wed, 06 Dec 2017 15:08:09 +0100	[thread overview]
Message-ID: <53N7YNHP.GHALSUOH.BTKUOC5Z@CYHZP44F.IJFBFASM.NG3EEJV5> (raw)

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

             reply	other threads:[~2017-12-06 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 14:08 Helmut Jarausch [this message]
2017-12-06 14:32 ` [gentoo-user] Sandbox violations when installing a Python package Michael Orlitzky
2017-12-06 16:09   ` Helmut Jarausch
2017-12-06 16:41     ` Michael Orlitzky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53N7YNHP.GHALSUOH.BTKUOC5Z@CYHZP44F.IJFBFASM.NG3EEJV5 \
    --to=jarausch@skynet.be \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox