<<[CHROOT]sabayon / # >> eselect profile list
Available profile symlink targets:
[1] default/linux/amd64/10.0 *
[2] default/linux/amd64/10.0/selinux
[3] default/linux/amd64/10.0/desktop
[4] default/linux/amd64/10.0/desktop/gnome
[5] default/linux/amd64/10.0/desktop/kde
[6] default/linux/amd64/10.0/developer
[7] default/linux/amd64/10.0/no-multilib
[8] default/linux/amd64/10.0/server
[9] hardened/linux/amd64
[10] hardened/linux/amd64/selinux
[11] hardened/linux/amd64/no-multilib
[12] hardened/linux/amd64/no-multilib/selinux
<<[CHROOT]sabayon / # >> cat /etc/make.conf
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /etc/make.conf.example for a more detailed example.
CFLAGS="-O2 -pipe -march=nocona"
#CFLAGS="-O2 -pipe -march=native"
CXXFLAGS="${CFLAGS}"
# This should not be changed unless you know exactly what you are doing. You
# should probably be using a different stage, instead.
CHOST="x86_64-pc-linux-gnu"
MAKEOPTS="-j1"
PORTAGE_NICENESS=5
# PLEASE NOTE: this USE statement has customised for use on TAD - Please do NOT use it elsewhere!
USE="xmlreader -mysql -postgres -perl ssl -apache2 -curl -gd -gdbm jpeg -pdflib -png -tiff -freetds -X -gnome -gtk -gtk2 -kde -oss -alsa -qt -truetype -ipv6 -cups -sdl urandom"
APACHE2_MODULES="actions alias auth_basic auth_digest authn_alias authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias"
# This will select the correct version of PECL modules etc
PHP_TARGETS="php5-2"
EMERGE_DEFAULT_OPTS="--autounmask=n"
GENTOO_MIRRORS="ftp://mirror.bytemark.co.uk/gentoo/ http://mirror.bytemark.co.uk/gentoo/ rsync://mirror.bytemark.co.uk/gentoo/ ftp://mirror.qubenet.net/mirror/gentoo/ http://mirror.qubenet.net/mirror/gentoo/ rsync://rsync.mirrorservice.org/www.ibiblio.org/gentoo/ http://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/ ftp://ftp.mirrorservice.org/sites/www.ibiblio.org/gentoo/"
SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage"
<<[CHROOT]sabayon / # >> cp /home/marcusw/savedstuff/etc/locale.gen /etc/
<<[CHROOT]sabayon / # >> locale-gen
* No locales found
<<[CHROOT]sabayon / # >> cp /home/marcusw/savedstuff/etc/localtime /etc/
<<[CHROOT]sabayon / # >> emerge gentoo-sources
* IMPORTANT: 5 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-kernel/gentoo-sources-3.0.6
* linux-3.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* genpatches-3.0-8.base.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* genpatches-3.0-8.extras.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
>>> Preparing to unpack ...
>>> Unpacking source...
>>> Unpacking linux-3.0.tar.bz2 to /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work
>>> Unpacking genpatches-3.0-8.base.tar.bz2 to /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/patches
>>> Unpacking genpatches-3.0-8.extras.tar.bz2 to /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/patches
* Applying 1000_linux-3.0.1.patch (-p0+) ... [ ok ]
* Applying 1001_linux-3.0.2.patch (-p0+) ... [ ok ]
* Applying 1002_linux-3.0.3.patch (-p0+) ... [ ok ]
* Applying 1003_linux-3.0.4.patch (-p0+) ... [ ok ]
* Applying 1004_linux-3.0.5.patch (-p0+) ... [ ok ]
* Applying 1005_linux-3.0.6.patch (-p0+) ... [ ok ]
* Applying 1700_i386-bigsmp-early-lapicid-override.patch (-p0+) ... [ ok ]
* Applying 1800_fix-zcache-build.patch (-p0+) ... [ ok ]
* Applying 2600_Input-ALPS-Move-protocol-information-to-Documentation.patch (-p0+) ... [ ok ]
* Applying 2605_Input-psmouse-Add-PSMOUSE_CMD_RESET_WRAP.patch (-p0+) ... [ ok ]
* Applying 2610_Input-ALPS-Add-protocol-version-field-in-alps_model.patch (-p0+) ... [ ok ]
* Applying 2615_Input-ALPS-Remove-assumptions-about-packet-size.patch (-p0+) ... [ ok ]
* Applying 2620_Input-ALPS-Add-support-for-protocol-versions-3-and-4.patch (-p0+) ... [ ok ]
* Applying 2625_Input-ALPS-Add-documentation-for-protocol-versions-3.patch (-p0+) ... [ ok ]
* Applying 2630_Input-ALPS-Add-semi-MT-support-for-v3-protocol.patch (-p0+) ... [ ok ]
* Applying 2635_Input-ALPS-dump-raw-packet-data.patch (-p0+) ... [ ok ]
* Applying 2900_change-dvb-firmware-url.patch (-p0+) ... [ ok ]
* Applying 4200_fbcondecor-0.9.6.patch (-p0+) ... [ ok ]
>>> Source unpacked in /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work
>>> Preparing source in /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/linux-3.0.6-gentoo ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/linux-3.0.6-gentoo ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/linux-3.0.6-gentoo ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-kernel/gentoo-sources-3.0.6
>>> Install gentoo-sources-3.0.6 into /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/image/ category sys-kernel
>>> Copying sources ...
>>> Completed installing gentoo-sources-3.0.6 into /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/image/
>>> Installing (1 of 1) sys-kernel/gentoo-sources-3.0.6
* If you are upgrading from a previous kernel, you may be interested
* in the following document:
* - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml
* For more info on this patchset, and how to report problems, see:
* http://dev.gentoo.org/~mpagano/genpatches
>>> Recording sys-kernel/gentoo-sources in "world" favorites file...
* Messages for package sys-kernel/gentoo-sources-3.0.6:
* If you are upgrading from a previous kernel, you may be interested
* in the following document:
* - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml
>>> Auto-cleaning packages...
app-admin/eselect
selected: 1.2.15
protected: 1.2.10
omitted: none
app-arch/gzip
selected: 1.4
protected: 1.3.12-r1
omitted: none
app-arch/tar
selected: 1.23-r2
protected: 1.19-r1
omitted: none
app-editors/nano
selected: 2.2.5
protected: 2.0.7
omitted: none
app-misc/ca-certificates
selected: 20110502-r1
protected: 20111025
omitted: none
app-shells/bash
selected: 4.1_p9
protected: 3.2_p33
omitted: none
dev-lang/perl
selected: 5.12.4-r1
protected: 5.12.3-r1
omitted: none
dev-libs/gmp
selected: 5.0.2
protected: 5.0.2_p1
omitted: none
dev-libs/libxml2
selected: 2.7.8-r3
protected: 2.7.8
omitted: none
dev-libs/openssl
selected: 1.0.0e
protected: 0.9.8o
omitted: none
dev-libs/popt
selected: 1.10.7
protected: 1.16-r1
omitted: none
net-misc/curl
selected: 7.21.4
protected: 7.17.1
omitted: none
net-misc/iputils
selected: 20100418-r1
protected: 20071127
omitted: none
net-misc/openssh
selected: 5.8_p1-r1
protected: 4.7_p1-r6
omitted: none
net-misc/wget
selected: 1.12-r3
protected: 1.11.1
omitted: none
perl-core/Scalar-List-Utils
selected: 1.230.0
protected: 1.19
omitted: none
sys-apps/acl
selected: 2.2.51
protected: 2.2.45
omitted: none
sys-apps/attr
selected: 2.4.32
protected: 2.4.46
omitted: none
sys-apps/busybox
selected: 1.19.0
protected: 1.8.2
omitted: none
sys-apps/coreutils
selected: 8.7
protected: 6.10-r2
omitted: none
sys-apps/diffutils
selected: 3.0
protected: 2.8.7-r2
omitted: none
sys-apps/file
selected: 5.07-r3
protected: 5.09
omitted: none
sys-apps/gawk
selected: 3.1.8
protected: 3.1.5-r5
omitted: none
sys-apps/grep
selected: 2.5.4-r1
protected: 2.5.1a-r1
omitted: none
sys-apps/groff
selected: 1.19.2-r1
protected: 1.21
omitted: none
sys-apps/kbd
selected: 1.15.3
protected: 1.13-r1
omitted: none
sys-apps/less
selected: 444
protected: 418
omitted: none
sys-apps/man
selected: 1.6f-r1
protected: 1.6f-r4
omitted: none
sys-apps/portage
selected: 2.1.10.11
protected: 2.1.10.41
omitted: none
sys-apps/sed
selected: 4.2.1
protected: 4.1.5-r1
omitted: none
sys-apps/shadow
selected: 4.1.4.3
protected: 4.0.18.2
omitted: none
sys-apps/texinfo
selected: 4.13
protected: 4.11-r1
omitted: none
sys-apps/util-linux
selected: 2.19.1-r1
protected: 2.13.1.1
omitted: none
sys-devel/gettext
selected: 0.18.1.1-r1
protected: 0.17-r1
omitted: none
sys-devel/make
selected: 3.81
protected: 3.82-r1
omitted: none
sys-fs/e2fsprogs
selected: 1.41.14
protected: 1.40.8
omitted: none
sys-fs/udev
selected: 164-r2
protected: 119
omitted: none
sys-libs/gdbm
selected: 1.8.3-r3
protected: 1.8.3-r4
omitted: none
sys-libs/glibc
selected: 2.13-r4
protected: 2.10.1-r1
omitted: none
sys-libs/ncurses
selected: 5.6-r2
protected: 5.9
omitted: none
sys-libs/pam
selected: 0.99.9.0
protected: 1.1.5
omitted: none
sys-libs/readline
selected: 6.2_p1
protected: 5.2_p12-r1
omitted: none
sys-process/psmisc
selected: 22.14
protected: 22.6
omitted: none
virtual/perl-Digest-MD5
selected: 2.39
protected: 2.36
omitted: none
virtual/perl-Scalar-List-Utils
selected: 1.230.0-r1
protected: 1.19
omitted: none
virtual/perl-libnet
selected: 1.220.0-r1
protected: 1.21
omitted: none
All selected packages: sys-apps/grep-2.5.4-r1 sys-apps/attr-2.4.32 dev-libs/popt-1.10.7 sys-devel/gettext-0.18.1.1-r1 sys-libs/ncurses-5.6-r2 sys-apps/shadow-4.1.4.3 app-arch/tar-1.23-r2 sys-process/psmisc-22.14 dev-lang/perl-5.12.4-r1 virtual/perl-Scalar-List-Utils-1.230.0-r1 sys-apps/coreutils-8.7 virtual/perl-libnet-1.220.0-r1 perl-core/Scalar-List-Utils-1.230.0 sys-apps/kbd-1.15.3 virtual/perl-Digest-MD5-2.39 sys-apps/texinfo-4.13 dev-libs/gmp-5.0.2 sys-apps/groff-1.19.2-r1 net-misc/iputils-20100418-r1 sys-apps/util-linux-2.19.1-r1 sys-libs/glibc-2.13-r4 sys-apps/diffutils-3.0 net-misc/curl-7.21.4 sys-apps/portage-2.1.10.11 sys-libs/gdbm-1.8.3-r3 sys-apps/acl-2.2.51 sys-libs/readline-6.2_p1 dev-libs/libxml2-2.7.8-r3 app-admin/eselect-1.2.15 sys-libs/pam-0.99.9.0 app-misc/ca-certificates-20110502-r1 net-misc/wget-1.12-r3 app-shells/bash-4.1_p9 sys-apps/man-1.6f-r1 sys-devel/make-3.81 sys-apps/gawk-3.1.8 sys-apps/file-5.07-r3 app-arch/gzip-1.4 sys-fs/udev-164-r2 net-misc/openssh-5.8_p1-r1 sys-fs/e2fsprogs-1.41.14 dev-libs/openssl-1.0.0e sys-apps/busybox-1.19.0 sys-apps/sed-4.2.1 app-editors/nano-2.2.5 sys-apps/less-444
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
>>> Unmerging app-admin/eselect-1.2.15...
>>> Unmerging app-arch/gzip-1.4...
>>> Unmerging app-arch/tar-1.23-r2...
>>> Unmerging app-editors/nano-2.2.5...
>>> Unmerging app-misc/ca-certificates-20110502-r1...
>>> Unmerging app-shells/bash-4.1_p9...
>>> Unmerging dev-lang/perl-5.12.4-r1...
* Linking /usr/bin/ptar-1.54-perl-5.12.3 to /usr/bin/ptar (relative)
* Linking /usr/share/man/man1/ptar-1.54-perl-5.12.3.1.bz2 to /usr/share/man/man1/ptar.1.bz2 (relative)
* Linking /usr/bin/ptardiff-1.54-perl-5.12.3 to /usr/bin/ptardiff (relative)
* Linking /usr/share/man/man1/ptardiff-1.54-perl-5.12.3.1.bz2 to /usr/share/man/man1/ptardiff.1.bz2 (relative)
* Linking /usr/bin/shasum-5.47-perl-5.12.3 to /usr/bin/shasum (relative)
* Linking /usr/share/man/man1/shasum-5.47-perl-5.12.3.1.bz2 to /usr/share/man/man1/shasum.1.bz2 (relative)
* Linking /usr/bin/cpan-1.9456-perl-5.12.3 to /usr/bin/cpan (relative)
* Linking /usr/share/man/man1/cpan-1.9456-perl-5.12.3.1.bz2 to /usr/share/man/man1/cpan.1.bz2 (relative)
* Linking /usr/bin/cpanp-0.90-perl-5.12.3 to /usr/bin/cpanp (relative)
* Linking /usr/share/man/man1/cpanp-0.90-perl-5.12.3.1.bz2 to /usr/share/man/man1/cpanp.1.bz2 (relative)
* Linking /usr/bin/cpan2dist-0.90-perl-5.12.3 to /usr/bin/cpan2dist (relative)
* Linking /usr/share/man/man1/cpan2dist-0.90-perl-5.12.3.1.bz2 to /usr/share/man/man1/cpan2dist.1.bz2 (relative)
* Linking /usr/bin/cpanp-run-perl-0.90-perl-5.12.3 to /usr/bin/cpanp-run-perl (relative)
* Linking /usr/bin/enc2xs-2.39-perl-5.12.3 to /usr/bin/enc2xs (relative)
* Linking /usr/share/man/man1/enc2xs-2.39-perl-5.12.3.1.bz2 to /usr/share/man/man1/enc2xs.1.bz2 (relative)
* Linking /usr/bin/piconv-2.39-perl-5.12.3 to /usr/bin/piconv (relative)
* Linking /usr/share/man/man1/piconv-2.39-perl-5.12.3.1.bz2 to /usr/share/man/man1/piconv.1.bz2 (relative)
* Linking /usr/bin/instmodsh-6.56-perl-5.12.3 to /usr/bin/instmodsh (relative)
* Linking /usr/share/man/man1/instmodsh-6.56-perl-5.12.3.1.bz2 to /usr/share/man/man1/instmodsh.1.bz2 (relative)
* Removing dead symlink /usr/bin/xsubpp
* Removing dead symlink /usr/share/man/man1/xsubpp.1.bz2
* Linking /usr/bin/config_data-0.3603-perl-5.12.3 to /usr/bin/config_data (relative)
* Linking /usr/share/man/man1/config_data-0.3603-perl-5.12.3.1.bz2 to /usr/share/man/man1/config_data.1.bz2 (relative)
* Linking /usr/bin/corelist-2.43-perl-5.12.3 to /usr/bin/corelist (relative)
* Linking /usr/share/man/man1/corelist-2.43-perl-5.12.3.1.bz2 to /usr/share/man/man1/corelist.1.bz2 (relative)
* Linking /usr/bin/pod2usage-1.37-perl-5.12.3 to /usr/bin/pod2usage (relative)
* Linking /usr/share/man/man1/pod2usage-1.37-perl-5.12.3.1.bz2 to /usr/share/man/man1/pod2usage.1.bz2 (relative)
* Linking /usr/bin/podchecker-1.37-perl-5.12.3 to /usr/bin/podchecker (relative)
* Linking /usr/share/man/man1/podchecker-1.37-perl-5.12.3.1.bz2 to /usr/share/man/man1/podchecker.1.bz2 (relative)
* Linking /usr/bin/podselect-1.37-perl-5.12.3 to /usr/bin/podselect (relative)
* Linking /usr/share/man/man1/podselect-1.37-perl-5.12.3.1.bz2 to /usr/share/man/man1/podselect.1.bz2 (relative)
* Linking /usr/bin/prove-3.17-perl-5.12.3 to /usr/bin/prove (relative)
* Linking /usr/share/man/man1/prove-3.17-perl-5.12.3.1.bz2 to /usr/share/man/man1/prove.1.bz2 (relative)
* Linking /usr/bin/pod2man-2.3.1-perl-5.12.3 to /usr/bin/pod2man (relative)
* Linking /usr/share/man/man1/pod2man-2.3.1-perl-5.12.3.1.bz2 to /usr/share/man/man1/pod2man.1.bz2 (relative)
* Linking /usr/bin/pod2text-2.3.1-perl-5.12.3 to /usr/bin/pod2text (relative)
* Linking /usr/share/man/man1/pod2text-2.3.1-perl-5.12.3.1.bz2 to /usr/share/man/man1/pod2text.1.bz2 (relative)
>>> Unmerging dev-libs/gmp-5.0.2...
>>> Unmerging dev-libs/libxml2-2.7.8-r3...
>>> Unmerging dev-libs/openssl-1.0.0e...
>>> Unmerging dev-libs/popt-1.10.7...
>>> Unmerging net-misc/curl-7.21.4...
>>> Unmerging net-misc/iputils-20100418-r1...
>>> Unmerging net-misc/openssh-5.8_p1-r1...
>>> Unmerging net-misc/wget-1.12-r3...
>>> Unmerging perl-core/Scalar-List-Utils-1.230.0...
>>> Unmerging sys-apps/acl-2.2.51...
>>> Unmerging sys-apps/attr-2.4.32...
>>> Unmerging sys-apps/busybox-1.19.0...
>>> Unmerging sys-apps/coreutils-8.7...
>>> Unmerging sys-apps/diffutils-3.0...
>>> Unmerging sys-apps/file-5.07-r3...
>>> Unmerging sys-apps/gawk-3.1.8...
>>> Unmerging sys-apps/grep-2.5.4-r1...
>>> Unmerging sys-apps/groff-1.19.2-r1...
>>> Unmerging sys-apps/kbd-1.15.3...
>>> Unmerging sys-apps/less-444...
>>> Unmerging sys-apps/man-1.6f-r1...
>>> Unmerging sys-apps/portage-2.1.10.11...
<<< /usr/lib64/portage/pym/portage/cache/metadata_overlay.py[co]
<<< /usr/lib64/portage/pym/portage/cache/util.py[co]
>>> Unmerging sys-apps/sed-4.2.1...
>>> Unmerging sys-apps/shadow-4.1.4.3...
>>> Unmerging sys-apps/texinfo-4.13...
>>> Unmerging sys-apps/util-linux-2.19.1-r1...
>>> Unmerging sys-devel/gettext-0.18.1.1-r1...
>>> Unmerging sys-devel/make-3.81...
>>> Unmerging sys-fs/e2fsprogs-1.41.14...
>>> Unmerging sys-fs/udev-164-r2...
>>> Unmerging sys-libs/gdbm-1.8.3-r3...
>>> Unmerging sys-libs/glibc-2.13-r4...
[Errno 2] No such file or directory:
/bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* 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.
[Errno 2] No such file or directory:
/usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* The ebuild phase 'die_hooks' 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.
!!! FAILED postrm: 1
* The 'postrm' phase of the 'sys-libs/glibc-2.13-r4' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'glibc-2.13-r4.ebuild' located in the '/var/db/pkg/sys-
* libs/glibc-2.13-r4' 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/ncurses-5.6-r2...
[Errno 2] No such file or directory:
/bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/sys-libs/ncurses-5.6-r2/environment.bz2" > "/var/tmp/portage/._unmerge_/sys-libs/ncurses-5.6-r2/temp/environment"
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
!!! FAILED prerm: 1
[Errno 2] No such file or directory:
/bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* 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.
[Errno 2] No such file or directory:
/usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* The ebuild phase 'die_hooks' 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.
!!! FAILED postrm: 1
* The 'postrm' phase of the 'sys-libs/ncurses-5.6-r2' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'ncurses-5.6-r2.ebuild' located in the '/var/db/pkg/sys-
* libs/ncurses-5.6-r2' 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/pam-0.99.9.0...
[Errno 2] No such file or directory:
/bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/sys-libs/pam-0.99.9.0/environment.bz2" > "/var/tmp/portage/._unmerge_/sys-libs/pam-0.99.9.0/temp/environment"
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
!!! FAILED prerm: 1
[Errno 2] No such file or directory:
/bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* 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.
[Errno 2] No such file or directory:
/usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* The ebuild phase 'die_hooks' 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.
!!! FAILED postrm: 1
* The 'postrm' phase of the 'sys-libs/pam-0.99.9.0' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'pam-0.99.9.0.ebuild' located in the '/var/db/pkg/sys-libs/pam-0.99.9.0'
* 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.2_p1...
[Errno 2] No such file or directory:
/bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/sys-libs/readline-6.2_p1/environment.bz2" > "/var/tmp/portage/._unmerge_/sys-libs/readline-6.2_p1/temp/environment"
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
!!! FAILED prerm: 1
[Errno 2] No such file or directory:
/bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* 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.
[Errno 2] No such file or directory:
/usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* The ebuild phase 'die_hooks' 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.
!!! FAILED postrm: 1
* The 'postrm' phase of the 'sys-libs/readline-6.2_p1' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'readline-6.2_p1.ebuild' located in the '/var/db/pkg/sys-
* libs/readline-6.2_p1' 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-process/psmisc-22.14...
[Errno 2] No such file or directory:
/bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/sys-process/psmisc-22.14/environment.bz2" > "/var/tmp/portage/._unmerge_/sys-process/psmisc-22.14/temp/environment"
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
!!! FAILED prerm: 1
[Errno 2] No such file or directory:
/bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* 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.
[Errno 2] No such file or directory:
/usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* The ebuild phase 'die_hooks' 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.
!!! FAILED postrm: 1
* The 'postrm' phase of the 'sys-process/psmisc-22.14' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'psmisc-22.14.ebuild' located in the '/var/db/pkg/sys-
* process/psmisc-22.14' 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 virtual/perl-Digest-MD5-2.39...
[Errno 2] No such file or directory:
/bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/virtual/perl-Digest-MD5-2.39/environment.bz2" > "/var/tmp/portage/._unmerge_/virtual/perl-Digest-MD5-2.39/temp/environment"
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
!!! FAILED prerm: 1
[Errno 2] No such file or directory:
/bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* 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.
[Errno 2] No such file or directory:
/usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* The ebuild phase 'die_hooks' 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.
!!! FAILED postrm: 1
* The 'postrm' phase of the 'virtual/perl-Digest-MD5-2.39' package has
* failed with exit value 1.
*
* The problem occurred while executing the ebuild file named 'perl-Digest-
* MD5-2.39.ebuild' located in the '/var/db/pkg/virtual/perl-Digest-
* MD5-2.39' 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 virtual/perl-Scalar-List-Utils-1.230.0-r1...
[Errno 2] No such file or directory:
/bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/virtual/perl-Scalar-List-Utils-1.230.0-r1/environment.bz2" > "/var/tmp/portage/._unmerge_/virtual/perl-Scalar-List-Utils-1.230.0-r1/temp/environment"
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
!!! FAILED prerm: 1
[Errno 2] No such file or directory:
/bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* 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.
[Errno 2] No such file or directory:
/usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* The ebuild phase 'die_hooks' 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.
!!! FAILED postrm: 1
* The 'postrm' phase of the 'virtual/perl-Scalar-List-Utils-1.230.0-r1'
* package has failed with exit value 1.
*
* The problem occurred while executing the ebuild file named 'perl-Scalar-
* List-Utils-1.230.0-r1.ebuild' located in the '/var/db/pkg/virtual/perl-
* Scalar-List-Utils-1.230.0-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 virtual/perl-libnet-1.220.0-r1...
[Errno 2] No such file or directory:
/bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/virtual/perl-libnet-1.220.0-r1/environment.bz2" > "/var/tmp/portage/._unmerge_/virtual/perl-libnet-1.220.0-r1/temp/environment"
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
!!! FAILED prerm: 1
[Errno 2] No such file or directory:
/bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* 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.
[Errno 2] No such file or directory:
/usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
Traceback (most recent call last):
File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
env, gid, groups, uid, umask, pre_exec)
File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
os.execve(binary, myargs, env)
File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 2] No such file or directory
* The ebuild phase 'die_hooks' 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.
!!! FAILED postrm: 1
* The 'postrm' phase of the 'virtual/perl-libnet-1.220.0-r1' package has
* failed with exit value 1.
*
* The problem occurred while executing the ebuild file named 'perl-
* libnet-1.220.0-r1.ebuild' located in the '/var/db/pkg/virtual/perl-
* libnet-1.220.0-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 dev-lang/perl-5.12.4-r1:
* Removing dead symlink /usr/bin/xsubpp
* Removing dead symlink /usr/share/man/man1/xsubpp.1.bz2
* Messages for package sys-libs/glibc-2.13-r4:
* 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.13-r4' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'glibc-2.13-r4.ebuild' located in the '/var/db/pkg/sys-
* libs/glibc-2.13-r4' 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/ncurses-5.6-r2:
* 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/ncurses-5.6-r2' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'ncurses-5.6-r2.ebuild' located in the '/var/db/pkg/sys-
* libs/ncurses-5.6-r2' 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/pam-0.99.9.0:
* 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/pam-0.99.9.0' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'pam-0.99.9.0.ebuild' located in the '/var/db/pkg/sys-libs/pam-0.99.9.0'
* 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.2_p1:
* 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.2_p1' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'readline-6.2_p1.ebuild' located in the '/var/db/pkg/sys-
* libs/readline-6.2_p1' 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-process/psmisc-22.14:
* 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-process/psmisc-22.14' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'psmisc-22.14.ebuild' located in the '/var/db/pkg/sys-
* process/psmisc-22.14' 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 virtual/perl-Digest-MD5-2.39:
* 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 'virtual/perl-Digest-MD5-2.39' package has
* failed with exit value 1.
*
* The problem occurred while executing the ebuild file named 'perl-Digest-
* MD5-2.39.ebuild' located in the '/var/db/pkg/virtual/perl-Digest-
* MD5-2.39' 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 virtual/perl-Scalar-List-Utils-1.230.0-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 'virtual/perl-Scalar-List-Utils-1.230.0-r1'
* package has failed with exit value 1.
*
* The problem occurred while executing the ebuild file named 'perl-Scalar-
* List-Utils-1.230.0-r1.ebuild' located in the '/var/db/pkg/virtual/perl-
* Scalar-List-Utils-1.230.0-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 virtual/perl-libnet-1.220.0-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 'virtual/perl-libnet-1.220.0-r1' package has
* failed with exit value 1.
*
* The problem occurred while executing the ebuild file named 'perl-
* libnet-1.220.0-r1.ebuild' located in the '/var/db/pkg/virtual/perl-
* libnet-1.220.0-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.
* GNU info directory index is up-to-date.
* IMPORTANT: 5 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
<<[CHROOT]sabayon / # >> uname -r
bash: /usr/bin/uname: No such file or directory
<<[CHROOT]sabayon / # >> emerge
bash: /usr/bin/emerge: /usr/bin/python: bad interpreter: No such file or directory
<<[CHROOT]sabayon / # >> ls
bash: /bin/ls: No such file or directory
<<[CHROOT]sabayon / # >> cd /
<<[CHROOT]sabayon / # >> ls
bash: /bin/ls: No such file or directory