| 1 |
I run eix-sync instead. I just ran it with no problems here. |
| 2 |
|
| 3 |
Hope this helps, |
| 4 |
Mark |
| 5 |
|
| 6 |
On 4/23/06, Mick <michaelkintzios@×××××.com> wrote: |
| 7 |
> As it tries to update its cache after an emerge --sync it comes up |
| 8 |
> with a load of errors like so: |
| 9 |
> ====================== |
| 10 |
> Literal data: 5903578 bytes |
| 11 |
> Matched data: 0 bytes |
| 12 |
> File list size: 3297486 |
| 13 |
> Total bytes written: 36921 |
| 14 |
> Total bytes read: 5388275 |
| 15 |
> |
| 16 |
> wrote 36921 bytes read 5388275 bytes 37544.61 bytes/sec |
| 17 |
> total size is 126887824 speedup is 23.39 |
| 18 |
> |
| 19 |
> >>> Updating Portage cache: |
| 20 |
> Failed cache update: app-accessibility/at-poke-0.2.2 "Corruption |
| 21 |
> detected when reading key 'at-poke-0.2.2': dictionary update sequence |
| 22 |
> element #0 has length 1; 2 is required" |
| 23 |
> |
| 24 |
> Failed cache update: app-accessibility/dasher-3.2.18 "Corruption |
| 25 |
> detected when reading key 'dasher-3.2.18': dictionary update sequence |
| 26 |
> element #0 has length 1; 2 is required" |
| 27 |
> ====================== |
| 28 |
> . . . and so on until the end of the packages. |
| 29 |
> |
| 30 |
> I resynced twice, same error. Anyone else had it? |
| 31 |
> -- |
| 32 |
> Regards, |
| 33 |
> Mick |
| 34 |
> |
| 35 |
> -- |
| 36 |
> gentoo-user@g.o mailing list |
| 37 |
> |
| 38 |
> |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-user@g.o mailing list |
Archives