Summary: | Portage 2.0.51.22-r1 with ccache and userpriv set checks CCACHE_DIR permissions incorrectly | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jeremy Barton <sixteen-gentoo> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | vdaghan |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 108082 | ||
Attachments: | patch of the /usr/lib/portage/pym/portage.py |
Description
Jeremy Barton
2005-07-15 09:21:00 UTC
Created attachment 65095 [details, diff]
patch of the /usr/lib/portage/pym/portage.py
Looks good to me, if portage's GID is not equal to the UID then all kinds of permission changes get triggers, even through they aren't needed. A quick check shows stable could use it. *** Bug 104392 has been marked as a duplicate of this bug. *** Fixed in 2.0.53_rc3 |