Summary: | 1.2 --> 1.4 Update step2 dies | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joe Kallar (RETIRED) <blademan> |
Component: | Current packages | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | rajiv |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joe Kallar (RETIRED)
2002-11-05 15:43:30 UTC
emerge rsync and try it again. Tried emerge (r)sync and emerge portage and then the step2 script already. I also tried emerge system, and did notice that gcc was last to be emerged on emerge system, whereas the script wanted to run emerge gcc earlier. Still no luck, emerge system merged everything OK, except gcc. Emerged portage and binutils, but it seems the script emerges them again anyway. with the same error as below but the scripts ends: emerge gcc binutils FAILED. /var/log/emerge.log says: Started emerge on: Nov 06, 2002 *** emerge portage >>> emerge (1 of 1) sys-apps/portage-2.0.43 to / >>> AUTOCLEAN: sys-apps/portage --- AUTOCLEAN: Nothing unmerged. ::: completed emerge (1 of 1) sys-apps/portage-2.0.43 to / *** exiting successfully. Started emerge on: Nov 06, 2002 *** emerge gcc binutils >>> emerge (1 of 2) sys-devel/gcc-3.2-r1 to / Honestly, Don't bother to try and update from 1.2 -> 1.4, its _really_ not worth it from experience Redownload the scripts. I made a change to them for portage-2.0.43 changes. Lemme know how that goes. Sorry, after reading Gerk's comments here and in the PPC forum, I blew away the 1.2 and I'm setting up a 1.4rc1 PPC stage 3. :( I just did find that iptables dies similarly, but I'll post another bug for that. should we add something to the 1.2->1.4 update doc that says it is not for ppc ? grrrr. |