Code: Select all
fdsa ~ # emerge portage
* IMPORTANT: 1 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-apps/portage-2.2.28::gentoo
* portage-2.2.28.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
/var/tmp/portage/._portage_reinstall_.mi4xkh3d/bin/ebuild-helpers/xattr/install: line 40: /usr/bin/python3.4: Permission denied
/var/tmp/portage/._portage_reinstall_.mi4xkh3d/bin/ebuild-helpers/xattr/install: line 40: exec: /usr/bin/python3.4: cannot execute: Permission denied
* ERROR: sys-apps/portage-2.2.28::gentoo failed (unpack phase):
* Failed to create dir '/var/tmp/portage/sys-apps/portage-2.2.28/work'
*
* Call stack:
* ebuild.sh, line 805: Called __ebuild_main 'unpack'
* phase-functions.sh, line 974: Called __dyn_unpack
* phase-functions.sh, line 240: Called die
* The specific snippet of code:
* install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.2.28::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.2.28::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.2.28/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.2.28/temp/environment'.
* Working directory: '/var/tmp/portage/._portage_reinstall_.mi4xkh3d/pym'
* S: '/var/tmp/portage/sys-apps/portage-2.2.28/work/portage-2.2.28'
/var/tmp/portage/._portage_reinstall_.mi4xkh3d/bin/ebuild-ipc: line 7: /usr/bin/python3.4: Permission denied
/var/tmp/portage/._portage_reinstall_.mi4xkh3d/bin/ebuild-ipc: line 7: exec: /usr/bin/python3.4: cannot execute: Permission denied
* The ebuild phase 'unpack' 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 to emerge sys-apps/portage-2.2.28, Log file:
>>> '/var/tmp/portage/sys-apps/portage-2.2.28/temp/build.log'
* Messages for package sys-apps/portage-2.2.28:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* ERROR: sys-apps/portage-2.2.28::gentoo failed (unpack phase):
* Failed to create dir '/var/tmp/portage/sys-apps/portage-2.2.28/work'
*
* Call stack:
* ebuild.sh, line 805: Called __ebuild_main 'unpack'
* phase-functions.sh, line 974: Called __dyn_unpack
* phase-functions.sh, line 240: Called die
* The specific snippet of code:
* install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}" || die "Failed to create dir '${WORKDIR}'"
*
* If you need support, post the output of `emerge --info '=sys-apps/portage-2.2.28::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.2.28::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.2.28/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.2.28/temp/environment'.
* Working directory: '/var/tmp/portage/._portage_reinstall_.mi4xkh3d/pym'
* S: '/var/tmp/portage/sys-apps/portage-2.2.28/work/portage-2.2.28'
