1 |
On 25/04/06, lordsauronthegreat@×××××.com <lordsauronthegreat@×××××.com> wrote: |
2 |
> On Monday 24 April 2006 05:01 am, Mick wrote: |
3 |
> > On 23/04/06, Glenn Enright <elinar@×××××××.nz> wrote: |
4 |
> > > Before you do that try emerge metadata or emerge sync |
5 |
> > |
6 |
> > Thanks guys. Emerge metadata creates multiple errors (here's an extract): |
7 |
> > ========================= |
8 |
> > Failed cache update: dev-libs/gmime-2.1.14-r1 "Corruption detected |
9 |
> > when reading key 'gmime-2.1.14-r1': dictionary update sequence element |
10 |
> > #0 has length 1; 2 is required" |
11 |
> > |
12 |
> > Failed cache update: dev-libs/gmime-2.1.9-r3 "Corruption detected when |
13 |
> > reading key 'gmime-2.1.9-r3': dictionary update sequence element #0 |
14 |
> > has length 1; 2 is required" |
15 |
> > ========================= |
16 |
> > |
17 |
> > What now? Shall I delete /var/cache/edb/dep/usr/portage, or some |
18 |
> > other file/directory too? |
19 |
> |
20 |
> Because I said I think it might (major emphasis on might) help is no reason to |
21 |
> start deleting things. DO NOT delete anything without knowing what you're |
22 |
> doing. I just said I thought it might force a rebuild-from-scratch of the |
23 |
> cache, however, I have really no idea. If I built the software, that's |
24 |
> what'd happen, but I didn't so that's where it is. I said it mainly in hopes |
25 |
> that it might help someone more knowledgeable come to a real solution. |
26 |
> |
27 |
> If you still want to delete it, just let me ask you one thing: is this a toy, |
28 |
> or a critical machine? Is this your linux box that works as a learning |
29 |
> environment, or is this thing really part of a system that needs to be on? |
30 |
> If it's just your playground, back everything important (of YOUR data, not OS |
31 |
> settings and crap like that) to another computer and delete to your hearts |
32 |
> content. You will most likely learn something. If you're like me, and |
33 |
> really depend on the system, don't try such a step. |
34 |
|
35 |
I thought of writing this for posterity. The corruption was probably |
36 |
caused because of a couple of forced reboots, when I was trying to |
37 |
send this laptop to sleep and could not bring the screen back to life |
38 |
- what? no backups? tut, tut! |
39 |
|
40 |
I downloaded a fresh portage snapshot and replaced my corrupted |
41 |
portage directory. Before I did that I first moved and then restored |
42 |
my /usr/portage/distfiles to save bandwidth. |
43 |
|
44 |
Everything now works as it should. Thanks for all the replies. |
45 |
-- |
46 |
Regards, |
47 |
Mick |
48 |
|
49 |
-- |
50 |
gentoo-user@g.o mailing list |