Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 30496 - When I try emerge -p system, i get various corrupt ebuilds(varries which one), emerge system never finishes
Summary: When I try emerge -p system, i get various corrupt ebuilds(varries which one)...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Portage team
Depends on:
Reported: 2003-10-06 11:01 UTC by jayson
Modified: 2004-02-25 22:48 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description jayson 2003-10-06 11:01:25 UTC
everything goes fine on the install until i have to do emerge -p system and 
emerge system(stage 2), i tried stage 3 but the kernel would never compile so 
i thought i'd try stage 2. emerge system will never finish, doesnt get past 
the first 5 or so ebuilds.

Reproducible: Always
Steps to Reproduce:
1.emerge -p system
2.emerge system

Actual Results:  
emerge system runs for a while, then it will either just hang, exit to # or 
tell me there is an error(and to report it), also error with eth0, cannot 
write to BAP(does that while downloading ebuilds).it'll be downloading and 
that error message will scroll about 5 times then it will resume(wireless was 
fine with windows)

Expected Results:  
finished emerging ebuilds.

i dont want to go back to windoze :( i just want gentoo to install
Comment 1 SpanKY gentoo-dev 2003-10-06 11:29:11 UTC
what if you `emerge sync` and try again
Comment 2 Martin Holzer (RETIRED) gentoo-dev 2003-10-07 03:18:49 UTC
do you have enough free diskspace and ram ?
do you have activated swap ?
Comment 3 Martin Holzer (RETIRED) gentoo-dev 2003-10-12 16:08:36 UTC
did you try memtest, cpuburn ?
seems to be a hardware issue
Comment 4 Nicholas Jones (RETIRED) gentoo-dev 2003-12-24 12:13:15 UTC
Needed info, too old now.
Comment 5 SpanKY gentoo-dev 2004-02-25 22:48:59 UTC
ended up being a hardware failure (motherboard short)