spire-Gentoo linux # emerge --depclean

 * 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.

Calculating dependencies... done!
>>> Calculating removal order...

 dev-lang/python
    selected: 2.6.6-r2
   protected: none
     omitted: 2.7.1-r1 3.1.3-r1

 sys-kernel/gentoo-sources
    selected: 2.6.36-r5
   protected: none
     omitted: 2.6.36-r8

 www-plugins/nspluginwrapper
    selected: 1.3.0
   protected: none
     omitted: none

 x11-proto/fontcacheproto
    selected: 0.1.3
   protected: none
     omitted: none

All selected packages: sys-kernel/gentoo-sources-2.6.36-r5 www-plugins/nspluginwrapper-1.3.0 x11-proto/fontcacheproto-0.1.3 dev-lang/python-2.6.6-r2

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

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in:  5 4 3 2 1
>>> Unmerging dev-lang/python-2.6.6-r2...
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: dev-lang/python-2.6.6-r2 failed (postrm phase):
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *   ebuild.sh, line 1837:  Called filter_readonly_variables
 *   ebuild.sh, line 1818:  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-r2',
 * the complete build log and the output of 'emerge -pqv =dev-lang/python-2.6.6-r2'.
 * The complete build log is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r2/temp/environment'.
 * S: '/var/tmp/binpkgs/dev-lang/python-2.6.6-r2/work/python-2.6.6'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: dev-lang/python-2.6.6-r2 failed:
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   misc-functions.sh, line   17:  Called source '/usr/lib64/portage/bin/ebuild.sh'
 *           ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *           ebuild.sh, line 1837:  Called filter_readonly_variables
 *           ebuild.sh, line 1818:  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-r2',
 * the complete build log and the output of 'emerge -pqv =dev-lang/python-2.6.6-r2'.
 * 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-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r2/temp/environment'.
 * S: '/var/tmp/binpkgs/dev-lang/python-2.6.6-r2/work/python-2.6.6'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED postrm: 1
 * The 'postrm' phase of the 'dev-lang/python-2.6.6-r2' package has failed
 * with exit value 1.
 *
 * The problem occurred while executing the ebuild file named
 * 'python-2.6.6-r2.ebuild' located in the '/var/db/pkg/dev-
 * lang/python-2.6.6-r2' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 *
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.
>>> Unmerging sys-kernel/gentoo-sources-2.6.36-r5...
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: sys-kernel/gentoo-sources-2.6.36-r5 failed (prerm phase):
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *   ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   ebuild.sh, line 1818:  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-kernel/gentoo-sources-2.6.36-r5',
 * the complete build log and the output of 'emerge -pqv =sys-kernel/gentoo-sources-2.6.36-r5'.
 * The complete build log is located at '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/temp/environment'.
 * S: '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/work/gentoo-sources-2.6.36'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * 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.
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: sys-kernel/gentoo-sources-2.6.36-r5 failed:
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   misc-functions.sh, line   17:  Called source '/usr/lib64/portage/bin/ebuild.sh'
 *           ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *           ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *           ebuild.sh, line 1818:  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-kernel/gentoo-sources-2.6.36-r5',
 * the complete build log and the output of 'emerge -pqv =sys-kernel/gentoo-sources-2.6.36-r5'.
 * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/'
 * The complete build log is located at '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/temp/environment'.
 * S: '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/work/gentoo-sources-2.6.36'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED prerm: 1
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: sys-kernel/gentoo-sources-2.6.36-r5 failed (postrm phase):
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *   ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   ebuild.sh, line 1818:  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-kernel/gentoo-sources-2.6.36-r5',
 * the complete build log and the output of 'emerge -pqv =sys-kernel/gentoo-sources-2.6.36-r5'.
 * The complete build log is located at '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/temp/environment'.
 * S: '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/work/gentoo-sources-2.6.36'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: sys-kernel/gentoo-sources-2.6.36-r5 failed:
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   misc-functions.sh, line   17:  Called source '/usr/lib64/portage/bin/ebuild.sh'
 *           ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *           ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *           ebuild.sh, line 1818:  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-kernel/gentoo-sources-2.6.36-r5',
 * the complete build log and the output of 'emerge -pqv =sys-kernel/gentoo-sources-2.6.36-r5'.
 * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/'
 * The complete build log is located at '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/temp/environment'.
 * S: '/var/tmp/binpkgs/sys-kernel/gentoo-sources-2.6.36-r5/work/gentoo-sources-2.6.36'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED postrm: 1
 * The 'postrm' phase of the 'sys-kernel/gentoo-sources-2.6.36-r5' package
 * has failed with exit value 1.
 *
 * The problem occurred while executing the ebuild file named 'gentoo-
 * sources-2.6.36-r5.ebuild' located in the '/var/db/pkg/sys-kernel/gentoo-
 * sources-2.6.36-r5' directory. If necessary, manually remove the
 * environment.bz2 file and/or the ebuild file located in that directory.
 *
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.
>>> Unmerging www-plugins/nspluginwrapper-1.3.0...
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: www-plugins/nspluginwrapper-1.3.0 failed (prerm phase):
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *   ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   ebuild.sh, line 1818:  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 =www-plugins/nspluginwrapper-1.3.0',
 * the complete build log and the output of 'emerge -pqv =www-plugins/nspluginwrapper-1.3.0'.
 * The complete build log is located at '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/temp/environment'.
 * S: '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/work/nspluginwrapper-1.3.0'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * 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.
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: www-plugins/nspluginwrapper-1.3.0 failed:
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   misc-functions.sh, line   17:  Called source '/usr/lib64/portage/bin/ebuild.sh'
 *           ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *           ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *           ebuild.sh, line 1818:  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 =www-plugins/nspluginwrapper-1.3.0',
 * the complete build log and the output of 'emerge -pqv =www-plugins/nspluginwrapper-1.3.0'.
 * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/'
 * The complete build log is located at '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/temp/environment'.
 * S: '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/work/nspluginwrapper-1.3.0'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED prerm: 1
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: www-plugins/nspluginwrapper-1.3.0 failed (postrm phase):
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *   ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   ebuild.sh, line 1818:  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 =www-plugins/nspluginwrapper-1.3.0',
 * the complete build log and the output of 'emerge -pqv =www-plugins/nspluginwrapper-1.3.0'.
 * The complete build log is located at '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/temp/environment'.
 * S: '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/work/nspluginwrapper-1.3.0'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: www-plugins/nspluginwrapper-1.3.0 failed:
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   misc-functions.sh, line   17:  Called source '/usr/lib64/portage/bin/ebuild.sh'
 *           ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *           ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *           ebuild.sh, line 1818:  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 =www-plugins/nspluginwrapper-1.3.0',
 * the complete build log and the output of 'emerge -pqv =www-plugins/nspluginwrapper-1.3.0'.
 * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/'
 * The complete build log is located at '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/temp/environment'.
 * S: '/var/tmp/binpkgs/www-plugins/nspluginwrapper-1.3.0/work/nspluginwrapper-1.3.0'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED postrm: 1
 * The 'postrm' phase of the 'www-plugins/nspluginwrapper-1.3.0' package
 * has failed with exit value 1.
 *
 * The problem occurred while executing the ebuild file named
 * 'nspluginwrapper-1.3.0.ebuild' located in the '/var/db/pkg/www-
 * plugins/nspluginwrapper-1.3.0' directory. If necessary, manually remove
 * the environment.bz2 file and/or the ebuild file located in that
 * directory.
 *
 * Removal of the environment.bz2 file is preferred since it may allow the
 * removal phases to execute successfully. The ebuild will be sourced and
 * the eclasses from the current portage tree will be used when necessary.
 * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
 * removal phases to be skipped entirely.
