| 1 |
On 26-08-2009 18:49:01 -0500, Jeremy Olexa wrote: |
| 2 |
> > I see the same thing here on x86-macos. It seems that after upgrading |
| 3 |
> > portage to 2.2.00.14160 PORTAGE_ROOT_USER is set to root. Haven't had |
| 4 |
> > time yet to see what exactly is going on. |
| 5 |
> > |
| 6 |
> Ouch, I've masked this for now. Sorry for the trouble. Further bug |
| 7 |
> fixing can take place on https://bugs.gentoo.org/282854 |
| 8 |
|
| 9 |
to recover from this, simply do this: |
| 10 |
|
| 11 |
- edit $EPREFIX/etc/make.globals |
| 12 |
ensure PORTAGE_ROOT_USER is set to the correct value |
| 13 |
- edit $EPREFIX/usr/lib/portage/pym/portage/const_autotool.py |
| 14 |
check and fix the values of portagegroup, portageuser, rootuser, |
| 15 |
rootuid and rootgid |
| 16 |
|
| 17 |
after that your portage should be willing to operate again |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Fabian Groffen |
| 22 |
Gentoo on a different level |
Archives