while installing a new system i got reproducible errors when i get to the step "scripts/bootstrap.sh" The fix was to unmask portage-2.0.46-r12 This was reproducible with the gentoo-basic-x86-1.4_rc2.iso boot cd and both the stage1-x86-1.4_rc2.tbz2 from the cd and stage1-x86-1.4_pre20030114.tar.bz2 from http://distro.ibiblio.org/pub/Linux/distributions/gentoo/experimental/x86/stages/ It seems to be related to the "emerge sync" more than the cd/stage1 stuff by unmasking portage-2.0.46-r12 it completes the bootstrap as expected. Reproducible: Always Steps to Reproduce:
I am also having problems with bootstrap.sh from gentoo-basic-x86-1.4.rc2.iso. I am new to gentoo, but have used Linux in various forms since 1995. I am not certain these are related, but they seem to be. Specifically, when bootstrap.sh runs portage.py fails to move the symlinks when completing the build on glibc-2.3.1. The error I get is: --- /lib/ >>> /lib/libc-2.3.1.so >>> /lib/ld-2.3.1.so !!! Failed to move special file: !!! '/var/tmp/portage/glibc-2.3.1-r2/image/lib/ld-linux.so.2' to '/lib/ld-linux.so.2' !!! (32512, '') !!! /lib/ld-linux.so.2 -> ld-2.3.1.so >>> /lib/libBrokenLocale-2.3.1.so >>> /lib/libm-2.3.1.so >>> /lib/libdl-2.3.1.so >>> /lib/libmemusage.so >>> /lib/libcrypt-2.3.1.so >>> /lib/libpthread-0.10.so >>> /lib/libresolv-2.3.1.so >>> /lib/libnss_dns-2.3.1.so >>> /lib/libanl-2.3.1.so >>> /lib/libnss_files-2.3.1.so >>> /lib/librt-2.3.1.so >>> /lib/libSegFault.so >>> /lib/libpcprofile.so >>> /lib/libthread_db-1.0.so >>> /lib/libnss_hesiod-2.3.1.so >>> /lib/libnsl-2.3.1.so >>> /lib/libnss_nis-2.3.1.so >>> /lib/libnss_nisplus-2.3.1.so >>> /lib/libnss_compat-2.3.1.so >>> /lib/libutil-2.3.1.so !!! Failed to move special file: !!! '/var/tmp/portage/glibc-2.3.1-r2/image/lib/libc.so.6' to '/lib/libc.so.6' !!! (32512, '') !!! /lib/libc.so.6 -> libc-2.3.1.so !!! Failed to move special file: !!! '/var/tmp/portage/glibc-2.3.1-r2/image/lib/libBrokenLocale.so.1' to '/lib/libBrokenLocale.so.1' !!! (32512, '') !!! /lib/libBrokenLocale.so.1 -> libBrokenLocale-2.3.1.so !!! Failed to move special file: !!! '/var/tmp/portage/glibc-2.3.1-r2/image/lib/libm.so.6' to '/lib/libm.so.6' !!! (32512, '') !!! /lib/libm.so.6 -> libm-2.3.1.so !!! Failed to move special file: !!! '/var/tmp/portage/glibc-2.3.1-r2/image/lib/libdl.so.2' to '/lib/libdl.so.2' !!! (32512, '') !!! /lib/libdl.so.2 -> libdl-2.3.1.so This continues for every single symlink, but I've stopped for sake of brevity. Is it possible that moving ld-2.3.1.so is making /bin/mv fail -- some sort of dynamic linking error? The error seems to occur when portage.py attempts to make the move around line 1462: a=getstatusoutput("/bin/mv -f "+"'"+src+"' '"+dest+"'") if a[0]!=0: print "!!! Failed to move special file:" print "!!! '"+src+"' to '"+dest+"'" print "!!!",a return None # failure Other notes: This is consistently reproducable. I can move the sym links by hand from a second, non-chrooted session. Once this is done, the chrooted session begins working happily again.
I have the exact problem described by Mr. Stuber, and so do several others. See the forum Installing Gentoo -> Boootstrap.sh problems for more details and discussion. It seems independent of processor, motherboard, chipset, and machine history. It is a complete showstopper for stage 1 installs on virgin systems.
We had a mirror having issues over the last couple days and has since been pulled from circulation. It appears that you have portage-2.0.46-r11 merged (which was unmasked on the mentioned mirror) and you need to rsync and then merge portage-2.0.46-r12. Sorry for the trouble.
Moving these so we can remove the "Install CD" component from "Gentoo Linux". I apologize to everyone for this spam, but according to the bugzilla developers, this is the only reasonable way to do this.
