From: Andrea Conti <alyf@alyf.net>
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 09:01:37 +0200 [thread overview]
Message-ID: <4C6B8551.20103@alyf.net> (raw)
In-Reply-To: <AANLkTim3cSnmH4R5yT5uDvYuoRSHAQEOEUeNE5YFV2XL@mail.gmail.com>
Hi,
> 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!
Back in the old days I had a trusty desktop 286 which sat on a piece of
furniture at approximately knee level, with a very prominent "reset"
button on the front panel... need I say more?
> 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
> How does a big-toe guy regenerate the database emerge --sync normally
> keeps for my machine?
First make sure all your filesystems are ok (touch /forcefsck and reboot).
Second, I am not sure whether eix is complaining about the portage tree
metadata (which is rsynced with the rest of the tree and not kept by
emerge, so it shouldn't get corrupted) or its own cache.
You can regenerate the former locally with emerge --metadata; if it
doesn't help (and I don't think it will) I would try deleting the
contents of /var/cache/eix and manually running eix-update.
HTH,
andrea
prev parent reply other threads:[~2010-08-18 7:02 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
2010-08-18 18:16 ` Dale
2010-08-18 7:01 ` Andrea Conti [this message]
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=4C6B8551.20103@alyf.net \
--to=alyf@alyf.net \
--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