| 1 |
Mark Knecht wrote: |
| 2 |
> On Tue, Aug 17, 2010 at 9:17 PM, Dale<rdalek1967@×××××.com> wrote: |
| 3 |
> |
| 4 |
>> Mark Knecht wrote: |
| 5 |
>> |
| 6 |
>>> OK, this is too funny. I'm sitting here in the dark browsing around on |
| 7 |
>>> my home machine while I'm doing an eix-sync. I have my legs crossed, |
| 8 |
>>> sitting in my chair that swivels, and guess what...my big toe is at |
| 9 |
>>> __exactly__ the height of the main power button on my APC UPS, and |
| 10 |
>>> darn if I don't hit it and power is gone! |
| 11 |
>>> |
| 12 |
>>> The machine booted and came back up with no obvious problems but when |
| 13 |
>>> I tried to continue with the eix-sync I get some pretty messed up |
| 14 |
>>> messages, ala: |
| 15 |
>>> |
| 16 |
>>> Can't read cache file |
| 17 |
>>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success |
| 18 |
>>> Reading category 146|154 ( 94%): x11-libs .. |
| 19 |
>>> Can't read cache file |
| 20 |
>>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success |
| 21 |
>>> Reading category 146|154 ( 94%): x11-libs .. |
| 22 |
>>> Can't read cache file |
| 23 |
>>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success |
| 24 |
>>> Reading category 146|154 ( 94%): x11-libs .. |
| 25 |
>>> Can't read cache file |
| 26 |
>>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success |
| 27 |
>>> Reading category 146|154 ( 94%): x11-libs .. |
| 28 |
>>> Can't read cache file |
| 29 |
>>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success |
| 30 |
>>> Reading category 154|154 (100%) Finished |
| 31 |
>>> |
| 32 |
>>> I tried removing the timestamp file to get it to sync again but that |
| 33 |
>>> didn't fix it. |
| 34 |
>>> |
| 35 |
>>> How does a big-toe guy regenerate the database emerge --sync normally |
| 36 |
>>> keeps for my machine? |
| 37 |
>>> |
| 38 |
>>> Too funny! (Hey - at least I provided a laugh I hope!) :-))) |
| 39 |
>>> |
| 40 |
>>> - Mark |
| 41 |
>>> |
| 42 |
>>> |
| 43 |
>>> |
| 44 |
>> I think this will help: |
| 45 |
>> |
| 46 |
>> emerge-webrsync |
| 47 |
>> |
| 48 |
>> That should download the complete tree. It will be a pretty good size file |
| 49 |
>> tho just in case you have dial-up or some other slow connection. |
| 50 |
>> |
| 51 |
>> Dale |
| 52 |
>> |
| 53 |
>> :-) :-) |
| 54 |
>> |
| 55 |
>> P. S. Careful with the toe next time. lol |
| 56 |
>> |
| 57 |
> Thanks Dale, and to Andrea also. |
| 58 |
> |
| 59 |
> On my machine I'm not finding a man page on emerge-webrsync so I'm a |
| 60 |
> bit hesitant to run it until I find maybe some information on line. |
| 61 |
> |
| 62 |
> Andrea's emerge --metadata command is one thing I thought about last |
| 63 |
> night, along with maybe --regen, but decided it wasn't worth messing |
| 64 |
> things up. I think maybe the removal of eix completely, then removal |
| 65 |
> of the cache database, and then re-emerging eix and starting clean |
| 66 |
> with that program might be the safest first step, assuming that I |
| 67 |
> don't find a problem with emerge itself this evening. |
| 68 |
> |
| 69 |
> Thanks for the ideas. |
| 70 |
> |
| 71 |
> Cheers, |
| 72 |
> Mark |
| 73 |
> |
| 74 |
|
| 75 |
What you described above is what emerge-webrsync does. Remember during |
| 76 |
the install when you downloaded a "snapshot" of the tree? That is |
| 77 |
basically what that does. It replaces the whole tree. Since you don't |
| 78 |
know what is corrupt, that is what I would do anyway. When you run a |
| 79 |
regular sync, it just replaces the files that have been updated or |
| 80 |
changed in some way. |
| 81 |
|
| 82 |
Actually, I would rm everything except distfiles and then sync. That |
| 83 |
would do the same thing but then I know for sure anything corrupt is |
| 84 |
gone for sure and I have a fresh start. |
| 85 |
|
| 86 |
Your mileage may vary tho. ;-) |
| 87 |
|
| 88 |
Dale |
| 89 |
|
| 90 |
:-) :-) |
Archives