public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Regenerate portage cache from scratch following a big toe crash?
Date: Wed, 18 Aug 2010 10:12:41 -0700	[thread overview]
Message-ID: <AANLkTikSnDuayjUAbGgrfWrjcx66ceJ3UPDHQQ1Cq48c@mail.gmail.com> (raw)
In-Reply-To: <4C6B5ECD.3080801@gmail.com>

On Tue, Aug 17, 2010 at 9:17 PM, Dale <rdalek1967@gmail.com> wrote:
> Mark Knecht wrote:
>>
>> OK, this is too funny. I'm sitting here in the dark browsing around on
>> my home machine while I'm doing an eix-sync. I have my legs crossed,
>> sitting in my chair that swivels, and guess what...my big toe is at
>> __exactly__ the height of the main power button on my APC UPS, and
>> darn if I don't hit it and power is gone!
>>
>> The machine booted and came back up with no obvious problems but when
>> I tried to continue with the eix-sync I get some pretty messed up
>> messages, ala:
>>
>> Can't read cache file
>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success
>>      Reading category 146|154 ( 94%): x11-libs ..
>> Can't read cache file
>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success
>>      Reading category 146|154 ( 94%): x11-libs ..
>> Can't read cache file
>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success
>>      Reading category 146|154 ( 94%): x11-libs ..
>> Can't read cache file
>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success
>>      Reading category 146|154 ( 94%): x11-libs ..
>> Can't read cache file
>> /usr/portage/metadata/cache/x11-libs/pixman-0.18.4: Success
>>      Reading category 154|154 (100%) Finished
>>
>> I tried removing the timestamp file to get it to sync again but that
>> didn't fix it.
>>
>> How does a big-toe guy regenerate the database emerge --sync normally
>> keeps for my machine?
>>
>> Too funny! (Hey - at least I provided a laugh I hope!) :-)))
>>
>> - Mark
>>
>>
>
> I think this will help:
>
> emerge-webrsync
>
> That should download the complete tree.  It will be a pretty good size file
> tho just in case you have dial-up or some other slow connection.
>
> Dale
>
> :-)  :-)
>
> P. S.  Careful with the toe next time.  lol

Thanks Dale, and to Andrea also.

On my machine I'm not finding a man page on emerge-webrsync so I'm a
bit hesitant to run it until I find maybe some information on line.

Andrea's emerge --metadata command is one thing I thought about last
night, along with maybe --regen, but decided it wasn't worth messing
things up. I think maybe the removal of eix completely, then removal
of the cache database, and then re-emerging eix and starting clean
with that program might be the safest first step, assuming that I
don't find a problem with emerge itself this evening.

Thanks for the ideas.

Cheers,
Mark



  reply	other threads:[~2010-08-18 17:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  4:04 [gentoo-user] Regenerate portage cache from scratch following a big toe crash? Mark Knecht
2010-08-18  4:17 ` Dale
2010-08-18 17:12   ` Mark Knecht [this message]
2010-08-18 18:16     ` Dale
2010-08-18  7:01 ` Andrea Conti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikSnDuayjUAbGgrfWrjcx66ceJ3UPDHQQ1Cq48c@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox