| 1 |
On Jan 23, 2008 8:03 AM, James <wireless@×××××××××××.com> wrote: |
| 2 |
> KH <gentoo-user <at> konstantinhansen.de> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
> > James Ausmus wrote: |
| 6 |
> |
| 7 |
> > > 1. Check your disk space, make sure it's not full |
| 8 |
> |
| 9 |
> Not a problem... |
| 10 |
> |
| 11 |
> > > 2. As root, do a chown -R portage:portage /var/cache/edb |
| 12 |
> |
| 13 |
> > add the -c to chown |
| 14 |
> > -c, --changes |
| 15 |
> > like verbose but report only when a change is made |
| 16 |
> |
| 17 |
> |
| 18 |
> Many of the files were owned by root:portage |
| 19 |
> |
| 20 |
> Now they are owned by portage:portage, but that did not |
| 21 |
> fix the error: |
| 22 |
|
| 23 |
<snip> |
| 24 |
|
| 25 |
OK, try doing: |
| 26 |
|
| 27 |
emerge --metadata |
| 28 |
|
| 29 |
Also, have you done a emerge --sync since this started? |
| 30 |
|
| 31 |
Sounds like it might just be a cache corruption - if the cache was |
| 32 |
corrupted during the rsync process in an emerge--sync, then just doing |
| 33 |
a emerge --metadata won't help, but if was just corrupted on disk (in |
| 34 |
the /var/cache/edb dir), then a emerge --metadata might do it. |
| 35 |
|
| 36 |
HTH- |
| 37 |
|
| 38 |
James |
| 39 |
-- |
| 40 |
gentoo-user@l.g.o mailing list |
Archives