every time coreutils is emerged to the latest version, no package can be emerged. Reproducible: Always Steps to Reproduce: 1. emerge coreutils 2. emerge (any other pkg) 3. break Actual Results: here is merging `screen` right after coreutils update: touch: setting times of `/var/tmp/portage/app-misc/screen-4.0.3/.unpacked': Bad address * * ERROR: app-misc/screen-4.0.3 failed. * Call stack: * ebuild.sh, line 2104: Called ebuild_main * ebuild.sh, line 2002: Called dyn_unpack * ebuild.sh, line 687: Called die * The specific snippet of code: * touch "${PORTAGE_BUILDDIR}/.unpacked" || die "IO Failure -- Failed 'touch .unpacked' in ${PORTAGE_BUILDDIR}" * The die message: * IO Failure -- Failed 'touch .unpacked' in /var/tmp/portage/app-misc/screen-4.0.3 * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-misc/screen-4.0.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-misc/screen-4.0.3/temp/environment'. * >>> Failed to emerge app-misc/screen-4.0.3, Log file: >>> '/var/tmp/portage/app-misc/screen-4.0.3/temp/build.log' This has been tested on a fresh gentoo installation with the same result.
Did you run 'hash -r', as said ewarn after emerging coreutils?
yes.
The meaning of "latest" depends on your keyword settings and base system. For stable users, most architectures would consider coreutils-7.1 latest available. For unstable, coreutils-7.2 is available. Could you be more specific about what version you are using? The output of "emerge --info" and "emerge --pretend --verbose coreutils" would be helpful in identifying what version is affected.
That's most likely a bug that has hit OpenVZ users ... please upgrade your kernel to a version from this year, the error should go away then.
*** This bug has been marked as a duplicate of bug 233280 ***
