- [32;01m * [39;49;00mPackage: dev-lang/python-exec-2.4.4
- [32;01m * [39;49;00mRepository: gentoo
- [32;01m * [39;49;00mMaintainer: python@gentoo.org
- [32;01m * [39;49;00mUpstream: mgorny@gentoo.org https://github.com/mgorny/python-exec/issues/
- [32;01m * [39;49;00mUSE: abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_jython2_7 python_targets_pypy python_targets_pypy3 python_targets_python2_7 python_targets_python3_4 python_targets_python3_5 python_targets_python3_6 userland_GNU
- [32;01m * [39;49;00mFEATURES: preserve-libs sandbox userpriv usersandbox
- >>> Unpacking source...
- >>> Unpacking python-exec-2.4.4.tar.bz2 to /var/tmp/portage/dev-lang/python-exec-2.4.4/work
- /var/tmp/portage/._portage_reinstall_.io4d3lml/bin/chmod-lite: line 9: /usr/src/Python-3.6.0/python: Permission denied
- /var/tmp/portage/._portage_reinstall_.io4d3lml/bin/chmod-lite: line 9: exec: /usr/src/Python-3.6.0/python: cannot execute: Permission denied
- >>> Source unpacked in /var/tmp/portage/dev-lang/python-exec-2.4.4/work
- /var/tmp/portage/._portage_reinstall_.io4d3lml/bin/phase-functions.sh: line 137: /usr/src/Python-3.6.0/python: Permission denied
- [31;01m*[0m ERROR: dev-lang/python-exec-2.4.4::gentoo failed (unpack phase):
- [31;01m*[0m filter-bash-environment.py failed
- [31;01m*[0m
- [31;01m*[0m Call stack:
- [31;01m*[0m ebuild.sh, line 767: Called __ebuild_main 'unpack'
- [31;01m*[0m phase-functions.sh, line 1045: Called __filter_readonly_variables '--filter-features'
- [31;01m*[0m phase-functions.sh, line 137: Called die
- [31;01m*[0m The specific snippet of code:
- [31;01m*[0m "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
- [31;01m*[0m
- [31;01m*[0m If you need support, post the output of `emerge --info '=dev-lang/python-exec-2.4.4::gentoo'`,
- [31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-lang/python-exec-2.4.4::gentoo'`.
- [31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-lang/python-exec-2.4.4/temp/build.log'.
- [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-exec-2.4.4/temp/environment'.
- [31;01m*[0m Working directory: '/var/tmp/portage/._portage_reinstall_.io4d3lml/pym'
- [31;01m*[0m S: '/var/tmp/portage/dev-lang/python-exec-2.4.4/work/python-exec-2.4.4'
- /var/tmp/portage/._portage_reinstall_.io4d3lml/bin/ebuild-ipc: line 7: /usr/src/Python-3.6.0/python: Permission denied
- /var/tmp/portage/._portage_reinstall_.io4d3lml/bin/ebuild-ipc: line 7: exec: /usr/src/Python-3.6.0/python: cannot execute: Permission denied
- [31;01m * [39;49;00mThe ebuild phase 'unpack' has exited unexpectedly. This type of behavior
- [31;01m * [39;49;00mis known to be triggered by things such as failed variable assignments
- [31;01m * [39;49;00m(bug #190128) or bad substitution errors (bug #200313). Normally, before
- [31;01m * [39;49;00mexiting, bash should have displayed an error message above. If bash did
- [31;01m * [39;49;00mnot produce an error message above, it's possible that the ebuild has
- [31;01m * [39;49;00mcalled `exit` when it should have called `die` instead. This behavior
- [31;01m * [39;49;00mmay also be triggered by a corrupt bash binary or a hardware problem
- [31;01m * [39;49;00msuch as memory or cpu malfunction. If the problem is not reproducible or
- [31;01m * [39;49;00mit appears to occur randomly, then it is likely to be triggered by a
- [31;01m * [39;49;00mhardware problem. If you suspect a hardware problem then you should try
- [31;01m * [39;49;00msome basic hardware diagnostics such as memtest. Please do not report
- [31;01m * [39;49;00mthis as a bug unless it is consistently reproducible and you are sure
- [31;01m * [39;49;00mthat your bash binary and hardware are functioning properly.