Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 265149 Details for
Bug 357009
Portage should disallow uninstallation of currently used Python interpreter
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Failure when using 2011-02-24 stage3
log.txt (text/plain), 151.48 KB, created by
Albert W. Hopkins
on 2011-03-08 13:07:44 UTC
(
hide
)
Description:
Failure when using 2011-02-24 stage3
Filename:
MIME Type:
Creator:
Albert W. Hopkins
Created:
2011-03-08 13:07:44 UTC
Size:
151.48 KB
patch
obsolete
>2011-03-08 07:35:41 (1.09 MB/s) - `stage3-amd64-20110224.tar.bz2' saved [160027705/160027705] > ># tar xjpf stage3-amd64-20110224.tar.bz2 -C /var/tmp/357001 ># mount -t proc none /var/tmp/357001/proc ># mount -o bind /dev /var/tmp/357001/dev ># wget http://gentoo.osuosl.org/snapshots/portage-latest.tar.xz >--2011-03-08 07:37:03-- http://gentoo.osuosl.org/snapshots/portage-latest.tar.xz >Resolving gentoo.osuosl.org... 64.50.236.52, 64.50.233.100 >Connecting to gentoo.osuosl.org|64.50.236.52|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 34005884 (32M) [application/x-tar] >Saving to: `portage-latest.tar.xz' > > 0% [ ] 0 --.-K/s 0% [ ] 24,322 118K/s 0% [ ] 99,618 243K/s 0% [ ] 264,690 422K/s 1% [ ] 463,066 555K/s 2% [ ] 693,298 662K/s 2% [> ] 988,690 785K/s 3% [> ] 1,324,626 893K/s 4% [> ] 1,579,474 934K/s 5% [=> ] 1,825,634 960K/s 6% [=> ] 2,096,866 993K/s 6% [=> ] 2,380,218 1.00M/s 7% [==> ] 2,698,778 1.04M/s 8% [==> ] 2,991,274 1.06M/s 9% [==> ] 3,185,306 1.05M/s 9% [==> ] 3,363,410 1.04M/s eta 28s 10% [===> ] 3,658,802 1.06M/s eta 28s 11% [===> ] 3,997,634 1.19M/s eta 28s 13% [====> ] 4,437,826 1.27M/s eta 28s 14% [====> ] 4,811,866 1.32M/s eta 28s 15% [====> ] 5,202,370 1.39M/s eta 23s 16% [=====> ] 5,554,234 1.40M/s eta 23s 17% [=====> ] 5,824,018 1.40M/s eta 23s 18% [======> ] 6,145,018 1.41M/s eta 23s 18% [======> ] 6,402,762 1.41M/s eta 23s 19% [======> ] 6,602,586 1.39M/s eta 21s 20% [======> ] 6,819,786 1.37M/s eta 21s 20% [=======> ] 7,028,298 1.34M/s eta 21s 21% [=======> ] 7,310,658 1.34M/s eta 21s 22% [=======> ] 7,645,146 1.38M/s eta 21s 23% [========> ] 8,054,930 1.44M/s eta 20s 24% [========> ] 8,411,138 1.47M/s eta 20s 25% [========> ] 8,715,218 1.46M/s eta 20s 26% [=========> ] 8,977,306 1.42M/s eta 20s 27% [=========> ] 9,325,282 1.41M/s eta 20s 28% [==========> ] 9,631,802 1.37M/s eta 18s 29% [==========> ] 10,010,186 1.40M/s eta 18s 30% [===========> ] 10,478,882 1.45M/s eta 18s 32% [===========> ] 10,887,674 1.48M/s eta 18s 33% [===========> ] 11,312,930 1.52M/s eta 18s 34% [============> ] 11,745,882 1.56M/s eta 16s 35% [============> ] 12,089,058 1.63M/s eta 16s 36% [=============> ] 12,548,530 1.69M/s eta 16s 37% [=============> ] 12,870,978 1.72M/s eta 16s 38% [==============> ] 13,205,922 1.71M/s eta 16s 40% [==============> ] 13,631,634 1.72M/s eta 14s 41% [===============> ] 14,030,826 1.72M/s eta 14s 42% [===============> ] 14,392,826 1.72M/s eta 14s 43% [===============> ] 14,705,594 1.75M/s eta 14s 43% [================> ] 14,923,250 1.72M/s eta 14s 44% [================> ] 15,184,882 1.69M/s eta 13s 45% [================> ] 15,455,658 1.67M/s eta 13s 45% [================> ] 15,610,594 1.61M/s eta 13s 46% [=================> ] 15,822,002 1.54M/s eta 13s 47% [=================> ] 16,056,578 1.47M/s eta 13s 47% [=================> ] 16,251,066 1.39M/s eta 12s 48% [==================> ] 16,625,642 1.40M/s eta 12s 49% [==================> ] 16,920,042 1.37M/s eta 12s 50% [==================> ] 17,234,258 1.35M/s eta 12s 51% [===================> ] 17,655,626 1.37M/s eta 12s 52% [===================> ] 17,973,730 1.36M/s eta 11s 53% [===================> ] 18,222,786 1.32M/s eta 11s 54% [====================> ] 18,500,802 1.29M/s eta 11s 54% [====================> ] 18,689,042 1.23M/s eta 11s 55% [====================> ] 18,914,930 1.22M/s eta 11s 56% [====================> ] 19,135,026 1.22M/s eta 10s 57% [=====================> ] 19,392,770 1.20M/s eta 10s 57% [=====================> ] 19,663,546 1.23M/s eta 10s 58% [=====================> ] 19,973,418 1.26M/s eta 10s 59% [======================> ] 20,331,074 1.30M/s eta 10s 60% [======================> ] 20,678,594 1.35M/s eta 9s 62% [=======================> ] 21,130,370 1.41M/s eta 9s 63% [=======================> ] 21,545,946 1.43M/s eta 9s 64% [========================> ] 21,876,090 1.43M/s eta 9s 64% [========================> ] 22,085,058 1.39M/s eta 9s 65% [========================> ] 22,339,450 1.36M/s eta 8s 66% [========================> ] 22,563,890 1.33M/s eta 8s 66% [=========================> ] 22,760,818 1.32M/s eta 8s 67% [=========================> ] 22,996,842 1.31M/s eta 8s 68% [=========================> ] 23,240,562 1.33M/s eta 8s 69% [==========================> ] 23,566,362 1.35M/s eta 7s 70% [==========================> ] 23,854,058 1.37M/s eta 7s 71% [==========================> ] 24,256,602 1.42M/s eta 7s 72% [===========================> ] 24,705,482 1.44M/s eta 7s 74% [===========================> ] 25,196,354 1.50M/s eta 7s 75% [============================> ] 25,770,218 1.57M/s eta 6s 77% [=============================> ] 26,233,578 1.58M/s eta 6s 78% [=============================> ] 26,625,530 1.59M/s eta 6s 79% [=============================> ] 27,010,698 1.58M/s eta 6s 80% [==============================> ] 27,274,690 1.56M/s eta 6s 81% [==============================> ] 27,592,794 1.60M/s eta 4s 81% [==============================> ] 27,791,170 1.59M/s eta 4s 82% [===============================> ] 27,988,098 1.57M/s eta 4s 83% [===============================> ] 28,235,706 1.60M/s eta 4s 83% [===============================> ] 28,487,658 1.59M/s eta 4s 84% [===============================> ] 28,704,858 1.56M/s eta 4s 85% [================================> ] 28,937,986 1.54M/s eta 4s 85% [================================> ] 29,068,306 1.46M/s eta 4s 85% [================================> ] 29,240,618 1.39M/s eta 4s 86% [================================> ] 29,438,994 1.26M/s eta 4s 87% [=================================> ] 29,673,570 1.20M/s eta 3s 87% [=================================> ] 29,887,874 1.14M/s eta 3s 88% [=================================> ] 30,131,138 1.09M/s eta 3s 89% [=================================> ] 30,421,194 1.03M/s eta 3s 90% [==================================> ] 30,684,274 1.02M/s eta 3s 91% [==================================> ] 30,972,426 1.02M/s eta 2s 91% [==================================> ] 31,247,546 1.05M/s eta 2s 92% [===================================> ] 31,485,018 1.07M/s eta 2s 93% [===================================> ] 31,702,218 1.07M/s eta 2s 93% [===================================> ] 31,925,210 1.05M/s eta 2s 94% [===================================> ] 32,106,210 1.03M/s eta 1s 95% [====================================> ] 32,307,482 1.03M/s eta 1s 95% [====================================> ] 32,552,194 1.06M/s eta 1s 96% [====================================> ] 32,820,074 1.09M/s eta 1s 97% [====================================> ] 33,122,706 1.11M/s eta 1s 98% [=====================================> ] 33,461,538 1.16M/s eta 0s 99% [=====================================> ] 33,780,098 1.20M/s eta 0s 100%[======================================>] 34,005,884 1.20M/s in 24s > >2011-03-08 07:37:28 (1.34 MB/s) - `portage-latest.tar.xz' saved [34005884/34005884] > ># tar xaf portage-latest.tar.bz2 -C /var/tmp/357001/usr ># mkdir /var/tmp/357001/usr/portage/packages ># mount -o bind /var/scratch/packages /var/tmp/357001/usr/portage/packages ># cp -L /etc/resolv.conf /var/tmp/357001/etc/ ># chroot /var/tmp/357001 /bin/bash >#[00m PS1="(chroot}# " >(chroot}# PS1="(chroot}# "[1P[1@) >(chroot)# env-update >>>> Regenerating /etc/ld.so.cache... >(chroot)# source /etc/profile >[01;31mvictoria[01;34m / #[00m source /etc/profile[9Penv-updatePS1="(chroot)# "}# ")# " >(chroot)# basic configurations (make.conf, locale.gen, package.use)b[1@#[1@ >(chroot)# export NOCOLOR=true >(chroot)# emerge --sync --quiet > >Performing Global Updates >(Could take a couple of minutes if you have a lot of binary packages.) > > >]0;emerge > * IMPORTANT: 2 news items need reading for repository 'gentoo'. > * Use eselect news to read news items. > >(chroot)# emerge --usepkg --binpkg-respect-use=y --newuse p update --newuse --deep worl --quie t world[1PM(chroot)# emerge --usepkg --binpkg-respect-use=y --update --newuse --deep --qui w[1PMchroot)# emerge --usepkg --binpkg-respect-use=y --update --newuse --deep --qui wo[1PMchroot)# emerge --usepkg --binpkg-respect-use=y --update --newuse --deep --qu wor[1PMchroot)# emerge --usepkg --binpkg-respect-use=y --update --newuse --deep --q worl[1PdMhroot)# emerge --usepkg --binpkg-respect-use=y --update --newuse --deep -- world[KMchroot)# emerge --usepkg --binpkg-respect-use=y --update --newuse --deep - world [KM(chroot)# emerge --usepkg --binpkg-respect-use=y --update --newuse --deep [1P >[KM(chroot)# emerge --usepkg --binpkg-respect-use=y --update --newuse --deep >]0;emerge > * IMPORTANT: 2 news items need reading for repository 'gentoo'. > * Use eselect news to read news items. > >Calculating dependencies - \ \ - | - | | - | | - | - - | - \ \ - / \ \... done! >>>> Starting parallel fetchE>>> Jobs: 0 of 43 complete, 1 running Load avg: 0.15, 0.15, 0.25]0;Jobs: 0 of 43 complete, 1 running Load avg: 0.15, 0.15, 0.25[K>>> Emerging binary (1 of 43) sys-libs/glibc-2.11.3E>>> Jobs: 0 of 43 complete, 1 running Load avg: 0.15, 0.15, 0.25]0;Jobs: 0 of 43 complete, 1 running Load avg: 0.15, 0.15, 0.25openpty failed: 'out of pty devices' >[K>>> Jobs: 0 of 43 complete, 1 running Load avg: 0.22, 0.16, 0.25]0;Jobs: 0 of 43 complete, 1 running Load avg: 0.22, 0.16, 0.25[K>>> Jobs: 0 of 43 complete Load avg: 0.22, 0.16, 0.25]0;Jobs: 0 of 43 complete Load avg: 0.22, 0.16, 0.25[K>>> Installing (1 of 43) sys-libs/glibc-2.11.3E>>> Jobs: 0 of 43 complete Load avg: 0.22, 0.16, 0.25]0;Jobs: 0 of 43 complete Load avg: 0.22, 0.16, 0.25[K>>> Jobs: 0 of 43 complete Load avg: 0.20, 0.16, 0.25]0;Jobs: 0 of 43 complete Load avg: 0.20, 0.16, 0.25[K>>> Jobs: 0 of 43 complete Load avg: 0.20, 0.16, 0.25]0;Jobs: 0 of 43 complete Load avg: 0.20, 0.16, 0.25[K>>> Jobs: 0 of 43 complete Load avg: 0.26, 0.18, 0.25]0;Jobs: 0 of 43 complete Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 1 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 1 running Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Emerging binary (2 of 43) sys-libs/ncurses-5.7-r3E>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Emerging binary (3 of 43) sys-apps/coreutils-8.7E>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 1 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 1 running Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Emerging binary (4 of 43) sys-apps/sed-4.2.1E>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 1 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 1 running Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Emerging binary (5 of 43) sys-apps/findutils-4.4.2E>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 1 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 1 running Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Emerging binary (6 of 43) sys-libs/timezone-data-2010oE>>> Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25]0;Jobs: 1 of 43 complete, 2 running Load avg: 0.26, 0.18, 0.25[K>>> Jobs: 1 of 43 complete, 1 running Load avg: 0.40, 0.21, 0.26]0;Jobs: 1 of 43 complete, 1 running Load avg: 0.40, 0.21, 0.26[K>>> Jobs: 1 of 43 complete Load avg: 0.40, 0.21, 0.26]0;Jobs: 1 of 43 complete Load avg: 0.40, 0.21, 0.26[K>>> Installing (2 of 43) sys-libs/ncurses-5.7-r3E>>> Jobs: 1 of 43 complete Load avg: 0.40, 0.21, 0.26]0;Jobs: 1 of 43 complete Load avg: 0.40, 0.21, 0.26[K>>> Jobs: 1 of 43 complete Load avg: 0.40, 0.21, 0.26]0;Jobs: 1 of 43 complete Load avg: 0.40, 0.21, 0.26[K>>> Jobs: 1 of 43 complete Load avg: 0.45, 0.22, 0.27]0;Jobs: 1 of 43 complete Load avg: 0.45, 0.22, 0.27[K>>> Jobs: 1 of 43 complete Load avg: 0.45, 0.22, 0.27]0;Jobs: 1 of 43 complete Load avg: 0.45, 0.22, 0.27[K>>> Jobs: 2 of 43 complete Load avg: 0.45, 0.22, 0.27]0;Jobs: 2 of 43 complete Load avg: 0.45, 0.22, 0.27[K>>> Installing (3 of 43) sys-apps/coreutils-8.7E>>> Jobs: 2 of 43 complete Load avg: 0.45, 0.22, 0.27]0;Jobs: 2 of 43 complete Load avg: 0.45, 0.22, 0.27[K>>> Jobs: 2 of 43 complete Load avg: 0.49, 0.23, 0.27]0;Jobs: 2 of 43 complete Load avg: 0.49, 0.23, 0.27[K>>> Jobs: 3 of 43 complete Load avg: 0.49, 0.23, 0.27]0;Jobs: 3 of 43 complete Load avg: 0.49, 0.23, 0.27[K>>> Installing (4 of 43) sys-apps/sed-4.2.1E>>> Jobs: 3 of 43 complete Load avg: 0.49, 0.23, 0.27]0;Jobs: 3 of 43 complete Load avg: 0.49, 0.23, 0.27[K>>> Jobs: 3 of 43 complete Load avg: 0.49, 0.23, 0.27]0;Jobs: 3 of 43 complete Load avg: 0.49, 0.23, 0.27[K>>> Jobs: 4 of 43 complete Load avg: 0.49, 0.23, 0.27]0;Jobs: 4 of 43 complete Load avg: 0.49, 0.23, 0.27[K>>> Installing (5 of 43) sys-apps/findutils-4.4.2E>>> Jobs: 4 of 43 complete Load avg: 0.49, 0.23, 0.27]0;Jobs: 4 of 43 complete Load avg: 0.49, 0.23, 0.27[K>>> Jobs: 4 of 43 complete Load avg: 0.53, 0.25, 0.27]0;Jobs: 4 of 43 complete Load avg: 0.53, 0.25, 0.27[K>>> Jobs: 5 of 43 complete Load avg: 0.53, 0.25, 0.27]0;Jobs: 5 of 43 complete Load avg: 0.53, 0.25, 0.27[K>>> Installing (6 of 43) sys-libs/timezone-data-2010oE>>> Jobs: 5 of 43 complete Load avg: 0.53, 0.25, 0.27]0;Jobs: 5 of 43 complete Load avg: 0.53, 0.25, 0.27[K>>> Jobs: 5 of 43 complete Load avg: 0.53, 0.25, 0.27]0;Jobs: 5 of 43 complete Load avg: 0.53, 0.25, 0.27[K>>> Jobs: 5 of 43 complete Load avg: 0.57, 0.26, 0.28]0;Jobs: 5 of 43 complete Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Emerging binary (7 of 43) app-misc/pax-utils-0.2.2E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Emerging binary (8 of 43) dev-libs/popt-1.16E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Emerging binary (9 of 43) sys-libs/e2fsprogs-libs-1.41.12E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Emerging binary (10 of 43) sys-apps/grep-2.5.4-r1E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Emerging binary (11 of 43) app-arch/gzip-1.4E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.57, 0.26, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Emerging binary (12 of 43) sys-apps/kbd-1.15E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Emerging binary (13 of 43) sys-apps/net-tools-1.60_p20090728014017-r1E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Emerging binary (14 of 43) sys-devel/flex-2.5.35E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Emerging binary (15 of 43) sys-apps/gawk-3.1.6E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Emerging binary (16 of 43) app-arch/xz-utils-5.0.1E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Emerging binary (17 of 43) app-arch/tar-1.23-r2E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.61, 0.27, 0.28[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Emerging binary (18 of 43) app-arch/cpio-2.11E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Emerging binary (19 of 43) net-misc/wget-1.12-r3E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Emerging binary (20 of 43) sys-devel/make-3.81-r2E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Emerging binary (21 of 43) sys-apps/diffutils-2.8.7-r2E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Emerging binary (22 of 43) app-shells/bash-4.1_p9E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Emerging binary (23 of 43) sys-apps/util-linux-2.18-r1E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.64, 0.28, 0.29[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Emerging binary (24 of 43) sys-apps/texinfo-4.13E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Emerging binary (25 of 43) sys-process/psmisc-22.12E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Emerging binary (26 of 43) sys-devel/bison-2.4.2E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Emerging binary (27 of 43) net-misc/iputils-20100418-r1E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Emerging binary (28 of 43) app-editors/nano-2.2.5E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Emerging binary (29 of 43) sys-devel/binutils-2.20.1-r1E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.75, 0.31, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.77, 0.32, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30[K>>> Emerging binary (30 of 43) sys-devel/gcc-4.4.5E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.77, 0.32, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30[K>>> Emerging binary (31 of 43) sys-libs/pam-1.1.3E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.77, 0.32, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30[K>>> Emerging binary (32 of 43) dev-libs/openssl-1.0.0dE>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.77, 0.32, 0.30[K>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30[K>>> Emerging binary (33 of 43) sys-apps/file-5.05E>>> Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30]0;Jobs: 6 of 43 complete, 2 running Load avg: 0.77, 0.32, 0.30[K>>> Jobs: 6 of 43 complete, 1 running Load avg: 0.87, 0.35, 0.31]0;Jobs: 6 of 43 complete, 1 running Load avg: 0.87, 0.35, 0.31[K>>> Jobs: 6 of 43 complete Load avg: 0.87, 0.35, 0.31]0;Jobs: 6 of 43 complete Load avg: 0.87, 0.35, 0.31[K>>> Installing (7 of 43) app-misc/pax-utils-0.2.2E>>> Jobs: 6 of 43 complete Load avg: 0.87, 0.35, 0.31]0;Jobs: 6 of 43 complete Load avg: 0.87, 0.35, 0.31[K>>> Jobs: 6 of 43 complete Load avg: 0.87, 0.35, 0.31]0;Jobs: 6 of 43 complete Load avg: 0.87, 0.35, 0.31[K>>> Jobs: 7 of 43 complete Load avg: 0.87, 0.35, 0.31]0;Jobs: 7 of 43 complete Load avg: 0.87, 0.35, 0.31[K>>> Installing (8 of 43) dev-libs/popt-1.16E>>> Jobs: 7 of 43 complete Load avg: 0.87, 0.35, 0.31]0;Jobs: 7 of 43 complete Load avg: 0.87, 0.35, 0.31[K>>> Jobs: 8 of 43 complete Load avg: 0.88, 0.36, 0.31]0;Jobs: 8 of 43 complete Load avg: 0.88, 0.36, 0.31[K>>> Installing (9 of 43) sys-libs/e2fsprogs-libs-1.41.12E>>> Jobs: 8 of 43 complete Load avg: 0.88, 0.36, 0.31]0;Jobs: 8 of 43 complete Load avg: 0.88, 0.36, 0.31[K>>> Jobs: 8 of 43 complete Load avg: 0.88, 0.36, 0.31]0;Jobs: 8 of 43 complete Load avg: 0.88, 0.36, 0.31[K>>> Jobs: 9 of 43 complete Load avg: 0.88, 0.36, 0.31]0;Jobs: 9 of 43 complete Load avg: 0.88, 0.36, 0.31[K>>> Installing (10 of 43) sys-apps/grep-2.5.4-r1E>>> Jobs: 9 of 43 complete Load avg: 0.88, 0.36, 0.31]0;Jobs: 9 of 43 complete Load avg: 0.88, 0.36, 0.31[K>>> Jobs: 9 of 43 complete Load avg: 0.81, 0.35, 0.31]0;Jobs: 9 of 43 complete Load avg: 0.81, 0.35, 0.31[K>>> Jobs: 10 of 43 complete Load avg: 0.81, 0.35, 0.31]0;Jobs: 10 of 43 complete Load avg: 0.81, 0.35, 0.31[K>>> Installing (11 of 43) app-arch/gzip-1.4E>>> Jobs: 10 of 43 complete Load avg: 0.81, 0.35, 0.31]0;Jobs: 10 of 43 complete Load avg: 0.81, 0.35, 0.31[K>>> Jobs: 10 of 43 complete Load avg: 0.81, 0.35, 0.31]0;Jobs: 10 of 43 complete Load avg: 0.81, 0.35, 0.31[K>>> Jobs: 11 of 43 complete Load avg: 0.81, 0.35, 0.31]0;Jobs: 11 of 43 complete Load avg: 0.81, 0.35, 0.31[K>>> Installing (12 of 43) sys-apps/kbd-1.15E>>> Jobs: 11 of 43 complete Load avg: 0.81, 0.35, 0.31]0;Jobs: 11 of 43 complete Load avg: 0.81, 0.35, 0.31[K>>> Jobs: 11 of 43 complete Load avg: 0.82, 0.37, 0.32]0;Jobs: 11 of 43 complete Load avg: 0.82, 0.37, 0.32[K>>> Jobs: 12 of 43 complete Load avg: 0.82, 0.37, 0.32]0;Jobs: 12 of 43 complete Load avg: 0.82, 0.37, 0.32[K>>> Installing (13 of 43) sys-apps/net-tools-1.60_p20090728014017-r1E>>> Jobs: 12 of 43 complete Load avg: 0.82, 0.37, 0.32]0;Jobs: 12 of 43 complete Load avg: 0.82, 0.37, 0.32[K>>> Jobs: 12 of 43 complete Load avg: 0.82, 0.37, 0.32]0;Jobs: 12 of 43 complete Load avg: 0.82, 0.37, 0.32[K>>> Jobs: 13 of 43 complete Load avg: 0.82, 0.37, 0.32]0;Jobs: 13 of 43 complete Load avg: 0.82, 0.37, 0.32[K>>> Installing (14 of 43) sys-devel/flex-2.5.35E>>> Jobs: 13 of 43 complete Load avg: 0.82, 0.37, 0.32]0;Jobs: 13 of 43 complete Load avg: 0.82, 0.37, 0.32[K>>> Jobs: 13 of 43 complete Load avg: 0.84, 0.38, 0.32]0;Jobs: 13 of 43 complete Load avg: 0.84, 0.38, 0.32[K>>> Jobs: 14 of 43 complete Load avg: 0.84, 0.38, 0.32]0;Jobs: 14 of 43 complete Load avg: 0.84, 0.38, 0.32[K>>> Installing (15 of 43) sys-apps/gawk-3.1.6E>>> Jobs: 14 of 43 complete Load avg: 0.84, 0.38, 0.32]0;Jobs: 14 of 43 complete Load avg: 0.84, 0.38, 0.32[K>>> Jobs: 14 of 43 complete Load avg: 0.84, 0.38, 0.32]0;Jobs: 14 of 43 complete Load avg: 0.84, 0.38, 0.32[K>>> Jobs: 15 of 43 complete Load avg: 0.84, 0.38, 0.32]0;Jobs: 15 of 43 complete Load avg: 0.84, 0.38, 0.32[K>>> Installing (16 of 43) app-arch/xz-utils-5.0.1E>>> Jobs: 15 of 43 complete Load avg: 0.84, 0.38, 0.32]0;Jobs: 15 of 43 complete Load avg: 0.84, 0.38, 0.32[K>>> Jobs: 16 of 43 complete Load avg: 0.85, 0.39, 0.32]0;Jobs: 16 of 43 complete Load avg: 0.85, 0.39, 0.32[K>>> Installing (17 of 43) app-arch/tar-1.23-r2E>>> Jobs: 16 of 43 complete Load avg: 0.85, 0.39, 0.32]0;Jobs: 16 of 43 complete Load avg: 0.85, 0.39, 0.32[K>>> Jobs: 16 of 43 complete Load avg: 0.85, 0.39, 0.32]0;Jobs: 16 of 43 complete Load avg: 0.85, 0.39, 0.32[K>>> Jobs: 17 of 43 complete Load avg: 0.85, 0.39, 0.32]0;Jobs: 17 of 43 complete Load avg: 0.85, 0.39, 0.32[K>>> Installing (18 of 43) app-arch/cpio-2.11E>>> Jobs: 17 of 43 complete Load avg: 0.85, 0.39, 0.32]0;Jobs: 17 of 43 complete Load avg: 0.85, 0.39, 0.32[K>>> Jobs: 17 of 43 complete Load avg: 0.86, 0.40, 0.33]0;Jobs: 17 of 43 complete Load avg: 0.86, 0.40, 0.33[K>>> Jobs: 18 of 43 complete Load avg: 0.86, 0.40, 0.33]0;Jobs: 18 of 43 complete Load avg: 0.86, 0.40, 0.33[K>>> Installing (19 of 43) net-misc/wget-1.12-r3E>>> Jobs: 18 of 43 complete Load avg: 0.86, 0.40, 0.33]0;Jobs: 18 of 43 complete Load avg: 0.86, 0.40, 0.33[K>>> Jobs: 18 of 43 complete Load avg: 0.79, 0.39, 0.32]0;Jobs: 18 of 43 complete Load avg: 0.79, 0.39, 0.32[K>>> Jobs: 19 of 43 complete Load avg: 0.79, 0.39, 0.32]0;Jobs: 19 of 43 complete Load avg: 0.79, 0.39, 0.32[K>>> Installing (20 of 43) sys-devel/make-3.81-r2E>>> Jobs: 19 of 43 complete Load avg: 0.79, 0.39, 0.32]0;Jobs: 19 of 43 complete Load avg: 0.79, 0.39, 0.32[K>>> Jobs: 19 of 43 complete Load avg: 0.79, 0.39, 0.32]0;Jobs: 19 of 43 complete Load avg: 0.79, 0.39, 0.32[K>>> Jobs: 20 of 43 complete Load avg: 0.79, 0.39, 0.32]0;Jobs: 20 of 43 complete Load avg: 0.79, 0.39, 0.32[K>>> Installing (21 of 43) sys-apps/diffutils-2.8.7-r2E>>> Jobs: 20 of 43 complete Load avg: 0.79, 0.39, 0.32]0;Jobs: 20 of 43 complete Load avg: 0.79, 0.39, 0.32[K>>> Jobs: 20 of 43 complete Load avg: 0.89, 0.42, 0.33]0;Jobs: 20 of 43 complete Load avg: 0.89, 0.42, 0.33[K>>> Jobs: 21 of 43 complete Load avg: 0.89, 0.42, 0.33]0;Jobs: 21 of 43 complete Load avg: 0.89, 0.42, 0.33[K>>> Installing (22 of 43) app-shells/bash-4.1_p9E>>> Jobs: 21 of 43 complete Load avg: 0.89, 0.42, 0.33]0;Jobs: 21 of 43 complete Load avg: 0.89, 0.42, 0.33[K>>> Jobs: 21 of 43 complete Load avg: 0.89, 0.42, 0.33]0;Jobs: 21 of 43 complete Load avg: 0.89, 0.42, 0.33[K>>> Jobs: 22 of 43 complete Load avg: 0.89, 0.42, 0.33]0;Jobs: 22 of 43 complete Load avg: 0.89, 0.42, 0.33[K>>> Installing (23 of 43) sys-apps/util-linux-2.18-r1E>>> Jobs: 22 of 43 complete Load avg: 0.89, 0.42, 0.33]0;Jobs: 22 of 43 complete Load avg: 0.89, 0.42, 0.33[K>>> Jobs: 22 of 43 complete Load avg: 0.90, 0.43, 0.34]0;Jobs: 22 of 43 complete Load avg: 0.90, 0.43, 0.34[K>>> Jobs: 23 of 43 complete Load avg: 0.90, 0.43, 0.34]0;Jobs: 23 of 43 complete Load avg: 0.90, 0.43, 0.34[K>>> Installing (24 of 43) sys-apps/texinfo-4.13E>>> Jobs: 23 of 43 complete Load avg: 0.90, 0.43, 0.34]0;Jobs: 23 of 43 complete Load avg: 0.90, 0.43, 0.34[K>>> Jobs: 23 of 43 complete Load avg: 0.90, 0.43, 0.34]0;Jobs: 23 of 43 complete Load avg: 0.90, 0.43, 0.34[K>>> Jobs: 24 of 43 complete Load avg: 0.90, 0.43, 0.34]0;Jobs: 24 of 43 complete Load avg: 0.90, 0.43, 0.34[K>>> Installing (25 of 43) sys-process/psmisc-22.12E>>> Jobs: 24 of 43 complete Load avg: 0.90, 0.43, 0.34]0;Jobs: 24 of 43 complete Load avg: 0.90, 0.43, 0.34[K>>> Jobs: 24 of 43 complete Load avg: 0.83, 0.42, 0.33]0;Jobs: 24 of 43 complete Load avg: 0.83, 0.42, 0.33[K>>> Jobs: 25 of 43 complete Load avg: 0.83, 0.42, 0.33]0;Jobs: 25 of 43 complete Load avg: 0.83, 0.42, 0.33[K>>> Installing (26 of 43) sys-devel/bison-2.4.2E>>> Jobs: 25 of 43 complete Load avg: 0.83, 0.42, 0.33]0;Jobs: 25 of 43 complete Load avg: 0.83, 0.42, 0.33[K>>> Jobs: 25 of 43 complete Load avg: 0.83, 0.42, 0.33]0;Jobs: 25 of 43 complete Load avg: 0.83, 0.42, 0.33[K>>> Jobs: 26 of 43 complete Load avg: 0.83, 0.42, 0.33]0;Jobs: 26 of 43 complete Load avg: 0.83, 0.42, 0.33[K>>> Installing (27 of 43) net-misc/iputils-20100418-r1E>>> Jobs: 26 of 43 complete Load avg: 0.83, 0.42, 0.33]0;Jobs: 26 of 43 complete Load avg: 0.83, 0.42, 0.33[K>>> Jobs: 26 of 43 complete Load avg: 0.76, 0.41, 0.33]0;Jobs: 26 of 43 complete Load avg: 0.76, 0.41, 0.33[K>>> Jobs: 27 of 43 complete Load avg: 0.76, 0.41, 0.33]0;Jobs: 27 of 43 complete Load avg: 0.76, 0.41, 0.33[K>>> Installing (28 of 43) app-editors/nano-2.2.5E>>> Jobs: 27 of 43 complete Load avg: 0.76, 0.41, 0.33]0;Jobs: 27 of 43 complete Load avg: 0.76, 0.41, 0.33[K>>> Jobs: 27 of 43 complete Load avg: 0.76, 0.41, 0.33]0;Jobs: 27 of 43 complete Load avg: 0.76, 0.41, 0.33[K>>> Jobs: 28 of 43 complete Load avg: 0.76, 0.41, 0.33]0;Jobs: 28 of 43 complete Load avg: 0.76, 0.41, 0.33[K>>> Installing (29 of 43) sys-devel/binutils-2.20.1-r1E>>> Jobs: 28 of 43 complete Load avg: 0.76, 0.41, 0.33]0;Jobs: 28 of 43 complete Load avg: 0.76, 0.41, 0.33[K>>> Jobs: 28 of 43 complete Load avg: 0.70, 0.41, 0.33]0;Jobs: 28 of 43 complete Load avg: 0.70, 0.41, 0.33[K>>> Jobs: 28 of 43 complete Load avg: 0.70, 0.41, 0.33]0;Jobs: 28 of 43 complete Load avg: 0.70, 0.41, 0.33[K>>> Jobs: 29 of 43 complete Load avg: 0.64, 0.40, 0.33]0;Jobs: 29 of 43 complete Load avg: 0.64, 0.40, 0.33[K>>> Installing (31 of 43) sys-libs/pam-1.1.3E>>> Jobs: 29 of 43 complete Load avg: 0.64, 0.40, 0.33]0;Jobs: 29 of 43 complete Load avg: 0.64, 0.40, 0.33[K>>> Jobs: 29 of 43 complete Load avg: 0.64, 0.40, 0.33]0;Jobs: 29 of 43 complete Load avg: 0.64, 0.40, 0.33[K>>> Jobs: 30 of 43 complete Load avg: 0.64, 0.40, 0.33]0;Jobs: 30 of 43 complete Load avg: 0.64, 0.40, 0.33[K>>> Installing (30 of 43) sys-devel/gcc-4.4.5E>>> Jobs: 30 of 43 complete Load avg: 0.64, 0.40, 0.33]0;Jobs: 30 of 43 complete Load avg: 0.64, 0.40, 0.33[K>>> Jobs: 30 of 43 complete Load avg: 0.59, 0.39, 0.33]0;Jobs: 30 of 43 complete Load avg: 0.59, 0.39, 0.33[K>>> Jobs: 30 of 43 complete Load avg: 0.59, 0.39, 0.33]0;Jobs: 30 of 43 complete Load avg: 0.59, 0.39, 0.33[K>>> Jobs: 30 of 43 complete Load avg: 0.62, 0.40, 0.33]0;Jobs: 30 of 43 complete Load avg: 0.62, 0.40, 0.33[K>>> Jobs: 30 of 43 complete Load avg: 0.62, 0.40, 0.33]0;Jobs: 30 of 43 complete Load avg: 0.62, 0.40, 0.33[K>>> Jobs: 31 of 43 complete Load avg: 0.65, 0.41, 0.33]0;Jobs: 31 of 43 complete Load avg: 0.65, 0.41, 0.33[K>>> Installing (33 of 43) sys-apps/file-5.05E>>> Jobs: 31 of 43 complete Load avg: 0.65, 0.41, 0.33]0;Jobs: 31 of 43 complete Load avg: 0.65, 0.41, 0.33[K>>> Jobs: 31 of 43 complete Load avg: 0.65, 0.41, 0.33]0;Jobs: 31 of 43 complete Load avg: 0.65, 0.41, 0.33[K>>> Jobs: 32 of 43 complete Load avg: 0.65, 0.41, 0.33]0;Jobs: 32 of 43 complete Load avg: 0.65, 0.41, 0.33[K>>> Installing (32 of 43) dev-libs/openssl-1.0.0dE>>> Jobs: 32 of 43 complete Load avg: 0.65, 0.41, 0.33]0;Jobs: 32 of 43 complete Load avg: 0.65, 0.41, 0.33[K>>> Jobs: 32 of 43 complete Load avg: 0.68, 0.42, 0.34]0;Jobs: 32 of 43 complete Load avg: 0.68, 0.42, 0.34[K>>> Jobs: 32 of 43 complete Load avg: 0.68, 0.42, 0.34]0;Jobs: 32 of 43 complete Load avg: 0.68, 0.42, 0.34[K>>> Jobs: 33 of 43 complete Load avg: 0.68, 0.42, 0.34]0;Jobs: 33 of 43 complete Load avg: 0.68, 0.42, 0.34[K>>> Jobs: 33 of 43 complete, 1 running Load avg: 0.68, 0.42, 0.34]0;Jobs: 33 of 43 complete, 1 running Load avg: 0.68, 0.42, 0.34[K>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.68, 0.42, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.68, 0.42, 0.34[K>>> Emerging binary (34 of 43) net-misc/rsync-3.0.7E>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.68, 0.42, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.68, 0.42, 0.34[K>>> Emerging binary (35 of 43) sys-fs/e2fsprogs-1.41.12E>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34[K>>> Jobs: 33 of 43 complete, 1 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 1 running Load avg: 0.71, 0.43, 0.34[K>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34[K>>> Emerging binary (36 of 43) sys-apps/man-1.6f-r4E>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34[K>>> Jobs: 33 of 43 complete, 1 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 1 running Load avg: 0.71, 0.43, 0.34[K>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34[K>>> Emerging binary (37 of 43) sys-auth/pambase-20101024E>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34[K>>> Jobs: 33 of 43 complete, 1 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 1 running Load avg: 0.71, 0.43, 0.34[K>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34[K>>> Emerging binary (38 of 43) dev-lang/perl-5.12.2-r6E>>> Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 2 running Load avg: 0.71, 0.43, 0.34[K>>> Jobs: 33 of 43 complete, 1 running Load avg: 0.71, 0.43, 0.34]0;Jobs: 33 of 43 complete, 1 running Load avg: 0.71, 0.43, 0.34[K>>> Jobs: 33 of 43 complete, 1 running Load avg: 0.73, 0.44, 0.34]0;Jobs: 33 of 43 complete, 1 running Load avg: 0.73, 0.44, 0.34[K>>> Jobs: 33 of 43 complete Load avg: 0.73, 0.44, 0.34]0;Jobs: 33 of 43 complete Load avg: 0.73, 0.44, 0.34[K>>> Installing (34 of 43) net-misc/rsync-3.0.7E>>> Jobs: 33 of 43 complete Load avg: 0.73, 0.44, 0.34]0;Jobs: 33 of 43 complete Load avg: 0.73, 0.44, 0.34[K>>> Jobs: 33 of 43 complete Load avg: 0.73, 0.44, 0.34]0;Jobs: 33 of 43 complete Load avg: 0.73, 0.44, 0.34[K>>> Jobs: 34 of 43 complete Load avg: 0.75, 0.45, 0.35]0;Jobs: 34 of 43 complete Load avg: 0.75, 0.45, 0.35[K>>> Installing (35 of 43) sys-fs/e2fsprogs-1.41.12E>>> Jobs: 34 of 43 complete Load avg: 0.75, 0.45, 0.35]0;Jobs: 34 of 43 complete Load avg: 0.75, 0.45, 0.35[K>>> Jobs: 34 of 43 complete Load avg: 0.75, 0.45, 0.35]0;Jobs: 34 of 43 complete Load avg: 0.75, 0.45, 0.35[K>>> Jobs: 35 of 43 complete Load avg: 0.75, 0.45, 0.35]0;Jobs: 35 of 43 complete Load avg: 0.75, 0.45, 0.35[K>>> Installing (36 of 43) sys-apps/man-1.6f-r4E>>> Jobs: 35 of 43 complete Load avg: 0.75, 0.45, 0.35]0;Jobs: 35 of 43 complete Load avg: 0.75, 0.45, 0.35[K>>> Jobs: 35 of 43 complete Load avg: 0.77, 0.46, 0.35]0;Jobs: 35 of 43 complete Load avg: 0.77, 0.46, 0.35[K>>> Jobs: 36 of 43 complete Load avg: 0.77, 0.46, 0.35]0;Jobs: 36 of 43 complete Load avg: 0.77, 0.46, 0.35[K>>> Installing (37 of 43) sys-auth/pambase-20101024E>>> Jobs: 36 of 43 complete Load avg: 0.77, 0.46, 0.35]0;Jobs: 36 of 43 complete Load avg: 0.77, 0.46, 0.35[K>>> Jobs: 36 of 43 complete Load avg: 0.77, 0.46, 0.35]0;Jobs: 36 of 43 complete Load avg: 0.77, 0.46, 0.35[K>>> Jobs: 37 of 43 complete Load avg: 0.77, 0.46, 0.35]0;Jobs: 37 of 43 complete Load avg: 0.77, 0.46, 0.35[K>>> Installing (38 of 43) dev-lang/perl-5.12.2-r6E>>> Jobs: 37 of 43 complete Load avg: 0.77, 0.46, 0.35]0;Jobs: 37 of 43 complete Load avg: 0.77, 0.46, 0.35[K>>> Jobs: 37 of 43 complete Load avg: 0.79, 0.47, 0.35]0;Jobs: 37 of 43 complete Load avg: 0.79, 0.47, 0.35[K>>> Jobs: 37 of 43 complete Load avg: 0.79, 0.47, 0.35]0;Jobs: 37 of 43 complete Load avg: 0.79, 0.47, 0.35[K>>> Jobs: 37 of 43 complete Load avg: 0.81, 0.48, 0.36]0;Jobs: 37 of 43 complete Load avg: 0.81, 0.48, 0.36[K>>> Jobs: 38 of 43 complete Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete Load avg: 0.81, 0.48, 0.36[K>>> Jobs: 38 of 43 complete, 1 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 1 running Load avg: 0.81, 0.48, 0.36[K>>> Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36[K>>> Emerging binary (39 of 43) sys-apps/man-pages-3.28E>>> Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36[K>>> Emerging binary (40 of 43) sys-apps/busybox-1.17.4E>>> Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36[K>>> Jobs: 38 of 43 complete, 1 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 1 running Load avg: 0.81, 0.48, 0.36[K>>> Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36[K>>> Emerging binary (41 of 43) sys-apps/shadow-4.1.4.3E>>> Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36[K>>> Jobs: 38 of 43 complete, 1 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 1 running Load avg: 0.81, 0.48, 0.36[K>>> Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36[K>>> Emerging binary (42 of 43) dev-lang/python-3.1.3-r1E>>> Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36]0;Jobs: 38 of 43 complete, 2 running Load avg: 0.81, 0.48, 0.36[K>>> Jobs: 38 of 43 complete, 1 running Load avg: 0.82, 0.49, 0.36]0;Jobs: 38 of 43 complete, 1 running Load avg: 0.82, 0.49, 0.36[K>>> Jobs: 38 of 43 complete, 1 running Load avg: 0.82, 0.49, 0.36]0;Jobs: 38 of 43 complete, 1 running Load avg: 0.82, 0.49, 0.36[K>>> Jobs: 38 of 43 complete Load avg: 0.82, 0.49, 0.36]0;Jobs: 38 of 43 complete Load avg: 0.82, 0.49, 0.36[K>>> Installing (39 of 43) sys-apps/man-pages-3.28E>>> Jobs: 38 of 43 complete Load avg: 0.82, 0.49, 0.36]0;Jobs: 38 of 43 complete Load avg: 0.82, 0.49, 0.36[K>>> Jobs: 38 of 43 complete Load avg: 0.84, 0.49, 0.36]0;Jobs: 38 of 43 complete Load avg: 0.84, 0.49, 0.36[K>>> Jobs: 39 of 43 complete Load avg: 0.84, 0.49, 0.36]0;Jobs: 39 of 43 complete Load avg: 0.84, 0.49, 0.36[K>>> Installing (40 of 43) sys-apps/busybox-1.17.4E>>> Jobs: 39 of 43 complete Load avg: 0.84, 0.49, 0.36]0;Jobs: 39 of 43 complete Load avg: 0.84, 0.49, 0.36[K>>> Jobs: 39 of 43 complete Load avg: 0.84, 0.49, 0.36]0;Jobs: 39 of 43 complete Load avg: 0.84, 0.49, 0.36[K>>> Jobs: 40 of 43 complete Load avg: 0.84, 0.49, 0.36]0;Jobs: 40 of 43 complete Load avg: 0.84, 0.49, 0.36[K>>> Installing (41 of 43) sys-apps/shadow-4.1.4.3E>>> Jobs: 40 of 43 complete Load avg: 0.84, 0.49, 0.36]0;Jobs: 40 of 43 complete Load avg: 0.84, 0.49, 0.36[K>>> Jobs: 40 of 43 complete Load avg: 0.77, 0.49, 0.36]0;Jobs: 40 of 43 complete Load avg: 0.77, 0.49, 0.36[K>>> Jobs: 41 of 43 complete Load avg: 0.77, 0.49, 0.36]0;Jobs: 41 of 43 complete Load avg: 0.77, 0.49, 0.36[K>>> Installing (42 of 43) dev-lang/python-3.1.3-r1E>>> Jobs: 41 of 43 complete Load avg: 0.77, 0.49, 0.36]0;Jobs: 41 of 43 complete Load avg: 0.77, 0.49, 0.36[K>>> Jobs: 41 of 43 complete Load avg: 0.87, 0.51, 0.37]0;Jobs: 41 of 43 complete Load avg: 0.87, 0.51, 0.37[K>>> Jobs: 41 of 43 complete Load avg: 0.87, 0.51, 0.37]0;Jobs: 41 of 43 complete Load avg: 0.87, 0.51, 0.37[K>>> Jobs: 41 of 43 complete Load avg: 0.88, 0.52, 0.37]0;Jobs: 41 of 43 complete Load avg: 0.88, 0.52, 0.37[K>>> Jobs: 41 of 43 complete Load avg: 0.88, 0.52, 0.37]0;Jobs: 41 of 43 complete Load avg: 0.88, 0.52, 0.37[K>>> Jobs: 42 of 43 complete Load avg: 0.88, 0.52, 0.37]0;Jobs: 42 of 43 complete Load avg: 0.88, 0.52, 0.37[K>>> Jobs: 42 of 43 complete, 1 running Load avg: 0.88, 0.52, 0.37]0;Jobs: 42 of 43 complete, 1 running Load avg: 0.88, 0.52, 0.37[K>>> Emerging binary (43 of 43) net-misc/openssh-5.8_p1-r1E>>> Jobs: 42 of 43 complete, 1 running Load avg: 0.88, 0.52, 0.37]0;Jobs: 42 of 43 complete, 1 running Load avg: 0.88, 0.52, 0.37[K>>> Jobs: 42 of 43 complete Load avg: 0.88, 0.52, 0.37]0;Jobs: 42 of 43 complete Load avg: 0.88, 0.52, 0.37[K>>> Installing (43 of 43) net-misc/openssh-5.8_p1-r1E>>> Jobs: 42 of 43 complete Load avg: 0.88, 0.52, 0.37]0;Jobs: 42 of 43 complete Load avg: 0.88, 0.52, 0.37[K>>> Jobs: 42 of 43 complete Load avg: 0.89, 0.53, 0.38]0;Jobs: 42 of 43 complete Load avg: 0.89, 0.53, 0.38[K>>> Jobs: 43 of 43 complete Load avg: 0.89, 0.53, 0.38]0;Jobs: 43 of 43 complete Load avg: 0.89, 0.53, 0.38E > * Messages for package sys-apps/coreutils-8.7: > > * Make sure you run 'hash -r' in your active shells. > * You should also re-source your shell settings for LS_COLORS > * changes, such as: source /etc/profile > > * Messages for package sys-libs/timezone-data-2010o: > > * You do not have TIMEZONE set in /etc/conf.d/clock. > * Skipping auto-update of /etc/localtime. > > * Messages for package net-misc/wget-1.12-r3: > > * The /etc/wget/wgetrc file has been relocated to /etc/wgetrc > > * Messages for package sys-libs/pam-1.1.3: > > * Some software with pre-loaded PAM libraries might experience > * warnings or failures related to missing symbols and/or versions > * after any update. While unfortunate this is a limit of the > * implementation of PAM and the software, and it requires you to > * restart the software manually after the update. > * > * You can get a list of such software running a command like > * lsof / | egrep -i 'del.*libpam\.so' > * > * Alternatively, simply reboot your system. > > * Messages for package sys-devel/gcc-4.4.5: > > * If you have issues with packages unable to locate libstdc++.la, > * then try running 'fix_libtool_files.sh' on the old gcc versions. > * You might want to review the GCC upgrade guide when moving between > * major versions (like 4.2 to 4.3): > * http://www.gentoo.org/doc/en/gcc-upgrading.xml > > * Messages for package sys-fs/e2fsprogs-1.41.12: > > * No /etc/mtab file, creating one temporarily > > * Messages for package dev-lang/perl-5.12.2-r6: > > * Removing dead symlink /usr/share/man/man1/ptar.1.bz2 > * Removing dead symlink /usr/share/man/man1/ptardiff.1.bz2 > * Removing dead symlink /usr/share/man/man1/shasum.1.bz2 > * Removing dead symlink /usr/share/man/man1/cpan.1.bz2 > * Removing dead symlink /usr/share/man/man1/cpanp.1.bz2 > * Removing dead symlink /usr/share/man/man1/cpan2dist.1.bz2 > * Removing dead symlink /usr/share/man/man1/enc2xs.1.bz2 > * Removing dead symlink /usr/share/man/man1/piconv.1.bz2 > * Removing dead symlink /usr/share/man/man1/instmodsh.1.bz2 > * Removing dead symlink /usr/share/man/man1/config_data.1.bz2 > * Removing dead symlink /usr/share/man/man1/corelist.1.bz2 > * Removing dead symlink /usr/share/man/man1/pod2usage.1.bz2 > * Removing dead symlink /usr/share/man/man1/podchecker.1.bz2 > * Removing dead symlink /usr/share/man/man1/podselect.1.bz2 > * Removing dead symlink /usr/share/man/man1/prove.1.bz2 > * Removing dead symlink /usr/share/man/man1/pod2man.1.bz2 > * Removing dead symlink /usr/share/man/man1/pod2text.1.bz2 > > * Messages for package dev-lang/perl-5.12.2-r6: > > * Unable to establish /usr/share/man/man1/ptar.1* symlink > * Unable to establish /usr/share/man/man1/ptardiff.1* symlink > * Unable to establish /usr/share/man/man1/shasum.1* symlink > * Unable to establish /usr/share/man/man1/cpan.1* symlink > * Unable to establish /usr/share/man/man1/cpanp.1* symlink > * Unable to establish /usr/share/man/man1/cpan2dist.1* symlink > * Unable to establish /usr/share/man/man1/enc2xs.1* symlink > * Unable to establish /usr/share/man/man1/piconv.1* symlink > * Unable to establish /usr/share/man/man1/instmodsh.1* symlink > * Unable to establish /usr/share/man/man1/config_data.1* symlink > * Unable to establish /usr/share/man/man1/corelist.1* symlink > * Unable to establish /usr/share/man/man1/pod2usage.1* symlink > * Unable to establish /usr/share/man/man1/podchecker.1* symlink > * Unable to establish /usr/share/man/man1/podselect.1* symlink > * Unable to establish /usr/share/man/man1/prove.1* symlink > * Unable to establish /usr/share/man/man1/pod2man.1* symlink > * Unable to establish /usr/share/man/man1/pod2text.1* symlink > > * Messages for package sys-apps/shadow-4.1.4.3: > > * Running 'grpck' returned errors. Please run it by hand, and then > * run 'grpconv' afterwards! > > * Messages for package net-misc/openssh-5.8_p1-r1: > > * Starting with openssh-5.8p1, the server will default to a newer key > * algorithm (ECDSA). You are encouraged to manually update your stored > * keys list as servers update theirs. See ssh-keyscan(1) for more info. > * Remember to merge your config files in /etc/ssh/ and then > * reload sshd: '/etc/init.d/sshd reload'. > * Please be aware users need a valid shell in /etc/passwd > * in order to be allowed to login. >>>> Auto-cleaning packages... > >>>> No outdated packages were found on your system. > > * IMPORTANT: 4 config files in '/etc' need updating. > * See the CONFIGURATION FILES section of the emerge > * man page to learn how to update config files. > > * IMPORTANT: 2 news items need reading for repository 'gentoo'. > * Use eselect news to read news items. > >(chroot)# etc-update >Scanning Configuration files... >Automerging trivial changes in: /etc/wgetrc >Automerging trivial changes in: /etc/ssh/sshd_config >The following is the list of files which need updating, each >configuration file is followed by a list of possible replacement files. >1) /etc/locale.gen (1) >2) /etc/pam.d/system-auth (1) >Please select a file to edit by entering the corresponding number. > (don't use -3, -5, -7 or -9 if you're unsure what to do) > (-1 to exit) (-3 to auto merge all remaining files) > (-5 to auto-merge AND not use 'mv -i') > (-7 to discard all updates) > (-9 to discard all updates AND not use 'rm -i'): 1 > >[?1049h[?1h=Showing differences between /etc/locale.gen and /etc/._cfg0000_locale.gen[m >--- /etc/locale.gen 2011-03-08 12:41:27.192934431 +0000[m >+++ /etc/._cfg0000_locale.gen 2011-03-07 00:12:52.000000000 +0000[m >@@ -15,8 +15,8 @@[m > # rebuilt for you. After updating this file, you can simply run `locale-gen`[m > # yourself instead of re-emerging glibc.[m > [m >-en_US ISO-8859-1[m >-en_US.UTF-8 UTF-8[m >+#en_US ISO-8859-1[m >+#en_US.UTF-8 UTF-8[m > #ja_JP.EUC-JP EUC-JP[m > #ja_JP.UTF-8 UTF-8[m > #ja_JP EUC-JP[m >[3mlines 1-14/14 (END) [23m[K[K:[K22[K[K[3mlines 1-14/14 (END) [23m[K[K[?1l>[?1049lFile: /etc/._cfg0000_locale.gen >1) Replace original with update >2) Delete update, keeping original as is >3) Interactively merge original with update >4) Show differences again >Please select from the menu above (-1 to ignore this update): 2 >Deleting /etc/._cfg0000_locale.gen >rm: remove regular file `/etc/._cfg0000_locale.gen'? y > >The following is the list of files which need updating, each >configuration file is followed by a list of possible replacement files. >2) /etc/pam.d/system-auth (1) >Please select a file to edit by entering the corresponding number. > (don't use -3, -5, -7 or -9 if you're unsure what to do) > (-1 to exit) (-3 to auto merge all remaining files) > (-5 to auto-merge AND not use 'mv -i') > (-7 to discard all updates) > (-9 to discard all updates AND not use 'rm -i'): 2 > >[?1049h[?1h=Showing differences between /etc/pam.d/system-auth and /etc/pam.d/._cfg0000_syst[m em-auth[m >--- /etc/pam.d/system-auth 2011-02-24 10:10:56.000000000 +0000[m >+++ /etc/pam.d/._cfg0000_system-auth 2011-03-01 21:09:02.000000000 +0000[m >@@ -5,8 +5,7 @@[m > account required pam_unix.so [m > account optional pam_permit.so[m > [m >-password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocred[m it=2 retry=3 [m >-password required pam_unix.so try_first_pass use_authtok nullok sh[m a512 shadow [m >+password required pam_unix.so try_first_pass nullok md5 shadow [m > password optional pam_permit.so[m > [m > session required pam_limits.so [m >[3mlines 1-13/13 (END) [23m[K[K[?1l>[?1049lFile: /etc/pam.d/._cfg0000_system-auth >1) Replace original with update >2) Delete update, keeping original as is >3) Interactively merge original with update >4) Show differences again >Please select from the menu above (-1 to ignore this update): 1 >Replacing /etc/pam.d/system-auth with /etc/pam.d/._cfg0000_system-auth >mv: overwrite `/etc/pam.d/system-auth'? y > >Exiting: Nothing left to do; exiting. :) >(chroot)# emerge --depclean --with-bdeps=n >]0;emerge > * Depclean may break link level dependencies. Thus, it is > * recommended to use a tool such as `revdep-rebuild` (from > * app-portage/gentoolkit) in order to detect such breakage. > * > * Always study the list of packages to be cleaned for any obvious > * mistakes. Packages that are part of the world set will always > * be kept. They can be manually added to this set with > * `emerge --noreplace <atom>`. Packages that are listed in > * package.provided (see portage(5)) will be removed by > * depclean, even if they are part of the world set. > * > * As a safety measure, depclean will not remove any packages > * unless *all* required dependencies have been resolved. As a > * consequence, it is often necessary to run `emerge --update > * --newuse --deep @world` prior to depclean. >!!! You have no world file. >!!! Proceeding is likely to break your installation. > >Calculating dependencies - - /... done! >>>> Calculating removal order... > > dev-libs/libpcre > selected: 8.02 > protected: none > omitted: none > > sys-libs/cracklib > selected: 2.8.16 > protected: none > omitted: none > > sys-apps/tcp-wrappers > selected: 7.6-r8 > protected: none > omitted: none > > sys-devel/gettext > selected: 0.18.1.1-r1 > protected: none > omitted: none > > dev-libs/libxml2 > selected: 2.7.8 > protected: none > omitted: none > > virtual/acl > selected: 0 > protected: none > omitted: none > > dev-vcs/git > selected: 1.7.3.4-r1 > protected: none > omitted: none > > sys-apps/acl > selected: 2.2.49 > protected: none > omitted: none > > dev-perl/Error > selected: 0.170.160 > protected: none > omitted: none > > dev-perl/Authen-SASL > selected: 2.15 > protected: none > omitted: none > > net-misc/curl > selected: 7.20.0-r2 > protected: none > omitted: none > > dev-perl/Net-SMTP-SSL > selected: 1.01 > protected: none > omitted: none > > dev-lang/python > selected: 2.6.6-r1 > protected: none > omitted: 3.1.3-r1 > > dev-perl/Digest-HMAC > selected: 1.01-r1 > protected: none > omitted: none > > sys-libs/gdbm > selected: 1.8.3-r4 > protected: none > omitted: none > > sys-apps/attr > selected: 2.4.44 > protected: none > omitted: none > > virtual/perl-libnet > selected: 1.22 > protected: none > omitted: none > > dev-perl/IO-Socket-SSL > selected: 1.35 > protected: none > omitted: none > > virtual/perl-Digest-MD5 > selected: 2.39 > protected: none > omitted: none > > dev-perl/Net-SSLeay > selected: 1.36 > protected: none > omitted: none > > dev-perl/Digest-SHA1 > selected: 2.12 > protected: none > omitted: none > > sys-libs/db > selected: 4.8.30 > protected: none > omitted: none > > virtual/perl-Scalar-List-Utils > selected: 1.23 > protected: none > omitted: none > > perl-core/Scalar-List-Utils > selected: 1.23 > protected: none > omitted: none > > virtual/perl-digest-base > selected: 1.16 > protected: none > omitted: none > >All selected packages: perl-core/Scalar-List-Utils-1.23 sys-apps/attr-2.4.44 virtual/acl-0 sys-apps/acl-2.2.49 net-misc/curl-7.20.0-r2 dev-libs/libxml2-2.7.8 dev-perl/Net-SMTP-SSL-1.01 dev-vcs/git-1.7.3.4-r1 dev-perl/Authen-SASL-2.15 virtual/perl-Digest-MD5-2.39 sys-libs/gdbm-1.8.3-r4 dev-libs/libpcre-8.02 sys-apps/tcp-wrappers-7.6-r8 dev-perl/Error-0.170.160 virtual/perl-digest-base-1.16 dev-lang/python-2.6.6-r1 dev-perl/Digest-SHA1-2.12 sys-libs/cracklib-2.8.16 dev-perl/IO-Socket-SSL-1.35 sys-devel/gettext-0.18.1.1-r1 dev-perl/Digest-HMAC-1.01-r1 dev-perl/Net-SSLeay-1.36 virtual/perl-Scalar-List-Utils-1.23 sys-libs/db-4.8.30 virtual/perl-libnet-1.22 > >>>> 'Selected' packages are slated for removal. >>>> 'Protected' and 'omitted' packages will not be removed. > >>>> Unmerging dev-libs/libpcre-8.02... >openpty failed: 'out of pty devices' >>>> Unmerging sys-libs/cracklib-2.8.16... >>>> Unmerging sys-apps/tcp-wrappers-7.6-r8... >>>> Unmerging sys-devel/gettext-0.18.1.1-r1... >>>> Unmerging dev-libs/libxml2-2.7.8... >>>> Unmerging virtual/acl-0... >>>> Unmerging dev-vcs/git-1.7.3.4-r1... >>>> Unmerging sys-apps/acl-2.2.49... >>>> Unmerging dev-perl/Error-0.170.160... >>>> Unmerging dev-perl/Authen-SASL-2.15... >>>> Unmerging net-misc/curl-7.20.0-r2... >>>> Unmerging dev-perl/Net-SMTP-SSL-1.01... >>>> Unmerging dev-lang/python-2.6.6-r1... >!!! FAILED postrm: 1 >>>> Unmerging dev-perl/Digest-HMAC-1.01-r1... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging sys-libs/gdbm-1.8.3-r4... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging sys-apps/attr-2.4.44... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging virtual/perl-libnet-1.22... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging dev-perl/IO-Socket-SSL-1.35... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging virtual/perl-Digest-MD5-2.39... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging dev-perl/Net-SSLeay-1.36... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging dev-perl/Digest-SHA1-2.12... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging sys-libs/db-4.8.30... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging virtual/perl-Scalar-List-Utils-1.23... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging perl-core/Scalar-List-Utils-1.23... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >>>> Unmerging virtual/perl-digest-base-1.16... >!!! FAILED prerm: 1 >!!! FAILED postrm: 1 >Packages installed: 87 >Packages in world: 0 >Packages in system: 51 >Required packages: 87 >Number removed: 25 > > * Messages for package dev-lang/python-2.6.6-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 'dev-lang/python-2.6.6-r1' package has failed > * with exit value 1. > * > * The problem occurred while executing the ebuild file named > * 'python-2.6.6-r1.ebuild' located in the '/var/db/pkg/dev- > * lang/python-2.6.6-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. > * ERROR: dev-lang/python-2.6.6-r1 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-lang/python-2.6.6-r1', > * the complete build log and the output of 'emerge -pqv =dev-lang/python-2.6.6-r1'. > * The complete build log is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/environment'. > * S: '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/work/python-2.6.6' > * ERROR: dev-lang/python-2.6.6-r1 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-lang/python-2.6.6-r1', > * the complete build log and the output of 'emerge -pqv =dev-lang/python-2.6.6-r1'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/environment'. > * S: '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/work/python-2.6.6' > > * Messages for package dev-perl/Digest-HMAC-1.01-r1: > > * 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. > * ERROR: dev-perl/Digest-HMAC-1.01-r1 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Digest-HMAC-1.01-r1', > * the complete build log and the output of 'emerge -pqv =dev-perl/Digest-HMAC-1.01-r1'. > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/work/Digest-HMAC-1.01' > * 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 'dev-perl/Digest-HMAC-1.01-r1' package has > * failed with exit value 1. > * > * The problem occurred while executing the ebuild file named 'Digest- > * HMAC-1.01-r1.ebuild' located in the '/var/db/pkg/dev-perl/Digest- > * HMAC-1.01-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. > * ERROR: dev-perl/Digest-HMAC-1.01-r1 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Digest-HMAC-1.01-r1', > * the complete build log and the output of 'emerge -pqv =dev-perl/Digest-HMAC-1.01-r1'. > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/work/Digest-HMAC-1.01' > * ERROR: dev-perl/Digest-HMAC-1.01-r1 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Digest-HMAC-1.01-r1', > * the complete build log and the output of 'emerge -pqv =dev-perl/Digest-HMAC-1.01-r1'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/work/Digest-HMAC-1.01' > * ERROR: dev-perl/Digest-HMAC-1.01-r1 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Digest-HMAC-1.01-r1', > * the complete build log and the output of 'emerge -pqv =dev-perl/Digest-HMAC-1.01-r1'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Digest-HMAC-1.01-r1/work/Digest-HMAC-1.01' > > * Messages for package sys-libs/gdbm-1.8.3-r4: > > * 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. > * ERROR: sys-libs/gdbm-1.8.3-r4 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-libs/gdbm-1.8.3-r4', > * the complete build log and the output of 'emerge -pqv =sys-libs/gdbm-1.8.3-r4'. > * The complete build log is located at '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/temp/environment'. > * S: '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/work/gdbm-1.8.3' > * 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/gdbm-1.8.3-r4' package has failed > * with exit value 1. > * > * The problem occurred while executing the ebuild file named > * 'gdbm-1.8.3-r4.ebuild' located in the '/var/db/pkg/sys- > * libs/gdbm-1.8.3-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. > * ERROR: sys-libs/gdbm-1.8.3-r4 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-libs/gdbm-1.8.3-r4', > * the complete build log and the output of 'emerge -pqv =sys-libs/gdbm-1.8.3-r4'. > * The complete build log is located at '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/temp/environment'. > * S: '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/work/gdbm-1.8.3' > * ERROR: sys-libs/gdbm-1.8.3-r4 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-libs/gdbm-1.8.3-r4', > * the complete build log and the output of 'emerge -pqv =sys-libs/gdbm-1.8.3-r4'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/temp/environment'. > * S: '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/work/gdbm-1.8.3' > * ERROR: sys-libs/gdbm-1.8.3-r4 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-libs/gdbm-1.8.3-r4', > * the complete build log and the output of 'emerge -pqv =sys-libs/gdbm-1.8.3-r4'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/temp/environment'. > * S: '/var/tmp/binpkgs/sys-libs/gdbm-1.8.3-r4/work/gdbm-1.8.3' > > * Messages for package sys-apps/attr-2.4.44: > > * 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. > * ERROR: sys-apps/attr-2.4.44 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-apps/attr-2.4.44', > * the complete build log and the output of 'emerge -pqv =sys-apps/attr-2.4.44'. > * The complete build log is located at '/var/tmp/binpkgs/sys-apps/attr-2.4.44/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-apps/attr-2.4.44/temp/environment'. > * S: '/var/tmp/binpkgs/sys-apps/attr-2.4.44/work/attr-2.4.44' > * 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-apps/attr-2.4.44' package has failed with > * exit value 1. > * > * The problem occurred while executing the ebuild file named > * 'attr-2.4.44.ebuild' located in the '/var/db/pkg/sys-apps/attr-2.4.44' > * 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. > * ERROR: sys-apps/attr-2.4.44 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-apps/attr-2.4.44', > * the complete build log and the output of 'emerge -pqv =sys-apps/attr-2.4.44'. > * The complete build log is located at '/var/tmp/binpkgs/sys-apps/attr-2.4.44/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-apps/attr-2.4.44/temp/environment'. > * S: '/var/tmp/binpkgs/sys-apps/attr-2.4.44/work/attr-2.4.44' > * ERROR: sys-apps/attr-2.4.44 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-apps/attr-2.4.44', > * the complete build log and the output of 'emerge -pqv =sys-apps/attr-2.4.44'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/sys-apps/attr-2.4.44/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-apps/attr-2.4.44/temp/environment'. > * S: '/var/tmp/binpkgs/sys-apps/attr-2.4.44/work/attr-2.4.44' > * ERROR: sys-apps/attr-2.4.44 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-apps/attr-2.4.44', > * the complete build log and the output of 'emerge -pqv =sys-apps/attr-2.4.44'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/sys-apps/attr-2.4.44/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-apps/attr-2.4.44/temp/environment'. > * S: '/var/tmp/binpkgs/sys-apps/attr-2.4.44/work/attr-2.4.44' > > * Messages for package virtual/perl-libnet-1.22: > > * 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. > * ERROR: virtual/perl-libnet-1.22 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-libnet-1.22', > * the complete build log and the output of 'emerge -pqv =virtual/perl-libnet-1.22'. > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-libnet-1.22/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-libnet-1.22/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-libnet-1.22/work/perl-libnet-1.22' > * 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.22' package has failed > * with exit value 1. > * > * The problem occurred while executing the ebuild file named 'perl- > * libnet-1.22.ebuild' located in the '/var/db/pkg/virtual/perl- > * libnet-1.22' 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. > * ERROR: virtual/perl-libnet-1.22 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-libnet-1.22', > * the complete build log and the output of 'emerge -pqv =virtual/perl-libnet-1.22'. > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-libnet-1.22/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-libnet-1.22/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-libnet-1.22/work/perl-libnet-1.22' > * ERROR: virtual/perl-libnet-1.22 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-libnet-1.22', > * the complete build log and the output of 'emerge -pqv =virtual/perl-libnet-1.22'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-libnet-1.22/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-libnet-1.22/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-libnet-1.22/work/perl-libnet-1.22' > * ERROR: virtual/perl-libnet-1.22 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-libnet-1.22', > * the complete build log and the output of 'emerge -pqv =virtual/perl-libnet-1.22'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-libnet-1.22/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-libnet-1.22/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-libnet-1.22/work/perl-libnet-1.22' > > * Messages for package dev-perl/IO-Socket-SSL-1.35: > > * 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. > * ERROR: dev-perl/IO-Socket-SSL-1.35 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/IO-Socket-SSL-1.35', > * the complete build log and the output of 'emerge -pqv =dev-perl/IO-Socket-SSL-1.35'. > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/work/IO-Socket-SSL-1.35' > * 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 'dev-perl/IO-Socket-SSL-1.35' package has > * failed with exit value 1. > * > * The problem occurred while executing the ebuild file named 'IO-Socket- > * SSL-1.35.ebuild' located in the '/var/db/pkg/dev-perl/IO-Socket- > * SSL-1.35' 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. > * ERROR: dev-perl/IO-Socket-SSL-1.35 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/IO-Socket-SSL-1.35', > * the complete build log and the output of 'emerge -pqv =dev-perl/IO-Socket-SSL-1.35'. > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/work/IO-Socket-SSL-1.35' > * ERROR: dev-perl/IO-Socket-SSL-1.35 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/IO-Socket-SSL-1.35', > * the complete build log and the output of 'emerge -pqv =dev-perl/IO-Socket-SSL-1.35'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/work/IO-Socket-SSL-1.35' > * ERROR: dev-perl/IO-Socket-SSL-1.35 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/IO-Socket-SSL-1.35', > * the complete build log and the output of 'emerge -pqv =dev-perl/IO-Socket-SSL-1.35'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/IO-Socket-SSL-1.35/work/IO-Socket-SSL-1.35' > > * Messages for package virtual/perl-Digest-MD5-2.39: > > * 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. > * ERROR: virtual/perl-Digest-MD5-2.39 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-Digest-MD5-2.39', > * the complete build log and the output of 'emerge -pqv =virtual/perl-Digest-MD5-2.39'. > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/work/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. > * ERROR: virtual/perl-Digest-MD5-2.39 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-Digest-MD5-2.39', > * the complete build log and the output of 'emerge -pqv =virtual/perl-Digest-MD5-2.39'. > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/work/perl-Digest-MD5-2.39' > * ERROR: virtual/perl-Digest-MD5-2.39 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-Digest-MD5-2.39', > * the complete build log and the output of 'emerge -pqv =virtual/perl-Digest-MD5-2.39'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/work/perl-Digest-MD5-2.39' > * ERROR: virtual/perl-Digest-MD5-2.39 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-Digest-MD5-2.39', > * the complete build log and the output of 'emerge -pqv =virtual/perl-Digest-MD5-2.39'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-Digest-MD5-2.39/work/perl-Digest-MD5-2.39' > > * Messages for package dev-perl/Net-SSLeay-1.36: > > * 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. > * ERROR: dev-perl/Net-SSLeay-1.36 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Net-SSLeay-1.36', > * the complete build log and the output of 'emerge -pqv =dev-perl/Net-SSLeay-1.36'. > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/work/Net-SSLeay-1.36' > * 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 'dev-perl/Net-SSLeay-1.36' package has failed > * with exit value 1. > * > * The problem occurred while executing the ebuild file named 'Net- > * SSLeay-1.36.ebuild' located in the '/var/db/pkg/dev-perl/Net- > * SSLeay-1.36' 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. > * ERROR: dev-perl/Net-SSLeay-1.36 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Net-SSLeay-1.36', > * the complete build log and the output of 'emerge -pqv =dev-perl/Net-SSLeay-1.36'. > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/work/Net-SSLeay-1.36' > * ERROR: dev-perl/Net-SSLeay-1.36 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Net-SSLeay-1.36', > * the complete build log and the output of 'emerge -pqv =dev-perl/Net-SSLeay-1.36'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/work/Net-SSLeay-1.36' > * ERROR: dev-perl/Net-SSLeay-1.36 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Net-SSLeay-1.36', > * the complete build log and the output of 'emerge -pqv =dev-perl/Net-SSLeay-1.36'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Net-SSLeay-1.36/work/Net-SSLeay-1.36' > > * Messages for package dev-perl/Digest-SHA1-2.12: > > * 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. > * ERROR: dev-perl/Digest-SHA1-2.12 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Digest-SHA1-2.12', > * the complete build log and the output of 'emerge -pqv =dev-perl/Digest-SHA1-2.12'. > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/work/Digest-SHA1-2.12' > * 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 'dev-perl/Digest-SHA1-2.12' package has failed > * with exit value 1. > * > * The problem occurred while executing the ebuild file named 'Digest- > * SHA1-2.12.ebuild' located in the '/var/db/pkg/dev-perl/Digest-SHA1-2.12' > * 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. > * ERROR: dev-perl/Digest-SHA1-2.12 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Digest-SHA1-2.12', > * the complete build log and the output of 'emerge -pqv =dev-perl/Digest-SHA1-2.12'. > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/work/Digest-SHA1-2.12' > * ERROR: dev-perl/Digest-SHA1-2.12 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Digest-SHA1-2.12', > * the complete build log and the output of 'emerge -pqv =dev-perl/Digest-SHA1-2.12'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/work/Digest-SHA1-2.12' > * ERROR: dev-perl/Digest-SHA1-2.12 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =dev-perl/Digest-SHA1-2.12', > * the complete build log and the output of 'emerge -pqv =dev-perl/Digest-SHA1-2.12'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/temp/environment'. > * S: '/var/tmp/binpkgs/dev-perl/Digest-SHA1-2.12/work/Digest-SHA1-2.12' > > * Messages for package sys-libs/db-4.8.30: > > * 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. > * ERROR: sys-libs/db-4.8.30 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-libs/db-4.8.30', > * the complete build log and the output of 'emerge -pqv =sys-libs/db-4.8.30'. > * The complete build log is located at '/var/tmp/binpkgs/sys-libs/db-4.8.30/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-libs/db-4.8.30/temp/environment'. > * S: '/var/tmp/binpkgs/sys-libs/db-4.8.30/work/db-4.8.30' > * 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/db-4.8.30' package has failed with > * exit value 1. > * > * The problem occurred while executing the ebuild file named > * 'db-4.8.30.ebuild' located in the '/var/db/pkg/sys-libs/db-4.8.30' > * 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. > * ERROR: sys-libs/db-4.8.30 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-libs/db-4.8.30', > * the complete build log and the output of 'emerge -pqv =sys-libs/db-4.8.30'. > * The complete build log is located at '/var/tmp/binpkgs/sys-libs/db-4.8.30/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-libs/db-4.8.30/temp/environment'. > * S: '/var/tmp/binpkgs/sys-libs/db-4.8.30/work/db-4.8.30' > * ERROR: sys-libs/db-4.8.30 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-libs/db-4.8.30', > * the complete build log and the output of 'emerge -pqv =sys-libs/db-4.8.30'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/sys-libs/db-4.8.30/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-libs/db-4.8.30/temp/environment'. > * S: '/var/tmp/binpkgs/sys-libs/db-4.8.30/work/db-4.8.30' > * ERROR: sys-libs/db-4.8.30 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =sys-libs/db-4.8.30', > * the complete build log and the output of 'emerge -pqv =sys-libs/db-4.8.30'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/sys-libs/db-4.8.30/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/sys-libs/db-4.8.30/temp/environment'. > * S: '/var/tmp/binpkgs/sys-libs/db-4.8.30/work/db-4.8.30' > > * Messages for package virtual/perl-Scalar-List-Utils-1.23: > > * 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. > * ERROR: virtual/perl-Scalar-List-Utils-1.23 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-Scalar-List-Utils-1.23', > * the complete build log and the output of 'emerge -pqv =virtual/perl-Scalar-List-Utils-1.23'. > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/work/perl-Scalar-List-Utils-1.23' > * 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.23' package > * has failed with exit value 1. > * > * The problem occurred while executing the ebuild file named 'perl-Scalar- > * List-Utils-1.23.ebuild' located in the '/var/db/pkg/virtual/perl-Scalar- > * List-Utils-1.23' 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. > * ERROR: virtual/perl-Scalar-List-Utils-1.23 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-Scalar-List-Utils-1.23', > * the complete build log and the output of 'emerge -pqv =virtual/perl-Scalar-List-Utils-1.23'. > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/work/perl-Scalar-List-Utils-1.23' > * ERROR: virtual/perl-Scalar-List-Utils-1.23 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-Scalar-List-Utils-1.23', > * the complete build log and the output of 'emerge -pqv =virtual/perl-Scalar-List-Utils-1.23'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/work/perl-Scalar-List-Utils-1.23' > * ERROR: virtual/perl-Scalar-List-Utils-1.23 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-Scalar-List-Utils-1.23', > * the complete build log and the output of 'emerge -pqv =virtual/perl-Scalar-List-Utils-1.23'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-Scalar-List-Utils-1.23/work/perl-Scalar-List-Utils-1.23' > > * Messages for package perl-core/Scalar-List-Utils-1.23: > > * 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. > * ERROR: perl-core/Scalar-List-Utils-1.23 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =perl-core/Scalar-List-Utils-1.23', > * the complete build log and the output of 'emerge -pqv =perl-core/Scalar-List-Utils-1.23'. > * The complete build log is located at '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/temp/environment'. > * S: '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/work/Scalar-List-Utils-1.23' > * 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 'perl-core/Scalar-List-Utils-1.23' package has > * failed with exit value 1. > * > * The problem occurred while executing the ebuild file named 'Scalar-List- > * Utils-1.23.ebuild' located in the '/var/db/pkg/perl-core/Scalar-List- > * Utils-1.23' 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. > * ERROR: perl-core/Scalar-List-Utils-1.23 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =perl-core/Scalar-List-Utils-1.23', > * the complete build log and the output of 'emerge -pqv =perl-core/Scalar-List-Utils-1.23'. > * The complete build log is located at '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/temp/environment'. > * S: '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/work/Scalar-List-Utils-1.23' > * ERROR: perl-core/Scalar-List-Utils-1.23 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =perl-core/Scalar-List-Utils-1.23', > * the complete build log and the output of 'emerge -pqv =perl-core/Scalar-List-Utils-1.23'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/temp/environment'. > * S: '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/work/Scalar-List-Utils-1.23' > * ERROR: perl-core/Scalar-List-Utils-1.23 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =perl-core/Scalar-List-Utils-1.23', > * the complete build log and the output of 'emerge -pqv =perl-core/Scalar-List-Utils-1.23'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/temp/environment'. > * S: '/var/tmp/binpkgs/perl-core/Scalar-List-Utils-1.23/work/Scalar-List-Utils-1.23' > > * Messages for package virtual/perl-digest-base-1.16: > > * 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. > * ERROR: virtual/perl-digest-base-1.16 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-digest-base-1.16', > * the complete build log and the output of 'emerge -pqv =virtual/perl-digest-base-1.16'. > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/work/perl-digest-base-1.16' > * 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-base-1.16' package has > * failed with exit value 1. > * > * The problem occurred while executing the ebuild file named 'perl-digest- > * base-1.16.ebuild' located in the '/var/db/pkg/virtual/perl-digest- > * base-1.16' 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. > * ERROR: virtual/perl-digest-base-1.16 failed: > * filter-bash-environment.py failed > * > * Call stack: > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-digest-base-1.16', > * the complete build log and the output of 'emerge -pqv =virtual/perl-digest-base-1.16'. > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/work/perl-digest-base-1.16' > * ERROR: virtual/perl-digest-base-1.16 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-digest-base-1.16', > * the complete build log and the output of 'emerge -pqv =virtual/perl-digest-base-1.16'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/work/perl-digest-base-1.16' > * ERROR: virtual/perl-digest-base-1.16 failed: > * filter-bash-environment.py failed > * > * Call stack: > * misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh' > * ebuild.sh, line 1926: Called preprocess_ebuild_env > * ebuild.sh, line 1813: Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' > * ebuild.sh, line 1794: Called die > * The specific snippet of code: > * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed" > * > * If you need support, post the output of 'emerge --info =virtual/perl-digest-base-1.16', > * the complete build log and the output of 'emerge -pqv =virtual/perl-digest-base-1.16'. > * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/' > * The complete build log is located at '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/temp/environment'. > * S: '/var/tmp/binpkgs/virtual/perl-digest-base-1.16/work/perl-digest-base-1.16' > > * IMPORTANT: 2 news items need reading for repository 'gentoo'. > * Use eselect news to read news items. > >(chroot)# emerge >(chroot)# python >(chroot)# eselect python list >[32m[1mAvailable Python interpreters:[m > [1m[1][m [mpython3.1[m >(chroot)#
<b>You cannot view the attachment while viewing its details because your browser does not support IFRAMEs. <a href="attachment.cgi?id=265149">View the attachment on a separate page</a>.</b>
View Attachment As Raw
Actions:
View
Attachments on
bug 357009
:
264299
| 265149
