| 1 |
On Wed, Aug 31, 2011 at 10:10 AM, Space Cake <spacecakex@×××××.com> wrote: |
| 2 |
> On 2011. aug. 31., szerda, 16.02.15 CEST, Michael Mol wrote: |
| 3 |
>> 2011/8/31 Space Cake <spacecakex@×××××.com>: |
| 4 |
>>> Hi, |
| 5 |
>>> |
| 6 |
>>> For a few days my routine upgrades failing at portage with the following |
| 7 |
>>> message. Do you have any idea what does it means? |
| 8 |
>>> |
| 9 |
>>> File |
| 10 |
>>> "/var/tmp/portage/sys-apps/portage-2.1.10.11/image/usr/lib/portage/pym/portage/tests/runTests", |
| 11 |
>>> line 21, in <module> |
| 12 |
>>> os.environ["PORTAGE_GRPNAME"] = grp.getgrgid(os.getgid()).gr_name |
| 13 |
>>> KeyError: 'getgrgid(): gid not found: 0' |
| 14 |
>>> |
| 15 |
>>> I've tried to google this, but nothing has found |
| 16 |
>> |
| 17 |
>> A new portage went stable a few days ago. You might try explicitly |
| 18 |
>> upgrading portage, and then continuing. |
| 19 |
> |
| 20 |
> Yes, this is what I've tried, but it is failed with the message above |
| 21 |
|
| 22 |
By the error, it looks like the code expected to be run as gid 0, but wasn't. |
| 23 |
|
| 24 |
I assume you ran etc-update? |
| 25 |
|
| 26 |
What about a downgrade? Could you downgrade portage to the last stable |
| 27 |
version (not sure what that is), and then upgrade it again? (I'd wait |
| 28 |
for someone else to chime in before you do this. It may be a riskier |
| 29 |
move than is obvious. I'm not sure.) |
| 30 |
|
| 31 |
-- |
| 32 |
:wq |
Archives