| Summary: | emerging fluxspace creates a symbolic link into the sandbox | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nadav Samet <thesamet> |
| Component: | New packages | Assignee: | Commonbox Team <commonbox> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Yeah I had an issue with that before. Humor me and test out the 0.4.0_alpha fluxspace ebuild. The error is corrected in that ebuild. I cannot reproduce this at all with either versions. |
I upgraded to python 2.3. Then fluxspace refused to work. It outputs the following: Traceback (most recent call last): File "/usr/bin/fluxspace", line 15, in ? import fluxspace File "/usr/lib/python2.3/site-packages/fluxspace.py", line 4, in ? import _fluxspace ImportError: No module named _fluxspace I re-emerged fluxspace and still got the same error. I've noticed the following weirdness (_fluxspace.so is symlinked into the sandbox): root@nadav / # ls -la /usr/lib/python2.3/site-packages/_fluxspace.so lrwxrwxrwx 1 root root 72 Jan 30 12:48 /usr/lib/python2.3/site-packages/_fluxspace.so -> /var/tmp/portage/fluxspace-0.0.3-r1/image//usr/lib/libfluxspace-0.0.3.so Reproducible: Always Steps to Reproduce: 1. Upgrade python 2. Reemerge fluxspace 3. Examine the above link