Failure bootstraping 2005.0 install

Message

Stewie Griffin · Post by **Stewie Griffin** » Thu Mar 31, 2005 11:25 pm

I'm doing a stage2 install with the 2005.0 universal install CD and I left my system bootstrapping and when i got back i saw this on the screen:

Code: Select all

>>> emerge (1 of 2) sys-apps/baselayout-1.9.4-r6 to /
>>> md5 src_uri ;-) sysvinit-2.84.tar.gz
>>> md5 src_uri ;-) rc-scripts-1.4.16.tar.bz2
>>> Unpacking source...
>>> Unpacking sysvinit-2.84.tar.gz to /var/tmp/portage/baselayout-1.9.4-r6/work
>>> Unpacking rc-scripts-1.4.16.tar.bz2 to /var/tmp/portage/baselayout-1.9.4-r6/work
 * Applying rc-scripts-1.4.16-splash.patch ...                                     [ ok ]
 * Applying rc-scripts-1.4.16-livecd.patch ...                                     [ ok ]
 * Applying rc-scripts-1.4.16-livecd-hvc.patch ...

 * Failed Patch: rc-scripts-1.4.16-livecd-hvc.patch !
 *  ( /usr/portage/sys-apps/baselayout/files/rc-scripts-1.4.16-livecd-hvc.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/baselayout-1.9.4-r6/temp/rc-scripts-1.4.16-livecd-hvc.patch-12278.out


!!! ERROR: sys-apps/baselayout-1.9.4-r6 failed.
!!! Function epatch, Line 401, Exitcode 0
!!! Failed Patch: rc-scripts-1.4.16-livecd-hvc.patch!
!!! If you need support, post the topmost build error, NOT this status message.

I'm not sure what the problem is, if anyone can help I'd be very grateful.
Thank you.

taurus · Post by **taurus** » Thu Mar 31, 2005 11:32 pm

Bootstrapping with Stage 2!!! I thought bootstrapping is only for Stage 1... If you start from Stage 2, you just need to run

Code: Select all

emerge --emptytree system

Please look at the Handbook, Chapter 6, Section d.

taurus

Stewie Griffin · Post by **Stewie Griffin** » Thu Mar 31, 2005 11:39 pm

ah, I'm a moron... I just kind of kept going with the install doc. since it didn't explicitly say "this section is for Stage1 users only," but it does say "progressing from stage1 to stage2".... I just assumed it was referring to stage1 of the install, not the stage1 stage.... Do I have to start my install over now? It ran through a good deal of the bootstrap script, but then crapped out at the point that I pasted...

thank you for the fast reply taurus

taurus · Post by **taurus** » Thu Mar 31, 2005 11:45 pm

I would go ahead and start it from the begining so you would have a clean system when you are done, NOT bootstrapping, of course.

Good luck and don't stay up too late!

taurus

hakatak · Post by **hakatak** » Fri Apr 01, 2005 2:29 am

I am having the same problem, and I am starting from Stage 1. Does anyone have any idea what the problem is? Here is the content of the /var/tmp/portage/baselayout-1.9.4-r6/temp/rc-scripts-1.4.16-livecd-hvc.patch-4743.out.

Code: Select all

***** rc-scripts-1.4.16-livecd-hvc.patch *****

===============================================================

PATCH COMMAND:  patch -p0 -g0 < /usr/portage/sys-apps/baselayout/files/rc-scripts-
1.4.16-livecd-hvc.patch

===============================================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- rc-scripts-1.4.16/sbin/livecd-functions.sh.orig    2005-03-22 20:40:25.912265
336 -0600
|+++ rc-scripts-1.4.16/sbin/livecd-functions.sh 2005-03-22 20:43:08.497311240 -060
0
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored
===============================================================

PATCH COMMAND:  patch -p1 -g0 < /usr/portage/sys-apps/baselayout/files/rc-scripts-
1.4.16-livecd-hvc.patch

===============================================================
patching file sbin/livecd-functions.sh
Hunk #1 FAILED at 150.
Hunk #2 succeeded at 184 with fuzz 2 (offset 5 lines).
Hunk #3 FAILED at 198.
2 out of 3 hunks FAILED -- saving rejects to file sbin/livecd-functions.sh.rej
===============================================================

PATCH COMMAND:  patch -p2 -g0 < /usr/portage/sys-apps/baselayout/files/rc-scripts-
1.4.16-livecd-hvc.patch

===============================================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- rc-scripts-1.4.16/sbin/livecd-functions.sh.orig    2005-03-22 20:40:25.912265
336 -0600
|+++ rc-scripts-1.4.16/sbin/livecd-functions.sh 2005-03-22 20:43:08.497311240 -060
0
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored
===============================================================

PATCH COMMAND:  patch -p3 -g0 < /usr/portage/sys-apps/baselayout/files/rc-scripts-
1.4.16-livecd-hvc.patch

===============================================================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- rc-scripts-1.4.16/sbin/livecd-functions.sh.orig    2005-03-22 20:40:25.912265
336 -0600
|+++ rc-scripts-1.4.16/sbin/livecd-functions.sh 2005-03-22 20:43:08.497311240 -060
0
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored
===============================================================

PATCH COMMAND:  patch -p4 -g0 < /usr/portage/sys-apps/baselayout/files/rc-scripts-
1.4.16-livecd-hvc.patch

===============================================================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- rc-scripts-1.4.16/sbin/livecd-functions.sh.orig    2005-03-22 20:40:25.912265
336 -0600
|+++ rc-scripts-1.4.16/sbin/livecd-functions.sh 2005-03-22 20:43:08.497311240 -060
0
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored

Thanks for any help.
Hakatak

zecora · Post by **zecora** » Fri Apr 01, 2005 3:47 am

hakatak,

Hey, so you are doing a stage1, and with which livecd? I am guessing 2005.0 but just tell me anyways. I am also wondering what your make.conf says, can you post that? mabey you should start a new thread as well.

renjuko · Post by **renjuko** » Fri Apr 01, 2005 3:48 am

hakatak i'm running into the same probelms. I just built another system yesterday and didn't have this problem.....makes me wish i kept that one for myself.

Do you have anything special set it your make.conf for CHOST, CFLAGS, etc.? Please post that info as well as the profile and arch that you chose as I believe that comes into play here.

-renjuko

zecora · Post by **zecora** » Fri Apr 01, 2005 3:51 am

For me i am also doing a install on 2 boxes and i am told you cannot have ACCEPT_KEYOWRDS="~x86" you must set it at least for the bootstrap part as ACCEPT_KEYOWRDS="x86" without the ~. So if i am wrong plz someone tell me. Ooo and post your make.conf

edit: Also what you could try is just doing a

Code: Select all

emerge sync && env-update && cd /usr/portage && bootstrap.sh && ACCEPT_KEYWORDS="~x86" emerge -e system

They might have fixed the problem, so mabey just do a emerge sync and redo the bootstrap again.

hakatak · Post by **hakatak** » Fri Apr 01, 2005 4:57 am

Guys,
Thanks for the offer for help. I have cleaned the partitions to try for the third time. I'm thinking that my setting the USE flags prior to bootstrapping might be the problem. I was trying to chain the bootstrap, emerge system, and emerge utilities together so it would run overnight, as I need to get this machine up and running. FYI, I was using CFLAGS= -march=pentium4 -02 -pipe -fomit-frame-pointer and CHOST = i686-pc-linux-gnu. I was using the default profile for the 2.6 kernel, and I wasn't using ~x86. If I restarted the bootstrap it would complete, but then when I emerge -e system, it would fail on the baselayout patching again.
Thanks,
hakatak

DiosT · Post by **DiosT** » Fri Apr 01, 2005 5:59 am

I'm on my second attempt on the gentoo installation this week...

I find that having -very few- USE flags when I first bootstrap -really- helps...

throwing in all the use flags you plan to have in the future ends up causing conflicts with compiling, I think......

I solved my compile issues (or at least, I've gotten 3 times further this time) by reducing my USE flags to basics, bootstraping, then running emerge --emptytree system

Since I don't know gentoo too well, I considered 'minimal' Use flags to be:
USE="gtk gtk2 alsa svga dvd cdr gnome -kde -qt"

but compared to the ~30 i declared at first, this seems to be working a lot better...

oh, and if you have 'Lockfile" issues, do a rm on the file and start the emerge over... that error set me back half a day (as I tried to 'work around' it with --resume / --skipfirst)

volospin · Post by **volospin** » Fri Apr 01, 2005 8:47 am

Bugzilla 87503
http://bugs.gentoo.org/show_bug.cgi?id=87503