Did you untar the stagex tarball before chrooting? This
is the message you get when the initial directories have
not been created. The make.conf is no big deal as it will
create that when it emerges.
Yes, I untarred stage 1. now I have tried:
emerge sync
(get message about
I usually do emerge sync daily, and do a emerge -u --deep
system -p and also world to see what it wants to do. If I
approve I'll emerge it. Doing it frequently keeps the
amount of changes down.
etc-updates are how Gentoo updates config files but gives
you a warning (unlike other distros).
I just started an install with 1.4 rc4 and after the emerge sync step it
says:
* An update to portage is available. It is _highly_ recommended
* that you update portage now, before any other packages are updated.
* Please do so and then update ALL of your configuration files.
I tried:
emerge
On Tue, 2003-06-03 at 19:54, Chris Bare wrote:
I just started an install with 1.4 rc4 and after the emerge sync step it
says:
* An update to portage is available. It is _highly_ recommended
* that you update portage now, before any other packages are updated.
* Please do so and then
I'm getting the same message and have been for a while. I built this
machine a month ago but have been hesitant to do that step.
On a machine I built last week, I believe I did the portage emerge. I
Actually sent the same question to this list. Check the archives for
people's answers.
No, that's what I used. Here's my original question and the only
response I got:
http://marc.theaimsgroup.com/?l=gentoo-userm=105414699615759w=2
http://marc.theaimsgroup.com/?t=10541512311r=1w=2
It didn't say much. I believe that I did:
emerge -p portage
emerge portage
emerge sync
and then
Following on from Chris's question, right now if I do an emerge -Dp
world I get a pretty radical looking list of things that are going to
happen:
Wizard usr # emerge -Dp world
These are the packages that I would merge, in order:
Calculating world dependencies ...done!
[ebuildU ]
It didn't say much. I believe that I did:
emerge -p portage
emerge portage
emerge sync
and then went on, but this is just memory. I was at the same point as
you are right now I think...
Do you think you did an emerge sync first? I tried emerge -p portage as
the first step after chroot
On Tue, 2003-06-03 at 20:18, Chris Bare wrote:
It didn't say much. I believe that I did:
emerge -p portage
emerge portage
emerge sync
and then went on, but this is just memory. I was at the same point as
you are right now I think...
Do you think you did an emerge sync
[EMAIL PROTECTED] ~ $ date ; echo ${Chris Bare}
Wednesday 04 June 2003 12:18 am
cdimage / # emerge -p portage
Note: /etc/make.profile/make.defaults isn't available.
an 'emerge sync' will probably fix this.
!!! No profile directory; system mode unavailable.
# emerge sync
# emerge
Did you untar the stagex tarball before chrooting? This
is the message you get when the initial directories have
not been created. The make.conf is no big deal as it will
create that when it emerges.
On Tue, 3 Jun 2003 23:18:00 -0400 (EDT)
Chris Bare [EMAIL PROTECTED] wrote:
It didn't say
11 matches
Mail list logo
