Summary: | portage does not detect insufficient privileges | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michal Suchanek <hramrach> |
Component: | [OLD] Core system | Assignee: | osx porters <osx> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michal Suchanek
2004-09-07 02:52:48 UTC
Are you in portage group? I can't remember whether I added myself to it or not, but if you want to run emerge with user privilege you need to be in portage group. Check the permissions on /usr/lib/portage/pym please. Sidenote, portage has _never_ used sudo calls. It expects to be started w/ the appropriate permissions, and will complain if it lacks them (or if the user isn't part of the portage group)... The effect of portage calling sudo when the emerge command is issued is the result of an alias added to /etc/profile; there is no code in portage to detect the permissions of the calling user. Portage is an administrative tool and thus intened to be used by system administrators. The alias is simply a convienence. I'm marking this bug as invalid because there is nothing broken. Err... alias? care to elaborate, since I've yet to see/here of it? Just curious since the reporter didn't mention anything of it, and I haven't seen it so far in my osx adventures... There is still the messsage the says that your portage is broken, not that your id is invalid. Sorry for the delay. The 2004-07 installer adds "alias emerge='sudo emerge'" to /etc/profile. This is found in the post-install script. My understanding is that the next installer will not need to make any additions to /etc/profile. This is not a bug. Emerge must be run as a superuser, which is done on mac os x via 'sudo'. Adding `alias emerge="sudo emerge"` to /etc/profile may be an acceptable solution to some. Closing out bugs that've been resolved for a while now... |