From: "malary" <malary@malary.hu>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] problem re ebuilds
Date: Wed, 30 Aug 2006 10:08:22 +0200 [thread overview]
Message-ID: <001001c6cc0b$77e4fcc0$0200a8c0@malary> (raw)
In-Reply-To: 20060830073609.59595.qmail@web35214.mail.mud.yahoo.com
Hali!
Try --update instead of update
# emerge --update portage
And the kernel source build name is gentoo-sources
# emerge gentoo-sources
malary
http://malary.hu
----- Original Message -----
From: "Stephen Liu" <satimis@yahoo.com>
To: <gentoo-user@lists.gentoo.org>
Sent: Wednesday, August 30, 2006 9:36 AM
Subject: [gentoo-user] problem re ebuilds
> Hi folks,
>
> Installing Gentoo amd64
> Guide:- Gentoo Linux AMD64 Handbook
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml
>
>
> On running;
> # emerge --sync --quiet
>
> following warning popup:
> * An update to portage is available. It is highly recommended
> * that your update portage now, before any other packages are updated
> * please do so and then update All your configuration files
> * end *
>
>
> Ran;
> # emerge update portage
> Calculating dependencies
> emerge: there are no ebuilds to satify "update"
> * end *
>
> I left it aside and continued to;
> Code Listing 22: installing a kernel source
> # USE="-doc symlink" emerge gentoo-sources
>
> following warning popup;
> Calculating denpendencies
> emerge: there are no ebuilds to satisfy "gentoo-source"
> * end *
>
> Please advise how to solve these problems. How to update other
> packages? What are those packages?
>
> TIA
>
> B.R.
> SL
>
> --
> gentoo-user@gentoo.org mailing list
>
>
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-08-30 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 7:36 [gentoo-user] problem re ebuilds Stephen Liu
2006-08-30 7:51 ` Neil Bothwick
2006-08-30 7:54 ` Uwe Thiem
2006-08-30 7:57 ` Daniel Huckstep
2006-08-30 8:08 ` malary [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='001001c6cc0b$77e4fcc0$0200a8c0@malary' \
--to=malary@malary.hu \
--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