emerge -e system fails

[wachtda]

hey folks!

i tried to install a stage1 an got followed error on
emerge -e system

[fangorn]

Did you use the 2005.0 Installation Handbook?

I used it too and it is imho not so lucky in its choice of words.

As I used it there was only the way of a Stage 3 Installation described. There was no hint that you have to bootstrap your system with a Stage 1. don't know if they changed that.

So to say it out loud
Did you bootstrap your system, otherwise all the necessary tools to do a emerge -e world are not present in your system!!! You have to run bootstrap.sh first!

fangorn

[wachtda]

hello fangorn!

i used the latest doc on gentoo.org:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml

and the bootstrap procedure i already did, like described in manual!

_________________
the world is not enough...

[Karsten from Berlin]

Hi again!

1. Please control (from your LiveCD host system), that all directories/mount-points are mounted inside your Gentoo-system.
2. Do a 'emerge --sync && env-update && source /etc/profile && env-update'
3. After that, do a 'emerge -fe system' - drink a cup of coffee in the meantime, it will (only) download all the files that are needed for the 'emerge -e system'
4. After downloading, retry the 'emerge -e system' again
5. If it bails out with an error while compiling, edit the make.conf and change the CHOST-settings I told you back to '-O2 -march=pentium4 -pipe'. Sometimes packages don't want enhanced settings - do __not__ call anything with 'emerge ...', because...
6. ...then you can type 'emerge --resume' - this will not start the 'emerge -e system' from the beginning, but start with the package that didn't compile and bailed out
_________________
Heaven: The police are British, the chefs Italian, the mechanics German, the lovers French and it's organized by the Swiss.
Hell: The police are German, the chefs British, the mechanics French, the lovers Swiss and it's organized by the Italians.

[wachtda]

hi karsten!

thanx for your input...
i now started the emerge -e system again like you described!

now it's time for waiting


report any success, if compiling is finished or
an error occurs...
_________________
the world is not enough...

[rwvo]

I'm afraid Karsten's suggestion is not going to help you. I ran into the very same problem: "emerge -e system" aborted due to a missing file (gzip_1.3.5.org.tar.gz). The package seems to be broken; it only contains the patches, not the original source code. I manually downloaded the missing file from a gentoo mirror, put it in /usr/portage/app-arch/gzip/file (where it belongs), and ran "emerge gzip". No luck: emerge was complaining about a security warning ("there's a file that is not in the Manifest", or something like that). I removed the file again.

This is where I started to do really stupid things. I did "emerge --unmerge gzip", hoping that this would enable me to emerge a newer version. However, this also removes the binaries of gzip that have been installed in stage 1, so now I can't unpack any packages, and basically, I have to start all over again.

In retrospect, I think I should have kept the orig file, and I should have added it and its MD5 sum to the Manifest file (I know: there's a security risk involved!), but that's too late for me now. Maybe it works for you, but don't take my word for it, as I'm an absolute newbie w.r.t. Gentoo.

Question: where should I report the broken package?

Cheers,
rr

[wachtda]

@rwvo
if you have right and the package is broken, i will realy
think about erasing this gentoo garbage from my notebook and go back to debian...

just yesterday i had a problem with a ebuild called groff which was false in the package-db!!!
it seems that gentoo developpers don't realy test their work good enough befor publishing...

_________________
the world is not enough...

[Karsten from Berlin]

Feel free to make a bug-report in Gentoo's bugzilla.
_________________
Heaven: The police are British, the chefs Italian, the mechanics German, the lovers French and it's organized by the Swiss.
Hell: The police are German, the chefs British, the mechanics French, the lovers Swiss and it's organized by the Italians.

[rwvo]

I filed a bugreport in bugzilla indeed.

@wachtda: I can understand your frustration, but the developers are only human. You can't expect them to install a Gentoo system from scratch every time a package gets updated, so every once in a while there will be an error that goes unnoticed. Complaining alone doesn't get the errors fixed; reporting bugs does.

rwvo

[rwvo]

According to bugzilla, the bug has been fixed 20 minutes ago. "emerge --sync" should get you an upgraded portage tree that doesn't have the problem. Before you redo "emerge -e system" I'd check if /usr/portage/apps-arch/gzip/Manifest indeed lists the file that was missing before.

[wachtda]

ok!

emerge -e system finished without any error!


now i can continue with the kernel...
report more later!

_________________
the world is not enough...

[Karak]

Oh thank god this was a known issue that has been fixed... I was banging my head against the wall for the last 4 hours trying to figure out why this wasn't working! Then I thought... Check the forums you idiot! Re-sync'd and running the emerge again... You guys rock!
_________________
It's a shame so many perfectly good idea's have to be discarded simply because they won't work.

[wachtda]

after emerge gentoo-sources i
only have a 2.4 kernel!

why? how can i get a 2.6 kernel?

[EDIT]
i just updatet my profile to 2.6
rm /etc/make.profile
ln -s ../usr/portage/profiles/default-linux/x86/2005.0 /etc/make.profile
[/EDIT]
_________________
the world is not enough...