| Summary: | sandbox violations with python distutils ebuilds | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Michael Hordijk <hoffbrinkle> |
| Component: | Core - Ebuild Support | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | zmedico |
| Priority: | High | ||
| Version: | 2.2 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ebuild environment
emerge --info |
||
Created attachment 170152 [details]
ebuild environment
Created attachment 170154 [details]
emerge --info
Something is causing distutils to misbehave. I've observed similar behavior on a python-2.5 system that had python-2.6 briefly installed and then uninstalled again. The symptom was that all distutils packages failed with a sandbox violation as reported in comment #0. The problem disappeared after I reinstalled my existing version of python-2.5 from a pre-built binary package. Can you still reproduce this bug? I haven't run into this one in a while, so I'm guessing it may be fixed. Haven't really played with Gentoo much in the past year though. |
After upgrading to portage-2.2_r12, (to get python-2.6), I get sandbox violations whenever I try to install distutil based packages. For instance, layman: creating /usr/lib/python2.6/site-packages/layman ACCESS DENIED mkdir: /usr/lib/python2.6/site-packages/layman error: could not create '/usr/lib/python2.6/site-packages/layman': Permission denied * * ERROR: app-portage/layman-1.1.1 failed. * Call stack: * ebuild.sh, line 49: Called src_install * environment, line 2409: Called distutils_src_install * environment, line 687: Called die * The specific snippet of code: * ${python} setup.py install --root="${D}" --no-compile "$@" || die "python setup.py install failed"; * The die message: * python setup.py install failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-portage/layman-1.1.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-portage/layman-1.1.1/temp/environment'. * It appears that ${D} is not correctly set or something. As such, attaching an environment from the above build as well as an emerge --info