| Summary: | sandbox access violations regarding portage .pyo files | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Wolfram Schlich (RETIRED) <wschlich> |
| Component: | Sandbox | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | major | CC: | python |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Wolfram Schlich (RETIRED)
2008-08-13 10:21:28 UTC
There's nothing sandbox can do about it. There's got to be some reason that python wants to replace those *.pyo files with new ones. Hmm, Ive seen this before.. When Python runs with the -O option it will re-generate .pyo files for .py files that have changed, replacing old pyo files with new ones. Now, this may have happened because portage got upgraded and the removal of the old version didn't take care of old pyo files (Same thing happened with scons in bug #107013). One thing I would suggest so you get rid of this is to merge something trivial with FEATURES='-sandbox' so .pyo files get generated and everything should be back to normal afterwards. Although it would be real nice if you could provide us with more info on when exactly you started getting this message (after upgrading portage perhaps? or python?) Kind regards, (In reply to comment #2) > Hmm, Ive seen this before.. > > When Python runs with the -O option it will re-generate .pyo files for .py > files that have changed, replacing old pyo files with new ones. Now, this may > have happened because portage got upgraded and the removal of the old version > didn't take care of old pyo files (Same thing happened with scons in bug > #107013). > > One thing I would suggest so you get rid of this is to merge something > trivial with FEATURES='-sandbox' so .pyo files get generated and everything > should be back to normal afterwards. I cannot confirm this -- I've been merging quite some packages with FEATURES="-sandbox -usersandbox" for some time, and it didn't fix it. > Although it would be real nice if you could provide us with more info on when > exactly you started getting this message (after upgrading portage perhaps? or > python?) It's been too long now to reconstruct that, sorry :( It happens on 3 machines for me. If nothing you do ever solves it then it seems like maybe the *.pyo files are constantly being updated over and over again by python. Im going to shoot at the dark here, as I can't reproduce this so I can't test properly. Did you try to remove all pyc, pyo files from /usr/lib/portage/pym and then emerge with -sandbox? Another thing, Have you tried to update portage to see if that helps with this issue? Have you checked that those pyo files actually change in time when using portage? And could you check that running one of those files with python -O directly produces the same result pyo file that the one being generated by emerge? Thanks, meanwhile I've upgraded all those machines to portage-2.2_rc*, no problems anymore :) Please reopen if it happens again. |