I just discovered that I get strange access violations with sys-apps/portage-2.1.5.2 when emerging sys-apps/sandbox-1.2.18.1-r2 as well as dev-libs/openssl-0.9.8g-r1. All other packages seem to be fine as far as I can tell. For sandbox I get the following >>> Emerging (1 of 1) sys-apps/sandbox-1.2.18.1-r2 to / * sandbox-1.2.18.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking sandbox-1.2.18.1.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking sandbox-1.2.18.1.tar.bz2 to /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work * Applying sandbox-1.2.18.1-open-normal-fail.patch ... [ ok ] * Applying sandbox-1.2.18.1-open-cloexec.patch ... [ ok ] >>> Source unpacked. >>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ... * If configure fails with a 'cannot run C compiled programs' error, try this: * FEATURES=-sandbox emerge sandbox ACCESS DENIED unlink: /usr/lib/portage/pym/portage_exception.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/cache/__init__.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/cache/cache_errors.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/cvstree.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/xpak.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/getbinpkg.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/output.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_const.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_util.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_dep.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_versions.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_data.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_manifest.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_checksum.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_exec.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_gpg.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_locks.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_localization.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/eclass_cache.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_update.pyo ACCESS DENIED unlink: /usr/lib/portage/pym/portage_selinux.pyo * Configuring sandbox for ABI=default... and the same ACCESS DENIED thingy right after the compilation is done >>> Source compiled. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-10492.log" unlink: /usr/lib/portage/pym/portage_exception.pyo unlink: /usr/lib/portage/pym/portage.pyo unlink: /usr/lib/portage/pym/cache/__init__.pyo unlink: /usr/lib/portage/pym/cache/cache_errors.pyo unlink: /usr/lib/portage/pym/cvstree.pyo unlink: /usr/lib/portage/pym/xpak.pyo unlink: /usr/lib/portage/pym/getbinpkg.pyo unlink: /usr/lib/portage/pym/output.pyo unlink: /usr/lib/portage/pym/portage_const.pyo unlink: /usr/lib/portage/pym/portage_util.pyo unlink: /usr/lib/portage/pym/portage_dep.pyo unlink: /usr/lib/portage/pym/portage_versions.pyo unlink: /usr/lib/portage/pym/portage_data.pyo unlink: /usr/lib/portage/pym/portage_manifest.pyo unlink: /usr/lib/portage/pym/portage_checksum.pyo unlink: /usr/lib/portage/pym/portage_exec.pyo unlink: /usr/lib/portage/pym/portage_gpg.pyo unlink: /usr/lib/portage/pym/portage_locks.pyo unlink: /usr/lib/portage/pym/portage_localization.pyo unlink: /usr/lib/portage/pym/eclass_cache.pyo unlink: /usr/lib/portage/pym/portage_update.pyo unlink: /usr/lib/portage/pym/portage_selinux.pyo For openssl I get the same complaint right after the compile phase but not the one at the beginning. Reverting back to the current stable portage-2.1.4.4 fixes all these issue. I am not quite sure how to test this further. Please let me know what additional info I should provide if any. The box on which this happens is fully ~x86. Thanks, Markus
Have you recently updated python? If so, normally you need to run python-updater in order to avoid sandbox access violations like those. Simply reinstalling portage (regardless of which version) should solve any sandbox violations for /usr/lib/portage/pym/*.py[co] files.
Hi Zac, Thanks much for your feedback and no, I haven't upgraded python on this machine. Re-emerging portage does not help (I've done it multiple times) only downgrading to the stable version. Strangely, I can emerge 99.9% of all packages just fine. Only sandbox and openssl consistently bomb with sys-apps/portage-2.1.5.2 for some reason I don't understand. Thanks for your help. Best, Markus
This issue has disappeared with 2.2_rc1 hence I am closing this one as fixed. Thanks, Markus
