Spoiler
/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/build.log
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: Нет такого файла или каталога
* ERROR: dev-lang/python-2.6.6-r1 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-r1',
* the complete build log and the output of 'emerge -pqv =dev-lang/python-2.6.6-r1'.
* The complete build log is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/environment'.
* S: '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/work/python-2.6.6'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: Нет такого файла или каталога
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: не могу запустить: Нет такого файла или каталога
* 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: Нет такого файла или каталога
* ERROR: dev-lang/python-2.6.6-r1 failed:
* filter-bash-environment.py failed
*
* Call stack:
* misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh'
* ebuild.sh, line 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-r1',
* the complete build log and the output of 'emerge -pqv =dev-lang/python-2.6.6-r1'.
* This ebuild is from an overlay named 'gentoo': '/var/db/pkg/'
* The complete build log is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/environment'.
* S: '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/work/python-2.6.6'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: Нет такого файла или каталога
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: не могу запустить: Нет такого файла или каталога
* 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-r1' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'python-2.6.6-r1.ebuild' located in the '/var/db/pkg/dev-
* lang/python-2.6.6-r1' directory. If necessary, manually remove the
* environment.bz2 file and/or the ebuild file located in that directory.
*
* Removal of the environment.bz2 file is preferred since it may allow the
* removal phases to execute successfully. The ebuild will be sourced and
* the eclasses from the current portage tree will be used when necessary.
* Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
* removal phases to be skipped entirely.
/usr/lib64/portage/bin/ebuild.sh: line 1818: /usr/bin/python2.6: Нет такого файла или каталога
* ERROR: dev-lang/python-2.6.6-r1 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-r1',
* the complete build log and the output of 'emerge -pqv =dev-lang/python-2.6.6-r1'.
* The complete build log is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/environment'.
* S: '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/work/python-2.6.6'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: Нет такого файла или каталога
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: не могу запустить: Нет такого файла или каталога
* 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: Нет такого файла или каталога
* ERROR: dev-lang/python-2.6.6-r1 failed:
* filter-bash-environment.py failed
*
* Call stack:
* misc-functions.sh, line 17: Called source '/usr/lib64/portage/bin/ebuild.sh'
* ebuild.sh, line 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-r1',
* the complete build log and the output of 'emerge -pqv =dev-lang/python-2.6.6-r1'.
* This ebuild is from an overlay named 'gentoo': '/var/db/pkg/'
* The complete build log is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/temp/environment'.
* S: '/var/tmp/binpkgs/dev-lang/python-2.6.6-r1/work/python-2.6.6'
/usr/lib64/portage/bin/ebuild-ipc: line 7: /usr/bin/python2.6: Нет такого файла или каталога
/usr/lib64/portage/bin/ebuild-ipc: line 7: exec: /usr/bin/python2.6: не могу запустить: Нет такого файла или каталога
* 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-r1' package has failed
* with exit value 1.
*
* The problem occurred while executing the ebuild file named
* 'python-2.6.6-r1.ebuild' located in the '/var/db/pkg/dev-
* lang/python-2.6.6-r1' directory. If necessary, manually remove the
* environment.bz2 file and/or the ebuild file located in that directory.
*
* Removal of the environment.bz2 file is preferred since it may allow the
* removal phases to execute successfully. The ebuild will be sourced and
* the eclasses from the current portage tree will be used when necessary.
* Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
* removal phases to be skipped entirely.
Соответственно, не работает питон, emerge и т.д. В чем может быть дело и как это лечить?
upd. Погорячился. все вылечилось временным созданием симлинка python2.6 на python2.7, eselect'ом версии 2.7