Summary: | broken sandbox support after upgrade from binary package | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | infobox.oleg |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | sandbox, steven |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge log displaying errors |
Description
infobox.oleg
2009-02-21 19:27:16 UTC
Created attachment 182755 [details]
emerge log displaying errors
Here is an error log after my system got broken. Unfortunately I don't have the original log from emerge, which messed the system and I'm not willing to break the production OS again :-)
Where did you get the sandbox binpkg which triggered this? Do you have a build log from when it was built? (In reply to comment #2) > Where did you get the sandbox binpkg which triggered this? Do you have a build > log from when it was built? > I've built binpkg using quickpkg on the same machine. I don't have build log, but sandbox 1.3.5 was working just fine after emerge from source. There's not much we can do without more info if it's not reproducible. Just for anyone else who finds this bug later... Sandbox broke on me when I merged it from a binary package as well. The solution provided by the original reporter ('USE=-sandbox emerge sandbox') didn't solve the problem for me, but doing 'emerge -C sandbox; emerge sandbox' corrected the problem. Oh, also, I am pretty sure this bug I just submitted (277902) is the cause for this bug (259837): http://bugs.gentoo.org/show_bug.cgi?id=277902 |