bootstrap log

update.log (text/plain), 19.90 KB, created by Kevin Morgan on 2010-02-10 03:55:32 UTC

 [32;01m*[0m System has been bootstrapped already!
 [32;01m*[0m If you re-bootstrap the system, you must complete the entire bootstrap process
 [32;01m*[0m otherwise you will have a broken system.
 [32;01m*[0m Press enter to continue or CTRL+C to abort ...

[32;01mGentoo Linux; [34;01mhttp://www.gentoo.org/[0m
Copyright 1999-2009 Gentoo Foundation; Distributed under the GPLv2
Starting Bootstrap of base system ...
-------------------------------------------------------------------------------
  [[ (0/3) Locating packages ]]
 [32;01m*[0m Using baselayout : sys-apps/baselayout
 [32;01m*[0m Using portage    : virtual/portage
 [32;01m*[0m Using os-headers : >=sys-kernel/linux-headers-2.6.27-r2
 [32;01m*[0m Using binutils   : sys-devel/binutils
 [32;01m*[0m Using gcc        : sys-devel/gcc
 [32;01m*[0m Using gettext    : gettext
 [32;01m*[0m Using libc       : virtual/libc
 [32;01m*[0m Using texinfo    : sys-apps/texinfo
 [32;01m*[0m Using zlib       : sys-libs/zlib
 [32;01m*[0m Using ncurses    : sys-libs/ncurses
-------------------------------------------------------------------------------
  [[ (1/3) Configuring environment ]]
 [32;01m*[0m GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
 [32;01m*[0m PORTDIR="/usr/portage"
 [32;01m*[0m DISTDIR="/usr/portage/distfiles"
 [32;01m*[0m PKGDIR="/usr/portage/packages"
 [32;01m*[0m PORTAGE_TMPDIR="/var/tmp"
 [32;01m*[0m CFLAGS="-O2 -pipe"
 [32;01m*[0m CHOST="x86_64-pc-linux-gnu"
 [32;01m*[0m CXXFLAGS="-O2 -pipe"
 [32;01m*[0m ACCEPT_KEYWORDS="amd64"
 [32;01m*[0m FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
 [32;01m*[0m STAGE1_USE="multilib nptl nptlonly unicode"
-------------------------------------------------------------------------------
  [[ (2/3) Updating portage ]]


Performing Global Updates: /usr/portage/profiles/updates/1Q-2010
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  #='/var/db update'  @='/var/db move'
  s='/var/db SLOT move'  %='binary move'  S='binary SLOT move'
  p='update /etc/portage/package.*'
...............................
!!! CONFIG_PROTECT is empty

Calculating dependencies   ... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-apps/portage-2.1.7.16
 * portage-2.1.7.16.patch.bz2 RMD160 SHA1 SHA256 size ;-) ...            [ ok ]
 * portage-2.1.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                 [ ok ]
 * checking ebuild checksums ;-) ...                                     [ ok ]
 * checking auxfile checksums ;-) ...                                    [ ok ]
 * checking miscfile checksums ;-) ...                                   [ ok ]
>>> Unpacking source...
>>> Unpacking portage-2.1.7.16.patch.bz2 to /var/tmp/portage/sys-apps/portage-2.1.7.16/work
>>> Unpacking portage-2.1.7.tar.bz2 to /var/tmp/portage/sys-apps/portage-2.1.7.16/work
>>> Source unpacked in /var/tmp/portage/sys-apps/portage-2.1.7.16/work
>>> Preparing source in /var/tmp/portage/sys-apps/portage-2.1.7.16/work/portage-2.1.7 ...
 [32;01m*[0m Applying portage-2.1.7.16.patch ...
[A[72C  [34;01m[ [32;01mok[34;01m ][0m
 [32;01m*[0m Setting portage.VERSION to 2.1.7.16 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-apps/portage-2.1.7.16/work/portage-2.1.7 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-apps/portage-2.1.7.16/work/portage-2.1.7 ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-apps/portage-2.1.7.16

>>> Install portage-2.1.7.16 into /var/tmp/portage/sys-apps/portage-2.1.7.16/image/ category sys-apps
patching file make.conf
>>> Completed installing portage-2.1.7.16 into /var/tmp/portage/sys-apps/portage-2.1.7.16/image/

strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment
ecompressdir: bzip2 -9 /usr/share/man

>>> Installing (1 of 1) sys-apps/portage-2.1.7.16
 [32;01m*[0m Compilation and optimization of Python modules for Python 2.6 ...
[A[72C  [34;01m[ [32;01mok[34;01m ][0m
 [32;01m*[0m 
 [32;01m*[0m For help with using portage please consult the Gentoo Handbook
 [32;01m*[0m at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3
 [32;01m*[0m 
>>> Auto-cleaning packages...

 app-admin/eselect-python
    selected: 20090824 
   protected: 20091230 
     omitted: none 

 app-admin/perl-cleaner
    selected: 1.05 
   protected: 1.04.3 
     omitted: none 

 app-arch/bzip2
    selected: 1.0.5-r1 
   protected: 1.0.5 
     omitted: none 

 app-arch/cpio
    selected: 2.9-r2 
   protected: 2.9-r1 
     omitted: none 

 app-misc/ca-certificates
    selected: 20090709 
   protected: 20070303-r1 
     omitted: none 

 app-misc/pax-utils
    selected: 0.1.19 
   protected: 0.2 
     omitted: none 

 app-shells/bash
    selected: 4.0_p35 
   protected: 3.2_p17-r1 
     omitted: none 

 dev-lang/perl
    selected: 5.8.8-r8 
   protected: 5.8.8-r5 
     omitted: none 

 dev-libs/libffi
    selected: 3.0.8 
   protected: 3.0.9 
     omitted: none 

 dev-libs/libxml2
    selected: 2.7.3-r2 
   protected: 2.6.30-r1 
     omitted: none 

 dev-libs/mpfr
    selected: 2.4.1_p5 
   protected: 2.2.1_p5 
     omitted: none 

 dev-libs/openssl
    selected: 0.9.8l-r2 
   protected: 0.9.8g-r2 
     omitted: none 

 net-misc/wget
    selected: 1.12 
   protected: 1.10.2 
     omitted: none 

 sys-apps/baselayout
    selected: 1.12.13 
   protected: 1.12.11.1 
     omitted: none 

 sys-apps/module-init-tools
    selected: 3.5 
   protected: 3.4 
     omitted: none 

 sys-apps/sandbox
    selected: 1.6-r2 
   protected: 2.2 
     omitted: none 

 sys-apps/texinfo
    selected: 4.13 
   protected: 4.8-r5 
     omitted: none 

 sys-apps/util-linux
    selected: 2.16.1 
   protected: 2.13.1.1 
     omitted: none 

 sys-apps/which
    selected: 2.20 
   protected: 2.16 
     omitted: none 

 sys-devel/autoconf
    selected: 2.63-r1 
   protected: 2.61-r1 
     omitted: none 

 sys-devel/binutils
    selected: 2.18-r3 
   protected: 2.18-r1 
     omitted: none 

 sys-devel/gcc-config
    selected: 1.4.1 
   protected: 1.4.0-r4 
     omitted: none 

 sys-devel/libperl
    selected: 5.8.8-r2 
   protected: 5.8.8-r1 
     omitted: none 

 sys-fs/udev
    selected: 146-r1 
   protected: 115-r1 
     omitted: none 

 sys-kernel/linux-headers
    selected: 2.6.27-r2 
   protected: 2.6.23-r3 
     omitted: none 

 sys-libs/cracklib
    selected: 2.8.13-r1 
   protected: 2.8.10 
     omitted: none 

 sys-libs/glibc
    selected: 2.10.1-r1 
   protected: 2.6.1 
     omitted: none 

 sys-libs/readline
    selected: 6.0_p4 
   protected: 5.2_p7 
     omitted: none 

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Unmerging app-admin/eselect-python-20090824...
>>> Unmerging app-admin/perl-cleaner-1.05...
>>> Unmerging app-arch/bzip2-1.0.5-r1...
>>> Unmerging app-arch/cpio-2.9-r2...
>>> Unmerging app-misc/ca-certificates-20090709...
>>> Unmerging app-misc/pax-utils-0.1.19...
>>> Unmerging app-shells/bash-4.0_p35...
>>> Unmerging dev-lang/perl-5.8.8-r8...
 [33;01m*[0m Removing dead symlink /usr/bin/enc2xs
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/enc2xs.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/piconv
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/piconv.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/pod2usage
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/pod2usage.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/podchecker
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/podchecker.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/podselect
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/podselect.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/instmodsh
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/instmodsh.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/prove
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/prove.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/cpan
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/cpan.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/pod2man
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/pod2man.1.bz2
 [33;01m*[0m Removing dead symlink /usr/bin/pod2text
 [33;01m*[0m Removing dead symlink /usr/share/man/man1/pod2text.1.bz2
>>> Unmerging dev-libs/libffi-3.0.8...
>>> Unmerging dev-libs/libxml2-2.7.3-r2...
 [32;01m*[0m [1;34m<<< /usr/lib64/python2.6/site-packages/libxml2.py[co][0m
 [32;01m*[0m [1;34m<<< /usr/lib64/python2.6/site-packages/drv_libxml2.py[co][0m
>>> Unmerging dev-libs/mpfr-2.4.1_p5...
>>> Unmerging dev-libs/openssl-0.9.8l-r2...
>>> Unmerging net-misc/wget-1.12...
>>> Unmerging sys-apps/baselayout-1.12.13...
>>> Unmerging sys-apps/module-init-tools-3.5...
>>> Unmerging sys-apps/sandbox-1.6-r2...
>>> Unmerging sys-apps/texinfo-4.13...
>>> Unmerging sys-apps/util-linux-2.16.1...
>>> Unmerging sys-apps/which-2.20...
>>> Unmerging sys-devel/autoconf-2.63-r1...
>>> Unmerging sys-devel/binutils-2.18-r3...
 [32;01m*[0m Switching to x86_64-pc-linux-gnu-2.18 ...
[A[72C  [34;01m[ [32;01mok[34;01m ][0m
>>> Regenerating /etc/ld.so.cache...

 [33;01m*[0m Please remember to run:

 [33;01m*[0m   # source /etc/profile

>>> Unmerging sys-devel/gcc-config-1.4.1...
>>> Unmerging sys-devel/libperl-5.8.8-r2...
>>> Unmerging sys-fs/udev-146-r1...
>>> Unmerging sys-kernel/linux-headers-2.6.27-r2...
>>> Unmerging sys-libs/cracklib-2.8.13-r1...
>>> Unmerging sys-libs/glibc-2.10.1-r1...
[Errno 2] No such file or directory:
   /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
!!! FAILED postrm: 1
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * The 'postrm' phase of the 'sys-libs/glibc-2.10.1-r1' package has failed
 * with exit value 1.
 * 
 * The problem occurred while executing the ebuild file named
 * 'glibc-2.10.1-r1.ebuild' located in the '/var/db/pkg/sys-
 * libs/glibc-2.10.1-r1' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 * 
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.
>>> Unmerging sys-libs/readline-6.0_p4...
!!! Error extracting saved environment: '/var/db/pkg/sys-libs/readline-6.0_p4/environment.bz2'
[Errno 2] No such file or directory:
   /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" prerm
!!! FAILED prerm: 1
!!! Error extracting saved environment: '/var/db/pkg/sys-libs/readline-6.0_p4/environment.bz2'
 * The ebuild phase 'prerm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
[Errno 2] No such file or directory:
   /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
!!! FAILED postrm: 1
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * The 'postrm' phase of the 'sys-libs/readline-6.0_p4' package has failed
 * with exit value 1.
 * 
 * The problem occurred while executing the ebuild file named
 * 'readline-6.0_p4.ebuild' located in the '/var/db/pkg/sys-
 * libs/readline-6.0_p4' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 * 
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.

 * Messages for package dev-lang/perl-5.8.8-r8:
 * Removing dead symlink /usr/bin/enc2xs
 * Removing dead symlink /usr/share/man/man1/enc2xs.1.bz2
 * Removing dead symlink /usr/bin/piconv
 * Removing dead symlink /usr/share/man/man1/piconv.1.bz2
 * Removing dead symlink /usr/bin/pod2usage
 * Removing dead symlink /usr/share/man/man1/pod2usage.1.bz2
 * Removing dead symlink /usr/bin/podchecker
 * Removing dead symlink /usr/share/man/man1/podchecker.1.bz2
 * Removing dead symlink /usr/bin/podselect
 * Removing dead symlink /usr/share/man/man1/podselect.1.bz2
 * Removing dead symlink /usr/bin/instmodsh
 * Removing dead symlink /usr/share/man/man1/instmodsh.1.bz2
 * Removing dead symlink /usr/bin/prove
 * Removing dead symlink /usr/share/man/man1/prove.1.bz2
 * Removing dead symlink /usr/bin/cpan
 * Removing dead symlink /usr/share/man/man1/cpan.1.bz2
 * Removing dead symlink /usr/bin/pod2man
 * Removing dead symlink /usr/share/man/man1/pod2man.1.bz2
 * Removing dead symlink /usr/bin/pod2text
 * Removing dead symlink /usr/share/man/man1/pod2text.1.bz2


 * Messages for package sys-libs/glibc-2.10.1-r1:
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * The 'postrm' phase of the 'sys-libs/glibc-2.10.1-r1' package has failed
 * with exit value 1.
 * 
 * The problem occurred while executing the ebuild file named
 * 'glibc-2.10.1-r1.ebuild' located in the '/var/db/pkg/sys-
 * libs/glibc-2.10.1-r1' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 * 
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.


 * Messages for package sys-libs/readline-6.0_p4:
 * The ebuild phase 'prerm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * The 'postrm' phase of the 'sys-libs/readline-6.0_p4' package has failed
 * with exit value 1.
 * 
 * The problem occurred while executing the ebuild file named
 * 'readline-6.0_p4.ebuild' located in the '/var/db/pkg/sys-
 * libs/readline-6.0_p4' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 * 
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.


 * Regenerating GNU info directory index...
 * Processed 73 info files.
-------------------------------------------------------------------------------
  [[ (3/3) Emerging packages ]]
/usr/portage/scripts/bootstrap.sh: line 345: /bin/env: No such file or directory
/usr/portage/scripts/bootstrap.sh: line 153: /bin/mv: No such file or directory
/usr/portage/scripts/bootstrap.sh: line 156: /bin/cp: No such file or directory