From: Michael Sullivan <michael@espersunited.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge running forever
Date: Sun, 11 Jun 2006 10:02:49 -0500 [thread overview]
Message-ID: <1150038169.10761.7.camel@camille.espersunited.com> (raw)
In-Reply-To: <20060611.165357.74743437.Meino.Cramer@gmx.de>
On Sun, 2006-06-11 at 16:53 +0200, Meino Christian Cramer wrote:
> Hi,
>
> I did an
> emerge portage
> and everything runs fine.
>
> Than I did a
> emerge --searchdesc luks
>
> which runs "forever" (I killed that job after waiting for about half
> an hour...)
>
> What is going wrong here? Did I missing something while/after
> updateing portage ???
>
> Thanks a lot for any help in advance !
> mcc
>
Try eix. Much faster.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-11 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 14:53 [gentoo-user] emerge running forever Meino Christian Cramer
2006-06-11 15:02 ` Michael Sullivan [this message]
2006-06-11 15:13 ` Raymond Lewis Rebbeck
2006-06-11 15:16 ` Meino Christian Cramer
2006-06-11 19:12 ` Alexander Skwar
2006-06-11 15:14 ` Till Schwalbe
2006-06-11 15:40 ` Teresa and Dale
2006-06-11 15:52 ` David Morgan
2006-06-11 16:27 ` Teresa and 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=1150038169.10761.7.camel@camille.espersunited.com \
--to=michael@espersunited.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