public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Svoboda <r080@atlas.cz>
To: Gentoo Users <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] update-eix is running "forever"
Date: Tue, 12 Dec 2006 19:43:57 +0100	[thread overview]
Message-ID: <20061212184356.GA12955@ivanka.lan.i2s> (raw)

Hi,

I've been experimenting with overlays a bit. Then I decided to
disable them. Now if I run update-eix it runs like this:

$ update-eix
Reading Portage settings ..
Building database (/var/cache/eix) ..
[0] /usr/portage/ (cache: metadata)
     Reading 100%
[1] /usr/local/portage (cache: none)
     Reading 100%
[2] /usr/portage/local/layman/sunrise (cache: eix* [/usr/portage/local/layman/sunrise])

Here update-eix hangs and sits there doing I don't know what
but while at it, taking 99% of my CPU.

I tried to purge every mention of layman and sunrise out of
/etc and some other places too. No success. What could be
wrong?

Thanks,
Robert

-- 
Robert Svoboda
-- 
gentoo-user@gentoo.org mailing list



                 reply	other threads:[~2006-12-12 18:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20061212184356.GA12955@ivanka.lan.i2s \
    --to=r080@atlas.cz \
    --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