Emerge used to use sudo to perform requested operations but now it fails with an error. I am not aware of any setting I changed. Also when it was using sudo it would request the password and succeed on some operations and just fail on others. ie emerge -s would fail The error message when sudo is not used is quite misleading. The stable portage on GNU/Linux/ppc detects it does not have sufficient privileges and says so. To make it clear: i would expect portage to use sudo whenever needed. And I would expect emerge info to work without sudo. $ emerge info !!! Failed to complete portage imports. There are internal modules for !!! portage and failure here indicates that you have a problem with your !!! installation of portage. Please try a rescue portage located in the !!! portage tree under '/usr/portage/sys-apps/portage/files/' (default). !!! There is a README.rescue file that details the steps required to perform !!! a recovery of portage. name 'red' is not defined $ sudo emerge info !!! Relying on the shell to locate gcc, this may break !!! DISTCC, installing gcc-config and setting your current gcc !!! profile will fix this Portage 2.0.51_pre20 (default-macos-10.3, gcc-3.3, libsystem-7.1-r0, 7.5.0 Power Macintosh powerpc) ================================================================= System uname: 7.5.0 Power Macintosh powerpc macos-20040726 distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632) [disabled] ccache version 2.2 [enabled] Autoconf: sys-devel/autoconf-2.57 Automake: sys-devel/automake-1.6.3 Binutils: Headers: Libtools: ACCEPT_KEYWORDS="macos ~macos" AUTOCLEAN="yes" CFLAGS="-O2 -pipe" CHOST="powerpc-apple-darwin" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache collision-protect cvs fixpackages keepwork strict userpriv" GENTOO_MIRRORS="http://gentoo.osuosl.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="macos perl linguas_C linguas_POSIX linguas_en_US linguas_en_US.UTF-8 linguas_cs_CZ linguas_cs_CZ.UTF-8"
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...
