Summary: | Portage 2.2_r16 Doesn't Handle Permissions Well | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Matt <matt.palermo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 216231 |
Description
Matt
2008-11-25 12:58:46 UTC
The directory that is referenced by PORTAGE_TMPDIR is expected to be world writable (with sticky bit set). This should fix it: chmod 1777 /usr/portage/local I'll fix portage to raise a PermissionDenied exception in the case that you've triggered, which will cause it to bail out with a simple 'Permission Denied: /usr/portage/local' message, instead of showing a big traceback. (In reply to comment #1) > The directory that is referenced by PORTAGE_TMPDIR is expected to be world > writable (with sticky bit set). This should fix it: > > chmod 1777 /usr/portage/local > /me shakes his head. Yes. It *IS* supposed to be, isn't it... I changed the permissions and it works as it should. > I'll fix portage to raise a PermissionDenied exception in the case that you've > triggered, which will cause it to bail out with a simple 'Permission Denied: > /usr/portage/local' message, instead of showing a big traceback. > Thank you! Man, I love FOSS... :-) M. This is fixed in 2.1.6_rc2. |