>>> Unmerging x11-proto/fontcacheproto-0.1.3...
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: x11-proto/fontcacheproto-0.1.3 failed (prerm phase):
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *   ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   ebuild.sh, line 1818:  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 =x11-proto/fontcacheproto-0.1.3',
 * the complete build log and the output of 'emerge -pqv =x11-proto/fontcacheproto-0.1.3'.
 * The complete build log is located at '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/temp/environment'.
 * S: '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/work/fontcacheproto-0.1.3'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * 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.
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: x11-proto/fontcacheproto-0.1.3 failed:
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   misc-functions.sh, line   17:  Called source '/usr/lib64/portage/bin/ebuild.sh'
 *           ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *           ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *           ebuild.sh, line 1818:  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 =x11-proto/fontcacheproto-0.1.3',
 * the complete build log and the output of 'emerge -pqv =x11-proto/fontcacheproto-0.1.3'.
 * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/'
 * The complete build log is located at '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/temp/environment'.
 * S: '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/work/fontcacheproto-0.1.3'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED prerm: 1
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: x11-proto/fontcacheproto-0.1.3 failed (postrm phase):
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *   ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *   ebuild.sh, line 1818:  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 =x11-proto/fontcacheproto-0.1.3',
 * the complete build log and the output of 'emerge -pqv =x11-proto/fontcacheproto-0.1.3'.
 * The complete build log is located at '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/temp/environment'.
 * S: '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/work/fontcacheproto-0.1.3'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: No such file or directory
 * ERROR: x11-proto/fontcacheproto-0.1.3 failed:
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *   misc-functions.sh, line   17:  Called source '/usr/lib64/portage/bin/ebuild.sh'
 *           ebuild.sh, line 1950:  Called preprocess_ebuild_env
 *           ebuild.sh, line 1837:  Called filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
 *           ebuild.sh, line 1818:  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 =x11-proto/fontcacheproto-0.1.3',
 * the complete build log and the output of 'emerge -pqv =x11-proto/fontcacheproto-0.1.3'.
 * This ebuild is from an overlay named 'gentoo': '/var/db/pkg/'
 * The complete build log is located at '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/temp/environment'.
 * S: '/var/tmp/binpkgs/x11-proto/fontcacheproto-0.1.3/work/fontcacheproto-0.1.3'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: No such file or directory
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: cannot execute: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! FAILED postrm: 1
 * The 'postrm' phase of the 'x11-proto/fontcacheproto-0.1.3' package has
 * failed with exit value 1.
 *
 * The problem occurred while executing the ebuild file named
 * 'fontcacheproto-0.1.3.ebuild' located in the
 * '/var/db/pkg/x11-proto/fontcacheproto-0.1.3' 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.
Packages installed:   764
Packages in world:    40
Packages in system:   51
Required packages:    764
Number removed:       4

 * GNU info directory index is up-to-date.
Aspire-Gentoo linux #