From: "James Ausmus" <james.ausmus@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerge error
Date: Wed, 23 Jan 2008 08:13:56 -0800 [thread overview]
Message-ID: <b79f23070801230813k1b75ee13tb74e8278b1dd8fe8@mail.gmail.com> (raw)
In-Reply-To: <loom.20080123T154802-683@post.gmane.org>
On Jan 23, 2008 8:03 AM, James <wireless@tampabay.rr.com> wrote:
> KH <gentoo-user <at> konstantinhansen.de> writes:
>
>
> > James Ausmus wrote:
>
> > > 1. Check your disk space, make sure it's not full
>
> Not a problem...
>
> > > 2. As root, do a chown -R portage:portage /var/cache/edb
>
> > add the -c to chown
> > -c, --changes
> > like verbose but report only when a change is made
>
>
> Many of the files were owned by root:portage
>
> Now they are owned by portage:portage, but that did not
> fix the error:
<snip>
OK, try doing:
emerge --metadata
Also, have you done a emerge --sync since this started?
Sounds like it might just be a cache corruption - if the cache was
corrupted during the rsync process in an emerge--sync, then just doing
a emerge --metadata won't help, but if was just corrupted on disk (in
the /var/cache/edb dir), then a emerge --metadata might do it.
HTH-
James
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-23 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 3:08 [gentoo-user] emerge error James
2008-01-23 5:58 ` James Ausmus
2008-01-23 7:41 ` KH
2008-01-23 16:03 ` [gentoo-user] " James
2008-01-23 16:13 ` James Ausmus [this message]
2008-01-23 16:29 ` James
2008-01-23 16:39 ` James
2008-01-23 16:49 ` Neil Bothwick
2008-01-23 18:33 ` James
2008-01-23 19:37 ` Neil Bothwick
2008-01-23 20:08 ` James
2008-01-23 23:32 ` Neil Bothwick
2008-01-24 3:33 ` Hal Martin
2008-01-24 13:46 ` James
2008-01-24 20:07 ` Neil Bothwick
2008-01-25 1:34 ` James
2008-01-24 5:12 ` Joseph
2008-01-23 16:31 ` Dale
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=b79f23070801230813k1b75ee13tb74e8278b1dd8fe8@mail.gmail.com \
--to=james.ausmus@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