If sys-auth/pambase cannot parse /etc/make.conf, it errors: >>> Compiling source in /var/tmp/portage/sys-auth/pambase-20080318/work/pambase-20080318 ... [Errno 13] Permission denied: '/etc/make.conf.private' in /etc/make.conf [Errno 13] Permission denied: '/etc/make.conf.private' in /etc/make.conf cpp -traditional-cpp -P -include -conf -include basic-conf -DHAVE_CRACKLIB=1 system-auth.in -o system-auth cpp -traditional-cpp -P -include -conf -include basic-conf -DHAVE_CRACKLIB=1 system-login.in -o system-login <command line>:2:<command line>:2: error: -conf: No such file or directory error: -conf: No such file or directory make: *** [system-login] Error 1 make: *** Waiting for unfinished jobs.... make: *** [system-auth] Error 1 In my case, /etc/make.conf sources a /etc/make.conf.private (with authentication information) that is readable only by root.
This is a bogus bug to me. pambase is not sourcing make.conf at all, it's Portage that is trying to, and if you don't let portage access its own configuration file, you are on your own.
The access is being done after dropping to userpriv, and only is a problem with pambase.
Again this is not a problem of pambase, or mine at all. The problem is caused by has_version call, that _requires portage to source make.conf_. Please don't reopen this bug.
