| 1 |
luis jure schrieb am 11.10.2008 14:37: |
| 2 |
>> Can you emerge attr, then run lsattr on the files that cannot be |
| 3 |
>> unlinked? I suspect that they might have extended attributes |
| 4 |
>> preventing those file from being deleted. |
| 5 |
> |
| 6 |
> thanks for your answer, that doesn't seem to be the problem, though. |
| 7 |
> i can install everything using install.py directly (not emerging with |
| 8 |
> portage). also, using FEATURES="-sandbox" i can emerge without |
| 9 |
> problems. so this problem seems to be related to the "sandbox", |
| 10 |
> something i never got to understand completely... |
| 11 |
> |
| 12 |
|
| 13 |
Have you updated python recently and did not run python-updater? You can |
| 14 |
also try to re-emerge scons. |
| 15 |
|
| 16 |
|
| 17 |
Sandbox errors are mostly caused when the ebuild tries to access the |
| 18 |
filesystem directly instead of using $WORKDIR. |
| 19 |
|
| 20 |
Maybe some parts of install.py do not honor --instdir="${D}". |
| 21 |
|
| 22 |
Some links: |
| 23 |
http://bugday.gentoo.org/sandbox.html |
| 24 |
http://devmanual.gentoo.org/general-concepts/sandbox/index.html |
| 25 |
|
| 26 |
Regards, |
| 27 |
|
| 28 |
Daniel |
Archives