This week only. Pastebin PRO Accounts Christmas Special! Don't miss out!Want more features on Pastebin? Sign Up, it's FREE!
Guest

gentoo-sources emerge

By: a guest on Dec 22nd, 2011  |  syntax: Bash  |  size: 66.40 KB  |  views: 104  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. <<[CHROOT]sabayon / # >> eselect profile list
  2. Available profile symlink targets:
  3.   [1]   default/linux/amd64/10.0 *
  4.   [2]   default/linux/amd64/10.0/selinux
  5.   [3]   default/linux/amd64/10.0/desktop
  6.   [4]   default/linux/amd64/10.0/desktop/gnome
  7.   [5]   default/linux/amd64/10.0/desktop/kde
  8.   [6]   default/linux/amd64/10.0/developer
  9.   [7]   default/linux/amd64/10.0/no-multilib
  10.   [8]   default/linux/amd64/10.0/server
  11.   [9]   hardened/linux/amd64
  12.   [10]  hardened/linux/amd64/selinux
  13.   [11]  hardened/linux/amd64/no-multilib
  14.   [12]  hardened/linux/amd64/no-multilib/selinux
  15. <<[CHROOT]sabayon / # >> cat /etc/make.conf
  16. # These settings were set by the catalyst build script that automatically
  17. # built this stage.
  18. # Please consult /etc/make.conf.example for a more detailed example.
  19. CFLAGS="-O2 -pipe -march=nocona"
  20. #CFLAGS="-O2 -pipe -march=native"
  21. CXXFLAGS="${CFLAGS}"
  22.  
  23. # This should not be changed unless you know exactly what you are doing.  You
  24. # should probably be using a different stage, instead.
  25. CHOST="x86_64-pc-linux-gnu"
  26. MAKEOPTS="-j1"
  27. PORTAGE_NICENESS=5
  28.  
  29. # PLEASE NOTE: this USE statement has customised for use on TAD - Please do NOT use it elsewhere!
  30.  
  31. USE="xmlreader -mysql -postgres -perl ssl -apache2 -curl -gd -gdbm jpeg -pdflib -png -tiff -freetds -X -gnome -gtk -gtk2 -kde -oss -alsa -qt -truetype -ipv6 -cups -sdl urandom"
  32.  
  33. APACHE2_MODULES="actions alias auth_basic auth_digest authn_alias authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias"
  34.  
  35. # This will select the correct version of PECL modules etc
  36. PHP_TARGETS="php5-2"
  37. EMERGE_DEFAULT_OPTS="--autounmask=n"
  38.  
  39. GENTOO_MIRRORS="ftp://mirror.bytemark.co.uk/gentoo/ http://mirror.bytemark.co.uk/gentoo/ rsync://mirror.bytemark.co.uk/gentoo/ ftp://mirror.qubenet.net/mirror/gentoo/ http://mirror.qubenet.net/mirror/gentoo/ rsync://rsync.mirrorservice.org/www.ibiblio.org/gentoo/ http://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/ ftp://ftp.mirrorservice.org/sites/www.ibiblio.org/gentoo/"
  40. SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage"
  41.  
  42. <<[CHROOT]sabayon / # >> cp /home/marcusw/savedstuff/etc/locale.gen /etc/
  43. <<[CHROOT]sabayon / # >> locale-gen
  44.  * No locales found
  45. <<[CHROOT]sabayon / # >> cp /home/marcusw/savedstuff/etc/localtime /etc/
  46. <<[CHROOT]sabayon / # >> emerge gentoo-sources
  47.  
  48.  * IMPORTANT: 5 news items need reading for repository 'gentoo'.
  49.  * Use eselect news to read news items.
  50.  
  51. Calculating dependencies... done!
  52.  
  53. >>> Verifying ebuild manifests
  54.  
  55. >>> Emerging (1 of 1) sys-kernel/gentoo-sources-3.0.6
  56.  * linux-3.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                               [ ok ]
  57.  * genpatches-3.0-8.base.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                   [ ok ]
  58.  * genpatches-3.0-8.extras.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                 [ ok ]
  59. >>> Preparing to unpack ...
  60. >>> Unpacking source...
  61. >>> Unpacking linux-3.0.tar.bz2 to /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work
  62. >>> Unpacking genpatches-3.0-8.base.tar.bz2 to /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/patches
  63. >>> Unpacking genpatches-3.0-8.extras.tar.bz2 to /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/patches
  64.  * Applying 1000_linux-3.0.1.patch (-p0+) ...                                                                      [ ok ]
  65.  * Applying 1001_linux-3.0.2.patch (-p0+) ...                                                                      [ ok ]
  66.  * Applying 1002_linux-3.0.3.patch (-p0+) ...                                                                      [ ok ]
  67.  * Applying 1003_linux-3.0.4.patch (-p0+) ...                                                                      [ ok ]
  68.  * Applying 1004_linux-3.0.5.patch (-p0+) ...                                                                      [ ok ]
  69.  * Applying 1005_linux-3.0.6.patch (-p0+) ...                                                                      [ ok ]
  70.  * Applying 1700_i386-bigsmp-early-lapicid-override.patch (-p0+) ...                                               [ ok ]
  71.  * Applying 1800_fix-zcache-build.patch (-p0+) ...                                                                 [ ok ]
  72.  * Applying 2600_Input-ALPS-Move-protocol-information-to-Documentation.patch (-p0+) ...                            [ ok ]
  73.  * Applying 2605_Input-psmouse-Add-PSMOUSE_CMD_RESET_WRAP.patch (-p0+) ...                                         [ ok ]
  74.  * Applying 2610_Input-ALPS-Add-protocol-version-field-in-alps_model.patch (-p0+) ...                              [ ok ]
  75.  * Applying 2615_Input-ALPS-Remove-assumptions-about-packet-size.patch (-p0+) ...                                  [ ok ]
  76.  * Applying 2620_Input-ALPS-Add-support-for-protocol-versions-3-and-4.patch (-p0+) ...                             [ ok ]
  77.  * Applying 2625_Input-ALPS-Add-documentation-for-protocol-versions-3.patch (-p0+) ...                             [ ok ]
  78.  * Applying 2630_Input-ALPS-Add-semi-MT-support-for-v3-protocol.patch (-p0+) ...                                   [ ok ]
  79.  * Applying 2635_Input-ALPS-dump-raw-packet-data.patch (-p0+) ...                                                  [ ok ]
  80.  * Applying 2900_change-dvb-firmware-url.patch (-p0+) ...                                                          [ ok ]
  81.  * Applying 4200_fbcondecor-0.9.6.patch (-p0+) ...                                                                 [ ok ]
  82. >>> Source unpacked in /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work
  83. >>> Preparing source in /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/linux-3.0.6-gentoo ...
  84. >>> Source prepared.
  85. >>> Configuring source in /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/linux-3.0.6-gentoo ...
  86. >>> Source configured.
  87. >>> Compiling source in /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/work/linux-3.0.6-gentoo ...
  88. >>> Source compiled.
  89. >>> Test phase [not enabled]: sys-kernel/gentoo-sources-3.0.6
  90.  
  91. >>> Install gentoo-sources-3.0.6 into /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/image/ category sys-kernel
  92. >>> Copying sources ...
  93. >>> Completed installing gentoo-sources-3.0.6 into /var/tmp/portage/sys-kernel/gentoo-sources-3.0.6/image/
  94.  
  95.  
  96. >>> Installing (1 of 1) sys-kernel/gentoo-sources-3.0.6
  97.  
  98.  * If you are upgrading from a previous kernel, you may be interested
  99.  * in the following document:
  100.  *   - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml
  101.  
  102.  * For more info on this patchset, and how to report problems, see:
  103.  * http://dev.gentoo.org/~mpagano/genpatches
  104.  
  105. >>> Recording sys-kernel/gentoo-sources in "world" favorites file...
  106.  
  107.  * Messages for package sys-kernel/gentoo-sources-3.0.6:
  108.  
  109.  * If you are upgrading from a previous kernel, you may be interested
  110.  * in the following document:
  111.  *   - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml
  112. >>> Auto-cleaning packages...
  113.  
  114.  app-admin/eselect
  115.     selected: 1.2.15
  116.    protected: 1.2.10
  117.      omitted: none
  118.  
  119.  app-arch/gzip
  120.     selected: 1.4
  121.    protected: 1.3.12-r1
  122.      omitted: none
  123.  
  124.  app-arch/tar
  125.     selected: 1.23-r2
  126.    protected: 1.19-r1
  127.      omitted: none
  128.  
  129.  app-editors/nano
  130.     selected: 2.2.5
  131.    protected: 2.0.7
  132.      omitted: none
  133.  
  134.  app-misc/ca-certificates
  135.     selected: 20110502-r1
  136.    protected: 20111025
  137.      omitted: none
  138.  
  139.  app-shells/bash
  140.     selected: 4.1_p9
  141.    protected: 3.2_p33
  142.      omitted: none
  143.  
  144.  dev-lang/perl
  145.     selected: 5.12.4-r1
  146.    protected: 5.12.3-r1
  147.      omitted: none
  148.  
  149.  dev-libs/gmp
  150.     selected: 5.0.2
  151.    protected: 5.0.2_p1
  152.      omitted: none
  153.  
  154.  dev-libs/libxml2
  155.     selected: 2.7.8-r3
  156.    protected: 2.7.8
  157.      omitted: none
  158.  
  159.  dev-libs/openssl
  160.     selected: 1.0.0e
  161.    protected: 0.9.8o
  162.      omitted: none
  163.  
  164.  dev-libs/popt
  165.     selected: 1.10.7
  166.    protected: 1.16-r1
  167.      omitted: none
  168.  
  169.  net-misc/curl
  170.     selected: 7.21.4
  171.    protected: 7.17.1
  172.      omitted: none
  173.  
  174.  net-misc/iputils
  175.     selected: 20100418-r1
  176.    protected: 20071127
  177.      omitted: none
  178.  
  179.  net-misc/openssh
  180.     selected: 5.8_p1-r1
  181.    protected: 4.7_p1-r6
  182.      omitted: none
  183.  
  184.  net-misc/wget
  185.     selected: 1.12-r3
  186.    protected: 1.11.1
  187.      omitted: none
  188.  
  189.  perl-core/Scalar-List-Utils
  190.     selected: 1.230.0
  191.    protected: 1.19
  192.      omitted: none
  193.  
  194.  sys-apps/acl
  195.     selected: 2.2.51
  196.    protected: 2.2.45
  197.      omitted: none
  198.  
  199.  sys-apps/attr
  200.     selected: 2.4.32
  201.    protected: 2.4.46
  202.      omitted: none
  203.  
  204.  sys-apps/busybox
  205.     selected: 1.19.0
  206.    protected: 1.8.2
  207.      omitted: none
  208.  
  209.  sys-apps/coreutils
  210.     selected: 8.7
  211.    protected: 6.10-r2
  212.      omitted: none
  213.  
  214.  sys-apps/diffutils
  215.     selected: 3.0
  216.    protected: 2.8.7-r2
  217.      omitted: none
  218.  
  219.  sys-apps/file
  220.     selected: 5.07-r3
  221.    protected: 5.09
  222.      omitted: none
  223.  
  224.  sys-apps/gawk
  225.     selected: 3.1.8
  226.    protected: 3.1.5-r5
  227.      omitted: none
  228.  
  229.  sys-apps/grep
  230.     selected: 2.5.4-r1
  231.    protected: 2.5.1a-r1
  232.      omitted: none
  233.  
  234.  sys-apps/groff
  235.     selected: 1.19.2-r1
  236.    protected: 1.21
  237.      omitted: none
  238.  
  239.  sys-apps/kbd
  240.     selected: 1.15.3
  241.    protected: 1.13-r1
  242.      omitted: none
  243.  
  244.  sys-apps/less
  245.     selected: 444
  246.    protected: 418
  247.      omitted: none
  248.  
  249.  sys-apps/man
  250.     selected: 1.6f-r1
  251.    protected: 1.6f-r4
  252.      omitted: none
  253.  
  254.  sys-apps/portage
  255.     selected: 2.1.10.11
  256.    protected: 2.1.10.41
  257.      omitted: none
  258.  
  259.  sys-apps/sed
  260.     selected: 4.2.1
  261.    protected: 4.1.5-r1
  262.      omitted: none
  263.  
  264.  sys-apps/shadow
  265.     selected: 4.1.4.3
  266.    protected: 4.0.18.2
  267.      omitted: none
  268.  
  269.  sys-apps/texinfo
  270.     selected: 4.13
  271.    protected: 4.11-r1
  272.      omitted: none
  273.  
  274.  sys-apps/util-linux
  275.     selected: 2.19.1-r1
  276.    protected: 2.13.1.1
  277.      omitted: none
  278.  
  279.  sys-devel/gettext
  280.     selected: 0.18.1.1-r1
  281.    protected: 0.17-r1
  282.      omitted: none
  283.  
  284.  sys-devel/make
  285.     selected: 3.81
  286.    protected: 3.82-r1
  287.      omitted: none
  288.  
  289.  sys-fs/e2fsprogs
  290.     selected: 1.41.14
  291.    protected: 1.40.8
  292.      omitted: none
  293.  
  294.  sys-fs/udev
  295.     selected: 164-r2
  296.    protected: 119
  297.      omitted: none
  298.  
  299.  sys-libs/gdbm
  300.     selected: 1.8.3-r3
  301.    protected: 1.8.3-r4
  302.      omitted: none
  303.  
  304.  sys-libs/glibc
  305.     selected: 2.13-r4
  306.    protected: 2.10.1-r1
  307.      omitted: none
  308.  
  309.  sys-libs/ncurses
  310.     selected: 5.6-r2
  311.    protected: 5.9
  312.      omitted: none
  313.  
  314.  sys-libs/pam
  315.     selected: 0.99.9.0
  316.    protected: 1.1.5
  317.      omitted: none
  318.  
  319.  sys-libs/readline
  320.     selected: 6.2_p1
  321.    protected: 5.2_p12-r1
  322.      omitted: none
  323.  
  324.  sys-process/psmisc
  325.     selected: 22.14
  326.    protected: 22.6
  327.      omitted: none
  328.  
  329.  virtual/perl-Digest-MD5
  330.     selected: 2.39
  331.    protected: 2.36
  332.      omitted: none
  333.  
  334.  virtual/perl-Scalar-List-Utils
  335.     selected: 1.230.0-r1
  336.    protected: 1.19
  337.      omitted: none
  338.  
  339.  virtual/perl-libnet
  340.     selected: 1.220.0-r1
  341.    protected: 1.21
  342.      omitted: none
  343.  
  344. All selected packages: sys-apps/grep-2.5.4-r1 sys-apps/attr-2.4.32 dev-libs/popt-1.10.7 sys-devel/gettext-0.18.1.1-r1 sys-libs/ncurses-5.6-r2 sys-apps/shadow-4.1.4.3 app-arch/tar-1.23-r2 sys-process/psmisc-22.14 dev-lang/perl-5.12.4-r1 virtual/perl-Scalar-List-Utils-1.230.0-r1 sys-apps/coreutils-8.7 virtual/perl-libnet-1.220.0-r1 perl-core/Scalar-List-Utils-1.230.0 sys-apps/kbd-1.15.3 virtual/perl-Digest-MD5-2.39 sys-apps/texinfo-4.13 dev-libs/gmp-5.0.2 sys-apps/groff-1.19.2-r1 net-misc/iputils-20100418-r1 sys-apps/util-linux-2.19.1-r1 sys-libs/glibc-2.13-r4 sys-apps/diffutils-3.0 net-misc/curl-7.21.4 sys-apps/portage-2.1.10.11 sys-libs/gdbm-1.8.3-r3 sys-apps/acl-2.2.51 sys-libs/readline-6.2_p1 dev-libs/libxml2-2.7.8-r3 app-admin/eselect-1.2.15 sys-libs/pam-0.99.9.0 app-misc/ca-certificates-20110502-r1 net-misc/wget-1.12-r3 app-shells/bash-4.1_p9 sys-apps/man-1.6f-r1 sys-devel/make-3.81 sys-apps/gawk-3.1.8 sys-apps/file-5.07-r3 app-arch/gzip-1.4 sys-fs/udev-164-r2 net-misc/openssh-5.8_p1-r1 sys-fs/e2fsprogs-1.41.14 dev-libs/openssl-1.0.0e sys-apps/busybox-1.19.0 sys-apps/sed-4.2.1 app-editors/nano-2.2.5 sys-apps/less-444
  345.  
  346. >>> 'Selected' packages are slated for removal.
  347. >>> 'Protected' and 'omitted' packages will not be removed.
  348.  
  349. >>> Unmerging app-admin/eselect-1.2.15...
  350. >>> Unmerging app-arch/gzip-1.4...
  351. >>> Unmerging app-arch/tar-1.23-r2...
  352. >>> Unmerging app-editors/nano-2.2.5...
  353. >>> Unmerging app-misc/ca-certificates-20110502-r1...
  354. >>> Unmerging app-shells/bash-4.1_p9...
  355. >>> Unmerging dev-lang/perl-5.12.4-r1...
  356.  * Linking /usr/bin/ptar-1.54-perl-5.12.3 to /usr/bin/ptar (relative)
  357.  * Linking /usr/share/man/man1/ptar-1.54-perl-5.12.3.1.bz2 to /usr/share/man/man1/ptar.1.bz2 (relative)
  358.  * Linking /usr/bin/ptardiff-1.54-perl-5.12.3 to /usr/bin/ptardiff (relative)
  359.  * Linking /usr/share/man/man1/ptardiff-1.54-perl-5.12.3.1.bz2 to /usr/share/man/man1/ptardiff.1.bz2 (relative)
  360.  * Linking /usr/bin/shasum-5.47-perl-5.12.3 to /usr/bin/shasum (relative)
  361.  * Linking /usr/share/man/man1/shasum-5.47-perl-5.12.3.1.bz2 to /usr/share/man/man1/shasum.1.bz2 (relative)
  362.  * Linking /usr/bin/cpan-1.9456-perl-5.12.3 to /usr/bin/cpan (relative)
  363.  * Linking /usr/share/man/man1/cpan-1.9456-perl-5.12.3.1.bz2 to /usr/share/man/man1/cpan.1.bz2 (relative)
  364.  * Linking /usr/bin/cpanp-0.90-perl-5.12.3 to /usr/bin/cpanp (relative)
  365.  * Linking /usr/share/man/man1/cpanp-0.90-perl-5.12.3.1.bz2 to /usr/share/man/man1/cpanp.1.bz2 (relative)
  366.  * Linking /usr/bin/cpan2dist-0.90-perl-5.12.3 to /usr/bin/cpan2dist (relative)
  367.  * Linking /usr/share/man/man1/cpan2dist-0.90-perl-5.12.3.1.bz2 to /usr/share/man/man1/cpan2dist.1.bz2 (relative)
  368.  * Linking /usr/bin/cpanp-run-perl-0.90-perl-5.12.3 to /usr/bin/cpanp-run-perl (relative)
  369.  * Linking /usr/bin/enc2xs-2.39-perl-5.12.3 to /usr/bin/enc2xs (relative)
  370.  * Linking /usr/share/man/man1/enc2xs-2.39-perl-5.12.3.1.bz2 to /usr/share/man/man1/enc2xs.1.bz2 (relative)
  371.  * Linking /usr/bin/piconv-2.39-perl-5.12.3 to /usr/bin/piconv (relative)
  372.  * Linking /usr/share/man/man1/piconv-2.39-perl-5.12.3.1.bz2 to /usr/share/man/man1/piconv.1.bz2 (relative)
  373.  * Linking /usr/bin/instmodsh-6.56-perl-5.12.3 to /usr/bin/instmodsh (relative)
  374.  * Linking /usr/share/man/man1/instmodsh-6.56-perl-5.12.3.1.bz2 to /usr/share/man/man1/instmodsh.1.bz2 (relative)
  375.  * Removing dead symlink /usr/bin/xsubpp
  376.  * Removing dead symlink /usr/share/man/man1/xsubpp.1.bz2
  377.  * Linking /usr/bin/config_data-0.3603-perl-5.12.3 to /usr/bin/config_data (relative)
  378.  * Linking /usr/share/man/man1/config_data-0.3603-perl-5.12.3.1.bz2 to /usr/share/man/man1/config_data.1.bz2 (relative)
  379.  * Linking /usr/bin/corelist-2.43-perl-5.12.3 to /usr/bin/corelist (relative)
  380.  * Linking /usr/share/man/man1/corelist-2.43-perl-5.12.3.1.bz2 to /usr/share/man/man1/corelist.1.bz2 (relative)
  381.  * Linking /usr/bin/pod2usage-1.37-perl-5.12.3 to /usr/bin/pod2usage (relative)
  382.  * Linking /usr/share/man/man1/pod2usage-1.37-perl-5.12.3.1.bz2 to /usr/share/man/man1/pod2usage.1.bz2 (relative)
  383.  * Linking /usr/bin/podchecker-1.37-perl-5.12.3 to /usr/bin/podchecker (relative)
  384.  * Linking /usr/share/man/man1/podchecker-1.37-perl-5.12.3.1.bz2 to /usr/share/man/man1/podchecker.1.bz2 (relative)
  385.  * Linking /usr/bin/podselect-1.37-perl-5.12.3 to /usr/bin/podselect (relative)
  386.  * Linking /usr/share/man/man1/podselect-1.37-perl-5.12.3.1.bz2 to /usr/share/man/man1/podselect.1.bz2 (relative)
  387.  * Linking /usr/bin/prove-3.17-perl-5.12.3 to /usr/bin/prove (relative)
  388.  * Linking /usr/share/man/man1/prove-3.17-perl-5.12.3.1.bz2 to /usr/share/man/man1/prove.1.bz2 (relative)
  389.  * Linking /usr/bin/pod2man-2.3.1-perl-5.12.3 to /usr/bin/pod2man (relative)
  390.  * Linking /usr/share/man/man1/pod2man-2.3.1-perl-5.12.3.1.bz2 to /usr/share/man/man1/pod2man.1.bz2 (relative)
  391.  * Linking /usr/bin/pod2text-2.3.1-perl-5.12.3 to /usr/bin/pod2text (relative)
  392.  * Linking /usr/share/man/man1/pod2text-2.3.1-perl-5.12.3.1.bz2 to /usr/share/man/man1/pod2text.1.bz2 (relative)
  393. >>> Unmerging dev-libs/gmp-5.0.2...
  394. >>> Unmerging dev-libs/libxml2-2.7.8-r3...
  395. >>> Unmerging dev-libs/openssl-1.0.0e...
  396. >>> Unmerging dev-libs/popt-1.10.7...
  397. >>> Unmerging net-misc/curl-7.21.4...
  398. >>> Unmerging net-misc/iputils-20100418-r1...
  399. >>> Unmerging net-misc/openssh-5.8_p1-r1...
  400. >>> Unmerging net-misc/wget-1.12-r3...
  401. >>> Unmerging perl-core/Scalar-List-Utils-1.230.0...
  402. >>> Unmerging sys-apps/acl-2.2.51...
  403. >>> Unmerging sys-apps/attr-2.4.32...
  404. >>> Unmerging sys-apps/busybox-1.19.0...
  405. >>> Unmerging sys-apps/coreutils-8.7...
  406. >>> Unmerging sys-apps/diffutils-3.0...
  407. >>> Unmerging sys-apps/file-5.07-r3...
  408. >>> Unmerging sys-apps/gawk-3.1.8...
  409. >>> Unmerging sys-apps/grep-2.5.4-r1...
  410. >>> Unmerging sys-apps/groff-1.19.2-r1...
  411. >>> Unmerging sys-apps/kbd-1.15.3...
  412. >>> Unmerging sys-apps/less-444...
  413. >>> Unmerging sys-apps/man-1.6f-r1...
  414. >>> Unmerging sys-apps/portage-2.1.10.11...
  415. <<< /usr/lib64/portage/pym/portage/cache/metadata_overlay.py[co]
  416. <<< /usr/lib64/portage/pym/portage/cache/util.py[co]
  417. >>> Unmerging sys-apps/sed-4.2.1...
  418. >>> Unmerging sys-apps/shadow-4.1.4.3...
  419. >>> Unmerging sys-apps/texinfo-4.13...
  420. >>> Unmerging sys-apps/util-linux-2.19.1-r1...
  421. >>> Unmerging sys-devel/gettext-0.18.1.1-r1...
  422. >>> Unmerging sys-devel/make-3.81...
  423. >>> Unmerging sys-fs/e2fsprogs-1.41.14...
  424. >>> Unmerging sys-fs/udev-164-r2...
  425. >>> Unmerging sys-libs/gdbm-1.8.3-r3...
  426. >>> Unmerging sys-libs/glibc-2.13-r4...
  427. [Errno 2] No such file or directory:
  428.    /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
  429. Traceback (most recent call last):
  430.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  431.     env, gid, groups, uid, umask, pre_exec)
  432.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  433.     os.execve(binary, myargs, env)
  434.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  435.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  436. OSError: [Errno 2] No such file or directory
  437.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  438.  * is known to be triggered by things such as failed variable assignments
  439.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  440.  * exiting, bash should have displayed an error message above. If bash did
  441.  * not produce an error message above, it's possible that the ebuild has
  442. * called `exit` when it should have called `die` instead. This behavior
  443. * may also be triggered by a corrupt bash binary or a hardware problem
  444. * such as memory or cpu malfunction. If the problem is not reproducible or
  445. * it appears to occur randomly, then it is likely to be triggered by a
  446. * hardware problem. If you suspect a hardware problem then you should try
  447. * some basic hardware diagnostics such as memtest. Please do not report
  448. * this as a bug unless it is consistently reproducible and you are sure
  449. * that your bash binary and hardware are functioning properly.
  450. [Errno 2] No such file or directory:
  451.   /usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
  452. Traceback (most recent call last):
  453.  File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  454.    env, gid, groups, uid, umask, pre_exec)
  455.  File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  456.    os.execve(binary, myargs, env)
  457.  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  458.    rval = self._func(*wrapped_args, **wrapped_kwargs)
  459. OSError: [Errno 2] No such file or directory
  460. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  461. * behavior is known to be triggered by things such as failed variable
  462. * assignments (bug #190128) or bad substitution errors (bug #200313).
  463. * Normally, before exiting, bash should have displayed an error message
  464. * above. If bash did not produce an error message above, it's possible
  465.  * that the ebuild has called `exit` when it should have called `die`
  466.  * instead. This behavior may also be triggered by a corrupt bash binary or
  467.  * a hardware problem such as memory or cpu malfunction. If the problem is
  468.  * not reproducible or it appears to occur randomly, then it is likely to
  469.  * be triggered by a hardware problem. If you suspect a hardware problem
  470.  * then you should try some basic hardware diagnostics such as memtest.
  471.  * Please do not report this as a bug unless it is consistently
  472.  * reproducible and you are sure that your bash binary and hardware are
  473.  * functioning properly.
  474. !!! FAILED postrm: 1
  475.  * The 'postrm' phase of the 'sys-libs/glibc-2.13-r4' package has failed
  476.  * with exit value 1.
  477.  *
  478.  * The problem occurred while executing the ebuild file named
  479.  * 'glibc-2.13-r4.ebuild' located in the '/var/db/pkg/sys-
  480. * libs/glibc-2.13-r4' directory. If necessary, manually remove the
  481.  * environment.bz2 file and/or the ebuild file located in that directory.
  482.  *
  483.  * Removal of the environment.bz2 file is preferred since it may allow the
  484.  * removal phases to execute successfully. The ebuild will be sourced and
  485.  * the eclasses from the current portage tree will be used when necessary.
  486.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  487.  * removal phases to be skipped entirely.
  488. >>> Unmerging sys-libs/ncurses-5.6-r2...
  489. [Errno 2] No such file or directory:
  490.    /bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/sys-libs/ncurses-5.6-r2/environment.bz2" > "/var/tmp/portage/._unmerge_/sys-libs/ncurses-5.6-r2/temp/environment"
  491. Traceback (most recent call last):
  492.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  493.     env, gid, groups, uid, umask, pre_exec)
  494.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  495.     os.execve(binary, myargs, env)
  496.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  497.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  498. OSError: [Errno 2] No such file or directory
  499. !!! FAILED prerm: 1
  500. [Errno 2] No such file or directory:
  501.    /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
  502. Traceback (most recent call last):
  503.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  504.     env, gid, groups, uid, umask, pre_exec)
  505.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  506.     os.execve(binary, myargs, env)
  507.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  508.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  509. OSError: [Errno 2] No such file or directory
  510.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  511.  * is known to be triggered by things such as failed variable assignments
  512.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  513.  * exiting, bash should have displayed an error message above. If bash did
  514.  * not produce an error message above, it's possible that the ebuild has
  515. * called `exit` when it should have called `die` instead. This behavior
  516. * may also be triggered by a corrupt bash binary or a hardware problem
  517. * such as memory or cpu malfunction. If the problem is not reproducible or
  518. * it appears to occur randomly, then it is likely to be triggered by a
  519. * hardware problem. If you suspect a hardware problem then you should try
  520. * some basic hardware diagnostics such as memtest. Please do not report
  521. * this as a bug unless it is consistently reproducible and you are sure
  522. * that your bash binary and hardware are functioning properly.
  523. [Errno 2] No such file or directory:
  524.   /usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
  525. Traceback (most recent call last):
  526.  File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  527.    env, gid, groups, uid, umask, pre_exec)
  528.  File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  529.    os.execve(binary, myargs, env)
  530.  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  531.    rval = self._func(*wrapped_args, **wrapped_kwargs)
  532. OSError: [Errno 2] No such file or directory
  533. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  534. * behavior is known to be triggered by things such as failed variable
  535. * assignments (bug #190128) or bad substitution errors (bug #200313).
  536. * Normally, before exiting, bash should have displayed an error message
  537. * above. If bash did not produce an error message above, it's possible
  538.  * that the ebuild has called `exit` when it should have called `die`
  539.  * instead. This behavior may also be triggered by a corrupt bash binary or
  540.  * a hardware problem such as memory or cpu malfunction. If the problem is
  541.  * not reproducible or it appears to occur randomly, then it is likely to
  542.  * be triggered by a hardware problem. If you suspect a hardware problem
  543.  * then you should try some basic hardware diagnostics such as memtest.
  544.  * Please do not report this as a bug unless it is consistently
  545.  * reproducible and you are sure that your bash binary and hardware are
  546.  * functioning properly.
  547. !!! FAILED postrm: 1
  548.  * The 'postrm' phase of the 'sys-libs/ncurses-5.6-r2' package has failed
  549.  * with exit value 1.
  550.  *
  551.  * The problem occurred while executing the ebuild file named
  552.  * 'ncurses-5.6-r2.ebuild' located in the '/var/db/pkg/sys-
  553. * libs/ncurses-5.6-r2' directory. If necessary, manually remove the
  554.  * environment.bz2 file and/or the ebuild file located in that directory.
  555.  *
  556.  * Removal of the environment.bz2 file is preferred since it may allow the
  557.  * removal phases to execute successfully. The ebuild will be sourced and
  558.  * the eclasses from the current portage tree will be used when necessary.
  559.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  560.  * removal phases to be skipped entirely.
  561. >>> Unmerging sys-libs/pam-0.99.9.0...
  562. [Errno 2] No such file or directory:
  563.    /bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/sys-libs/pam-0.99.9.0/environment.bz2" > "/var/tmp/portage/._unmerge_/sys-libs/pam-0.99.9.0/temp/environment"
  564. Traceback (most recent call last):
  565.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  566.     env, gid, groups, uid, umask, pre_exec)
  567.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  568.     os.execve(binary, myargs, env)
  569.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  570.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  571. OSError: [Errno 2] No such file or directory
  572. !!! FAILED prerm: 1
  573. [Errno 2] No such file or directory:
  574.    /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
  575. Traceback (most recent call last):
  576.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  577.     env, gid, groups, uid, umask, pre_exec)
  578.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  579.     os.execve(binary, myargs, env)
  580.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  581.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  582. OSError: [Errno 2] No such file or directory
  583.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  584.  * is known to be triggered by things such as failed variable assignments
  585.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  586.  * exiting, bash should have displayed an error message above. If bash did
  587.  * not produce an error message above, it's possible that the ebuild has
  588. * called `exit` when it should have called `die` instead. This behavior
  589. * may also be triggered by a corrupt bash binary or a hardware problem
  590. * such as memory or cpu malfunction. If the problem is not reproducible or
  591. * it appears to occur randomly, then it is likely to be triggered by a
  592. * hardware problem. If you suspect a hardware problem then you should try
  593. * some basic hardware diagnostics such as memtest. Please do not report
  594. * this as a bug unless it is consistently reproducible and you are sure
  595. * that your bash binary and hardware are functioning properly.
  596. [Errno 2] No such file or directory:
  597.   /usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
  598. Traceback (most recent call last):
  599.  File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  600.    env, gid, groups, uid, umask, pre_exec)
  601.  File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  602.    os.execve(binary, myargs, env)
  603.  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  604.    rval = self._func(*wrapped_args, **wrapped_kwargs)
  605. OSError: [Errno 2] No such file or directory
  606. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  607. * behavior is known to be triggered by things such as failed variable
  608. * assignments (bug #190128) or bad substitution errors (bug #200313).
  609. * Normally, before exiting, bash should have displayed an error message
  610. * above. If bash did not produce an error message above, it's possible
  611.  * that the ebuild has called `exit` when it should have called `die`
  612.  * instead. This behavior may also be triggered by a corrupt bash binary or
  613.  * a hardware problem such as memory or cpu malfunction. If the problem is
  614.  * not reproducible or it appears to occur randomly, then it is likely to
  615.  * be triggered by a hardware problem. If you suspect a hardware problem
  616.  * then you should try some basic hardware diagnostics such as memtest.
  617.  * Please do not report this as a bug unless it is consistently
  618.  * reproducible and you are sure that your bash binary and hardware are
  619.  * functioning properly.
  620. !!! FAILED postrm: 1
  621.  * The 'postrm' phase of the 'sys-libs/pam-0.99.9.0' package has failed
  622.  * with exit value 1.
  623.  *
  624.  * The problem occurred while executing the ebuild file named
  625.  * 'pam-0.99.9.0.ebuild' located in the '/var/db/pkg/sys-libs/pam-0.99.9.0'
  626.  * directory. If necessary, manually remove the environment.bz2 file and/or
  627.  * the ebuild file located in that directory.
  628.  *
  629.  * Removal of the environment.bz2 file is preferred since it may allow the
  630.  * removal phases to execute successfully. The ebuild will be sourced and
  631.  * the eclasses from the current portage tree will be used when necessary.
  632.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  633.  * removal phases to be skipped entirely.
  634. >>> Unmerging sys-libs/readline-6.2_p1...
  635. [Errno 2] No such file or directory:
  636.    /bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/sys-libs/readline-6.2_p1/environment.bz2" > "/var/tmp/portage/._unmerge_/sys-libs/readline-6.2_p1/temp/environment"
  637. Traceback (most recent call last):
  638.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  639.     env, gid, groups, uid, umask, pre_exec)
  640.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  641.     os.execve(binary, myargs, env)
  642.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  643.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  644. OSError: [Errno 2] No such file or directory
  645. !!! FAILED prerm: 1
  646. [Errno 2] No such file or directory:
  647.    /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
  648. Traceback (most recent call last):
  649.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  650.     env, gid, groups, uid, umask, pre_exec)
  651.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  652.     os.execve(binary, myargs, env)
  653.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  654.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  655. OSError: [Errno 2] No such file or directory
  656.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  657.  * is known to be triggered by things such as failed variable assignments
  658.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  659.  * exiting, bash should have displayed an error message above. If bash did
  660.  * not produce an error message above, it's possible that the ebuild has
  661. * called `exit` when it should have called `die` instead. This behavior
  662. * may also be triggered by a corrupt bash binary or a hardware problem
  663. * such as memory or cpu malfunction. If the problem is not reproducible or
  664. * it appears to occur randomly, then it is likely to be triggered by a
  665. * hardware problem. If you suspect a hardware problem then you should try
  666. * some basic hardware diagnostics such as memtest. Please do not report
  667. * this as a bug unless it is consistently reproducible and you are sure
  668. * that your bash binary and hardware are functioning properly.
  669. [Errno 2] No such file or directory:
  670.   /usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
  671. Traceback (most recent call last):
  672.  File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  673.    env, gid, groups, uid, umask, pre_exec)
  674.  File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  675.    os.execve(binary, myargs, env)
  676.  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  677.    rval = self._func(*wrapped_args, **wrapped_kwargs)
  678. OSError: [Errno 2] No such file or directory
  679. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  680. * behavior is known to be triggered by things such as failed variable
  681. * assignments (bug #190128) or bad substitution errors (bug #200313).
  682. * Normally, before exiting, bash should have displayed an error message
  683. * above. If bash did not produce an error message above, it's possible
  684.  * that the ebuild has called `exit` when it should have called `die`
  685.  * instead. This behavior may also be triggered by a corrupt bash binary or
  686.  * a hardware problem such as memory or cpu malfunction. If the problem is
  687.  * not reproducible or it appears to occur randomly, then it is likely to
  688.  * be triggered by a hardware problem. If you suspect a hardware problem
  689.  * then you should try some basic hardware diagnostics such as memtest.
  690.  * Please do not report this as a bug unless it is consistently
  691.  * reproducible and you are sure that your bash binary and hardware are
  692.  * functioning properly.
  693. !!! FAILED postrm: 1
  694.  * The 'postrm' phase of the 'sys-libs/readline-6.2_p1' package has failed
  695.  * with exit value 1.
  696.  *
  697.  * The problem occurred while executing the ebuild file named
  698.  * 'readline-6.2_p1.ebuild' located in the '/var/db/pkg/sys-
  699. * libs/readline-6.2_p1' directory. If necessary, manually remove the
  700.  * environment.bz2 file and/or the ebuild file located in that directory.
  701.  *
  702.  * Removal of the environment.bz2 file is preferred since it may allow the
  703.  * removal phases to execute successfully. The ebuild will be sourced and
  704.  * the eclasses from the current portage tree will be used when necessary.
  705.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  706.  * removal phases to be skipped entirely.
  707. >>> Unmerging sys-process/psmisc-22.14...
  708. [Errno 2] No such file or directory:
  709.    /bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/sys-process/psmisc-22.14/environment.bz2" > "/var/tmp/portage/._unmerge_/sys-process/psmisc-22.14/temp/environment"
  710. Traceback (most recent call last):
  711.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  712.     env, gid, groups, uid, umask, pre_exec)
  713.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  714.     os.execve(binary, myargs, env)
  715.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  716.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  717. OSError: [Errno 2] No such file or directory
  718. !!! FAILED prerm: 1
  719. [Errno 2] No such file or directory:
  720.    /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
  721. Traceback (most recent call last):
  722.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  723.     env, gid, groups, uid, umask, pre_exec)
  724.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  725.     os.execve(binary, myargs, env)
  726.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  727.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  728. OSError: [Errno 2] No such file or directory
  729.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  730.  * is known to be triggered by things such as failed variable assignments
  731.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  732.  * exiting, bash should have displayed an error message above. If bash did
  733.  * not produce an error message above, it's possible that the ebuild has
  734. * called `exit` when it should have called `die` instead. This behavior
  735. * may also be triggered by a corrupt bash binary or a hardware problem
  736. * such as memory or cpu malfunction. If the problem is not reproducible or
  737. * it appears to occur randomly, then it is likely to be triggered by a
  738. * hardware problem. If you suspect a hardware problem then you should try
  739. * some basic hardware diagnostics such as memtest. Please do not report
  740. * this as a bug unless it is consistently reproducible and you are sure
  741. * that your bash binary and hardware are functioning properly.
  742. [Errno 2] No such file or directory:
  743.   /usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
  744. Traceback (most recent call last):
  745.  File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  746.    env, gid, groups, uid, umask, pre_exec)
  747.  File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  748.    os.execve(binary, myargs, env)
  749.  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  750.    rval = self._func(*wrapped_args, **wrapped_kwargs)
  751. OSError: [Errno 2] No such file or directory
  752. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  753. * behavior is known to be triggered by things such as failed variable
  754. * assignments (bug #190128) or bad substitution errors (bug #200313).
  755. * Normally, before exiting, bash should have displayed an error message
  756. * above. If bash did not produce an error message above, it's possible
  757.  * that the ebuild has called `exit` when it should have called `die`
  758.  * instead. This behavior may also be triggered by a corrupt bash binary or
  759.  * a hardware problem such as memory or cpu malfunction. If the problem is
  760.  * not reproducible or it appears to occur randomly, then it is likely to
  761.  * be triggered by a hardware problem. If you suspect a hardware problem
  762.  * then you should try some basic hardware diagnostics such as memtest.
  763.  * Please do not report this as a bug unless it is consistently
  764.  * reproducible and you are sure that your bash binary and hardware are
  765.  * functioning properly.
  766. !!! FAILED postrm: 1
  767.  * The 'postrm' phase of the 'sys-process/psmisc-22.14' package has failed
  768.  * with exit value 1.
  769.  *
  770.  * The problem occurred while executing the ebuild file named
  771.  * 'psmisc-22.14.ebuild' located in the '/var/db/pkg/sys-
  772. * process/psmisc-22.14' directory. If necessary, manually remove the
  773.  * environment.bz2 file and/or the ebuild file located in that directory.
  774.  *
  775.  * Removal of the environment.bz2 file is preferred since it may allow the
  776.  * removal phases to execute successfully. The ebuild will be sourced and
  777.  * the eclasses from the current portage tree will be used when necessary.
  778.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  779.  * removal phases to be skipped entirely.
  780. >>> Unmerging virtual/perl-Digest-MD5-2.39...
  781. [Errno 2] No such file or directory:
  782.    /bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/virtual/perl-Digest-MD5-2.39/environment.bz2" > "/var/tmp/portage/._unmerge_/virtual/perl-Digest-MD5-2.39/temp/environment"
  783. Traceback (most recent call last):
  784.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  785.     env, gid, groups, uid, umask, pre_exec)
  786.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  787.     os.execve(binary, myargs, env)
  788.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  789.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  790. OSError: [Errno 2] No such file or directory
  791. !!! FAILED prerm: 1
  792. [Errno 2] No such file or directory:
  793.    /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
  794. Traceback (most recent call last):
  795.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  796.     env, gid, groups, uid, umask, pre_exec)
  797.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  798.     os.execve(binary, myargs, env)
  799.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  800.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  801. OSError: [Errno 2] No such file or directory
  802.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  803.  * is known to be triggered by things such as failed variable assignments
  804.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  805.  * exiting, bash should have displayed an error message above. If bash did
  806.  * not produce an error message above, it's possible that the ebuild has
  807. * called `exit` when it should have called `die` instead. This behavior
  808. * may also be triggered by a corrupt bash binary or a hardware problem
  809. * such as memory or cpu malfunction. If the problem is not reproducible or
  810. * it appears to occur randomly, then it is likely to be triggered by a
  811. * hardware problem. If you suspect a hardware problem then you should try
  812. * some basic hardware diagnostics such as memtest. Please do not report
  813. * this as a bug unless it is consistently reproducible and you are sure
  814. * that your bash binary and hardware are functioning properly.
  815. [Errno 2] No such file or directory:
  816.   /usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
  817. Traceback (most recent call last):
  818.  File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  819.    env, gid, groups, uid, umask, pre_exec)
  820.  File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  821.    os.execve(binary, myargs, env)
  822.  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  823.    rval = self._func(*wrapped_args, **wrapped_kwargs)
  824. OSError: [Errno 2] No such file or directory
  825. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  826. * behavior is known to be triggered by things such as failed variable
  827. * assignments (bug #190128) or bad substitution errors (bug #200313).
  828. * Normally, before exiting, bash should have displayed an error message
  829. * above. If bash did not produce an error message above, it's possible
  830.  * that the ebuild has called `exit` when it should have called `die`
  831.  * instead. This behavior may also be triggered by a corrupt bash binary or
  832.  * a hardware problem such as memory or cpu malfunction. If the problem is
  833.  * not reproducible or it appears to occur randomly, then it is likely to
  834.  * be triggered by a hardware problem. If you suspect a hardware problem
  835.  * then you should try some basic hardware diagnostics such as memtest.
  836.  * Please do not report this as a bug unless it is consistently
  837.  * reproducible and you are sure that your bash binary and hardware are
  838.  * functioning properly.
  839. !!! FAILED postrm: 1
  840.  * The 'postrm' phase of the 'virtual/perl-Digest-MD5-2.39' package has
  841.  * failed with exit value 1.
  842.  *
  843.  * The problem occurred while executing the ebuild file named 'perl-Digest-
  844. * MD5-2.39.ebuild' located in the '/var/db/pkg/virtual/perl-Digest-
  845. * MD5-2.39' directory. If necessary, manually remove the environment.bz2
  846.  * file and/or the ebuild file located in that directory.
  847.  *
  848.  * Removal of the environment.bz2 file is preferred since it may allow the
  849.  * removal phases to execute successfully. The ebuild will be sourced and
  850.  * the eclasses from the current portage tree will be used when necessary.
  851.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  852.  * removal phases to be skipped entirely.
  853. >>> Unmerging virtual/perl-Scalar-List-Utils-1.230.0-r1...
  854. [Errno 2] No such file or directory:
  855.    /bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/virtual/perl-Scalar-List-Utils-1.230.0-r1/environment.bz2" > "/var/tmp/portage/._unmerge_/virtual/perl-Scalar-List-Utils-1.230.0-r1/temp/environment"
  856. Traceback (most recent call last):
  857.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  858.     env, gid, groups, uid, umask, pre_exec)
  859.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  860.     os.execve(binary, myargs, env)
  861.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  862.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  863. OSError: [Errno 2] No such file or directory
  864. !!! FAILED prerm: 1
  865. [Errno 2] No such file or directory:
  866.    /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
  867. Traceback (most recent call last):
  868.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  869.     env, gid, groups, uid, umask, pre_exec)
  870.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  871.     os.execve(binary, myargs, env)
  872.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  873.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  874. OSError: [Errno 2] No such file or directory
  875.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  876.  * is known to be triggered by things such as failed variable assignments
  877.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  878.  * exiting, bash should have displayed an error message above. If bash did
  879.  * not produce an error message above, it's possible that the ebuild has
  880. * called `exit` when it should have called `die` instead. This behavior
  881. * may also be triggered by a corrupt bash binary or a hardware problem
  882. * such as memory or cpu malfunction. If the problem is not reproducible or
  883. * it appears to occur randomly, then it is likely to be triggered by a
  884. * hardware problem. If you suspect a hardware problem then you should try
  885. * some basic hardware diagnostics such as memtest. Please do not report
  886. * this as a bug unless it is consistently reproducible and you are sure
  887. * that your bash binary and hardware are functioning properly.
  888. [Errno 2] No such file or directory:
  889.   /usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
  890. Traceback (most recent call last):
  891.  File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  892.    env, gid, groups, uid, umask, pre_exec)
  893.  File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  894.    os.execve(binary, myargs, env)
  895.  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  896.    rval = self._func(*wrapped_args, **wrapped_kwargs)
  897. OSError: [Errno 2] No such file or directory
  898. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  899. * behavior is known to be triggered by things such as failed variable
  900. * assignments (bug #190128) or bad substitution errors (bug #200313).
  901. * Normally, before exiting, bash should have displayed an error message
  902. * above. If bash did not produce an error message above, it's possible
  903.  * that the ebuild has called `exit` when it should have called `die`
  904.  * instead. This behavior may also be triggered by a corrupt bash binary or
  905.  * a hardware problem such as memory or cpu malfunction. If the problem is
  906.  * not reproducible or it appears to occur randomly, then it is likely to
  907.  * be triggered by a hardware problem. If you suspect a hardware problem
  908.  * then you should try some basic hardware diagnostics such as memtest.
  909.  * Please do not report this as a bug unless it is consistently
  910.  * reproducible and you are sure that your bash binary and hardware are
  911.  * functioning properly.
  912. !!! FAILED postrm: 1
  913.  * The 'postrm' phase of the 'virtual/perl-Scalar-List-Utils-1.230.0-r1'
  914.  * package has failed with exit value 1.
  915.  *
  916.  * The problem occurred while executing the ebuild file named 'perl-Scalar-
  917. * List-Utils-1.230.0-r1.ebuild' located in the '/var/db/pkg/virtual/perl-
  918. * Scalar-List-Utils-1.230.0-r1' directory. If necessary, manually remove
  919.  * the environment.bz2 file and/or the ebuild file located in that
  920.  * directory.
  921.  *
  922.  * Removal of the environment.bz2 file is preferred since it may allow the
  923.  * removal phases to execute successfully. The ebuild will be sourced and
  924.  * the eclasses from the current portage tree will be used when necessary.
  925.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  926.  * removal phases to be skipped entirely.
  927. >>> Unmerging virtual/perl-libnet-1.220.0-r1...
  928. [Errno 2] No such file or directory:
  929.    /bin/bash -c ${PORTAGE_BUNZIP2_COMMAND:-${PORTAGE_BZIP2_COMMAND} -d} -c -- "/var/db/pkg/virtual/perl-libnet-1.220.0-r1/environment.bz2" > "/var/tmp/portage/._unmerge_/virtual/perl-libnet-1.220.0-r1/temp/environment"
  930. Traceback (most recent call last):
  931.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  932.     env, gid, groups, uid, umask, pre_exec)
  933.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  934.     os.execve(binary, myargs, env)
  935.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  936.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  937. OSError: [Errno 2] No such file or directory
  938. !!! FAILED prerm: 1
  939. [Errno 2] No such file or directory:
  940.    /bin/bash -c "/usr/lib64/portage/bin/ebuild.sh" postrm
  941. Traceback (most recent call last):
  942.   File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  943.     env, gid, groups, uid, umask, pre_exec)
  944.   File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  945.     os.execve(binary, myargs, env)
  946.   File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  947.     rval = self._func(*wrapped_args, **wrapped_kwargs)
  948. OSError: [Errno 2] No such file or directory
  949.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  950.  * is known to be triggered by things such as failed variable assignments
  951.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  952.  * exiting, bash should have displayed an error message above. If bash did
  953.  * not produce an error message above, it's possible that the ebuild has
  954. * called `exit` when it should have called `die` instead. This behavior
  955. * may also be triggered by a corrupt bash binary or a hardware problem
  956. * such as memory or cpu malfunction. If the problem is not reproducible or
  957. * it appears to occur randomly, then it is likely to be triggered by a
  958. * hardware problem. If you suspect a hardware problem then you should try
  959. * some basic hardware diagnostics such as memtest. Please do not report
  960. * this as a bug unless it is consistently reproducible and you are sure
  961. * that your bash binary and hardware are functioning properly.
  962. [Errno 2] No such file or directory:
  963.   /usr/bin/sandbox "/usr/lib64/portage/bin/misc-functions.sh" die_hooks
  964. Traceback (most recent call last):
  965.  File "/usr/lib64/portage/pym/portage/process.py", line 250, in spawn
  966.    env, gid, groups, uid, umask, pre_exec)
  967.  File "/usr/lib64/portage/pym/portage/process.py", line 379, in _exec
  968.    os.execve(binary, myargs, env)
  969.  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
  970.    rval = self._func(*wrapped_args, **wrapped_kwargs)
  971. OSError: [Errno 2] No such file or directory
  972. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  973. * behavior is known to be triggered by things such as failed variable
  974. * assignments (bug #190128) or bad substitution errors (bug #200313).
  975. * Normally, before exiting, bash should have displayed an error message
  976. * above. If bash did not produce an error message above, it's possible
  977.  * that the ebuild has called `exit` when it should have called `die`
  978.  * instead. This behavior may also be triggered by a corrupt bash binary or
  979.  * a hardware problem such as memory or cpu malfunction. If the problem is
  980.  * not reproducible or it appears to occur randomly, then it is likely to
  981.  * be triggered by a hardware problem. If you suspect a hardware problem
  982.  * then you should try some basic hardware diagnostics such as memtest.
  983.  * Please do not report this as a bug unless it is consistently
  984.  * reproducible and you are sure that your bash binary and hardware are
  985.  * functioning properly.
  986. !!! FAILED postrm: 1
  987.  * The 'postrm' phase of the 'virtual/perl-libnet-1.220.0-r1' package has
  988.  * failed with exit value 1.
  989.  *
  990.  * The problem occurred while executing the ebuild file named 'perl-
  991. * libnet-1.220.0-r1.ebuild' located in the '/var/db/pkg/virtual/perl-
  992. * libnet-1.220.0-r1' directory. If necessary, manually remove the
  993.  * environment.bz2 file and/or the ebuild file located in that directory.
  994.  *
  995.  * Removal of the environment.bz2 file is preferred since it may allow the
  996.  * removal phases to execute successfully. The ebuild will be sourced and
  997.  * the eclasses from the current portage tree will be used when necessary.
  998.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  999.  * removal phases to be skipped entirely.
  1000.  
  1001.  * Messages for package dev-lang/perl-5.12.4-r1:
  1002.  
  1003.  * Removing dead symlink /usr/bin/xsubpp
  1004.  * Removing dead symlink /usr/share/man/man1/xsubpp.1.bz2
  1005.  
  1006.  * Messages for package sys-libs/glibc-2.13-r4:
  1007.  
  1008.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  1009.  * is known to be triggered by things such as failed variable assignments
  1010.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  1011.  * exiting, bash should have displayed an error message above. If bash did
  1012.  * not produce an error message above, it's possible that the ebuild has
  1013. * called `exit` when it should have called `die` instead. This behavior
  1014. * may also be triggered by a corrupt bash binary or a hardware problem
  1015. * such as memory or cpu malfunction. If the problem is not reproducible or
  1016. * it appears to occur randomly, then it is likely to be triggered by a
  1017. * hardware problem. If you suspect a hardware problem then you should try
  1018. * some basic hardware diagnostics such as memtest. Please do not report
  1019. * this as a bug unless it is consistently reproducible and you are sure
  1020. * that your bash binary and hardware are functioning properly.
  1021. * The 'postrm' phase of the 'sys-libs/glibc-2.13-r4' package has failed
  1022. * with exit value 1.
  1023. *
  1024. * The problem occurred while executing the ebuild file named
  1025. * 'glibc-2.13-r4.ebuild' located in the '/var/db/pkg/sys-
  1026.  * libs/glibc-2.13-r4' directory. If necessary, manually remove the
  1027. * environment.bz2 file and/or the ebuild file located in that directory.
  1028. *
  1029. * Removal of the environment.bz2 file is preferred since it may allow the
  1030. * removal phases to execute successfully. The ebuild will be sourced and
  1031. * the eclasses from the current portage tree will be used when necessary.
  1032. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  1033. * removal phases to be skipped entirely.
  1034.  
  1035. * Messages for package sys-libs/ncurses-5.6-r2:
  1036.  
  1037. * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  1038. * is known to be triggered by things such as failed variable assignments
  1039. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  1040. * exiting, bash should have displayed an error message above. If bash did
  1041. * not produce an error message above, it's possible that the ebuild has
  1042.  * called `exit` when it should have called `die` instead. This behavior
  1043.  * may also be triggered by a corrupt bash binary or a hardware problem
  1044.  * such as memory or cpu malfunction. If the problem is not reproducible or
  1045.  * it appears to occur randomly, then it is likely to be triggered by a
  1046.  * hardware problem. If you suspect a hardware problem then you should try
  1047.  * some basic hardware diagnostics such as memtest. Please do not report
  1048.  * this as a bug unless it is consistently reproducible and you are sure
  1049.  * that your bash binary and hardware are functioning properly.
  1050.  * The 'postrm' phase of the 'sys-libs/ncurses-5.6-r2' package has failed
  1051.  * with exit value 1.
  1052.  *
  1053.  * The problem occurred while executing the ebuild file named
  1054.  * 'ncurses-5.6-r2.ebuild' located in the '/var/db/pkg/sys-
  1055. * libs/ncurses-5.6-r2' directory. If necessary, manually remove the
  1056.  * environment.bz2 file and/or the ebuild file located in that directory.
  1057.  *
  1058.  * Removal of the environment.bz2 file is preferred since it may allow the
  1059.  * removal phases to execute successfully. The ebuild will be sourced and
  1060.  * the eclasses from the current portage tree will be used when necessary.
  1061.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  1062.  * removal phases to be skipped entirely.
  1063.  
  1064.  * Messages for package sys-libs/pam-0.99.9.0:
  1065.  
  1066.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  1067.  * is known to be triggered by things such as failed variable assignments
  1068.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  1069.  * exiting, bash should have displayed an error message above. If bash did
  1070.  * not produce an error message above, it's possible that the ebuild has
  1071. * called `exit` when it should have called `die` instead. This behavior
  1072. * may also be triggered by a corrupt bash binary or a hardware problem
  1073. * such as memory or cpu malfunction. If the problem is not reproducible or
  1074. * it appears to occur randomly, then it is likely to be triggered by a
  1075. * hardware problem. If you suspect a hardware problem then you should try
  1076. * some basic hardware diagnostics such as memtest. Please do not report
  1077. * this as a bug unless it is consistently reproducible and you are sure
  1078. * that your bash binary and hardware are functioning properly.
  1079. * The 'postrm' phase of the 'sys-libs/pam-0.99.9.0' package has failed
  1080. * with exit value 1.
  1081. *
  1082. * The problem occurred while executing the ebuild file named
  1083. * 'pam-0.99.9.0.ebuild' located in the '/var/db/pkg/sys-libs/pam-0.99.9.0'
  1084. * directory. If necessary, manually remove the environment.bz2 file and/or
  1085. * the ebuild file located in that directory.
  1086. *
  1087. * Removal of the environment.bz2 file is preferred since it may allow the
  1088. * removal phases to execute successfully. The ebuild will be sourced and
  1089. * the eclasses from the current portage tree will be used when necessary.
  1090. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  1091. * removal phases to be skipped entirely.
  1092.  
  1093. * Messages for package sys-libs/readline-6.2_p1:
  1094.  
  1095. * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  1096. * is known to be triggered by things such as failed variable assignments
  1097. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  1098. * exiting, bash should have displayed an error message above. If bash did
  1099. * not produce an error message above, it's possible that the ebuild has
  1100.  * called `exit` when it should have called `die` instead. This behavior
  1101.  * may also be triggered by a corrupt bash binary or a hardware problem
  1102.  * such as memory or cpu malfunction. If the problem is not reproducible or
  1103.  * it appears to occur randomly, then it is likely to be triggered by a
  1104.  * hardware problem. If you suspect a hardware problem then you should try
  1105.  * some basic hardware diagnostics such as memtest. Please do not report
  1106.  * this as a bug unless it is consistently reproducible and you are sure
  1107.  * that your bash binary and hardware are functioning properly.
  1108.  * The 'postrm' phase of the 'sys-libs/readline-6.2_p1' package has failed
  1109.  * with exit value 1.
  1110.  *
  1111.  * The problem occurred while executing the ebuild file named
  1112.  * 'readline-6.2_p1.ebuild' located in the '/var/db/pkg/sys-
  1113. * libs/readline-6.2_p1' directory. If necessary, manually remove the
  1114.  * environment.bz2 file and/or the ebuild file located in that directory.
  1115.  *
  1116.  * Removal of the environment.bz2 file is preferred since it may allow the
  1117.  * removal phases to execute successfully. The ebuild will be sourced and
  1118.  * the eclasses from the current portage tree will be used when necessary.
  1119.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  1120.  * removal phases to be skipped entirely.
  1121.  
  1122.  * Messages for package sys-process/psmisc-22.14:
  1123.  
  1124.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  1125.  * is known to be triggered by things such as failed variable assignments
  1126.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  1127.  * exiting, bash should have displayed an error message above. If bash did
  1128.  * not produce an error message above, it's possible that the ebuild has
  1129. * called `exit` when it should have called `die` instead. This behavior
  1130. * may also be triggered by a corrupt bash binary or a hardware problem
  1131. * such as memory or cpu malfunction. If the problem is not reproducible or
  1132. * it appears to occur randomly, then it is likely to be triggered by a
  1133. * hardware problem. If you suspect a hardware problem then you should try
  1134. * some basic hardware diagnostics such as memtest. Please do not report
  1135. * this as a bug unless it is consistently reproducible and you are sure
  1136. * that your bash binary and hardware are functioning properly.
  1137. * The 'postrm' phase of the 'sys-process/psmisc-22.14' package has failed
  1138. * with exit value 1.
  1139. *
  1140. * The problem occurred while executing the ebuild file named
  1141. * 'psmisc-22.14.ebuild' located in the '/var/db/pkg/sys-
  1142.  * process/psmisc-22.14' directory. If necessary, manually remove the
  1143. * environment.bz2 file and/or the ebuild file located in that directory.
  1144. *
  1145. * Removal of the environment.bz2 file is preferred since it may allow the
  1146. * removal phases to execute successfully. The ebuild will be sourced and
  1147. * the eclasses from the current portage tree will be used when necessary.
  1148. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  1149. * removal phases to be skipped entirely.
  1150.  
  1151. * Messages for package virtual/perl-Digest-MD5-2.39:
  1152.  
  1153. * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  1154. * is known to be triggered by things such as failed variable assignments
  1155. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  1156. * exiting, bash should have displayed an error message above. If bash did
  1157. * not produce an error message above, it's possible that the ebuild has
  1158.  * called `exit` when it should have called `die` instead. This behavior
  1159.  * may also be triggered by a corrupt bash binary or a hardware problem
  1160.  * such as memory or cpu malfunction. If the problem is not reproducible or
  1161.  * it appears to occur randomly, then it is likely to be triggered by a
  1162.  * hardware problem. If you suspect a hardware problem then you should try
  1163.  * some basic hardware diagnostics such as memtest. Please do not report
  1164.  * this as a bug unless it is consistently reproducible and you are sure
  1165.  * that your bash binary and hardware are functioning properly.
  1166.  * The 'postrm' phase of the 'virtual/perl-Digest-MD5-2.39' package has
  1167.  * failed with exit value 1.
  1168.  *
  1169.  * The problem occurred while executing the ebuild file named 'perl-Digest-
  1170. * MD5-2.39.ebuild' located in the '/var/db/pkg/virtual/perl-Digest-
  1171. * MD5-2.39' directory. If necessary, manually remove the environment.bz2
  1172.  * file and/or the ebuild file located in that directory.
  1173.  *
  1174.  * Removal of the environment.bz2 file is preferred since it may allow the
  1175.  * removal phases to execute successfully. The ebuild will be sourced and
  1176.  * the eclasses from the current portage tree will be used when necessary.
  1177.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  1178.  * removal phases to be skipped entirely.
  1179.  
  1180.  * Messages for package virtual/perl-Scalar-List-Utils-1.230.0-r1:
  1181.  
  1182.  * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  1183.  * is known to be triggered by things such as failed variable assignments
  1184.  * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  1185.  * exiting, bash should have displayed an error message above. If bash did
  1186.  * not produce an error message above, it's possible that the ebuild has
  1187. * called `exit` when it should have called `die` instead. This behavior
  1188. * may also be triggered by a corrupt bash binary or a hardware problem
  1189. * such as memory or cpu malfunction. If the problem is not reproducible or
  1190. * it appears to occur randomly, then it is likely to be triggered by a
  1191. * hardware problem. If you suspect a hardware problem then you should try
  1192. * some basic hardware diagnostics such as memtest. Please do not report
  1193. * this as a bug unless it is consistently reproducible and you are sure
  1194. * that your bash binary and hardware are functioning properly.
  1195. * The 'postrm' phase of the 'virtual/perl-Scalar-List-Utils-1.230.0-r1'
  1196. * package has failed with exit value 1.
  1197. *
  1198. * The problem occurred while executing the ebuild file named 'perl-Scalar-
  1199.  * List-Utils-1.230.0-r1.ebuild' located in the '/var/db/pkg/virtual/perl-
  1200.  * Scalar-List-Utils-1.230.0-r1' directory. If necessary, manually remove
  1201. * the environment.bz2 file and/or the ebuild file located in that
  1202. * directory.
  1203. *
  1204. * Removal of the environment.bz2 file is preferred since it may allow the
  1205. * removal phases to execute successfully. The ebuild will be sourced and
  1206. * the eclasses from the current portage tree will be used when necessary.
  1207. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  1208. * removal phases to be skipped entirely.
  1209.  
  1210. * Messages for package virtual/perl-libnet-1.220.0-r1:
  1211.  
  1212. * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  1213. * is known to be triggered by things such as failed variable assignments
  1214. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  1215. * exiting, bash should have displayed an error message above. If bash did
  1216. * not produce an error message above, it's possible that the ebuild has
  1217.  * called `exit` when it should have called `die` instead. This behavior
  1218.  * may also be triggered by a corrupt bash binary or a hardware problem
  1219.  * such as memory or cpu malfunction. If the problem is not reproducible or
  1220.  * it appears to occur randomly, then it is likely to be triggered by a
  1221.  * hardware problem. If you suspect a hardware problem then you should try
  1222.  * some basic hardware diagnostics such as memtest. Please do not report
  1223.  * this as a bug unless it is consistently reproducible and you are sure
  1224.  * that your bash binary and hardware are functioning properly.
  1225.  * The 'postrm' phase of the 'virtual/perl-libnet-1.220.0-r1' package has
  1226.  * failed with exit value 1.
  1227.  *
  1228.  * The problem occurred while executing the ebuild file named 'perl-
  1229. * libnet-1.220.0-r1.ebuild' located in the '/var/db/pkg/virtual/perl-
  1230. * libnet-1.220.0-r1' directory. If necessary, manually remove the
  1231.  * environment.bz2 file and/or the ebuild file located in that directory.
  1232.  *
  1233.  * Removal of the environment.bz2 file is preferred since it may allow the
  1234.  * removal phases to execute successfully. The ebuild will be sourced and
  1235.  * the eclasses from the current portage tree will be used when necessary.
  1236.  * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  1237.  * removal phases to be skipped entirely.
  1238.  
  1239.  * GNU info directory index is up-to-date.
  1240.  
  1241.  * IMPORTANT: 5 news items need reading for repository 'gentoo'.
  1242.  * Use eselect news to read news items.
  1243.  
  1244. <<[CHROOT]sabayon / # >> uname -r
  1245. bash: /usr/bin/uname: No such file or directory
  1246. <<[CHROOT]sabayon / # >> emerge
  1247. bash: /usr/bin/emerge: /usr/bin/python: bad interpreter: No such file or directory
  1248. <<[CHROOT]sabayon / # >> ls
  1249. bash: /bin/ls: No such file or directory
  1250. <<[CHROOT]sabayon / # >> cd /
  1251. <<[CHROOT]sabayon / # >> ls
  1252. bash: /bin/ls: No such file or directory
clone this paste RAW Paste Data