Attempts to emerge imlib (imlib-1.9.14-r1.ebuild) fails with Portage 2.0.13 with an access violation error. Error message reproduced below. It seems to be breaking the sandbox protection. Compiles successfully on system running Portage 2.0.11 Ian /bin/sh ./mkinstalldirs /usr/share/aclocal /bin/install -c -m 644 ./imlib.m4 /usr/share/aclocal/imlib.m4 ACCESS DENIED unlink: /usr/share/aclocal/imlib.m4 /bin/install: cannot remove `/usr/share/aclocal/imlib.m4': Permission denied make[2]: *** [install-m4dataDATA] Error 1 make[2]: Leaving directory `/var/tmp/portage/imlib-1.9.14-r1/work/imlib-1.9.14' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/var/tmp/portage/imlib-1.9.14-r1/work/imlib-1.9.14' make: *** [install-recursive] Error 1 !!! ERROR: The ebuild did not complete successfully. !!! Function src_install, Line 7, Exitcode 2 !!! (no error message) --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-imlib-1.9.14-r1-874.log" unlink: /usr/share/aclocal/imlib.m4 -------------------------------------------------------------------------------- !!! emerge aborting on /usr/portage/media-libs/imlib/imlib-1.9.14-r1.ebuild . epsilon portage # emerge --version
sorry about that. fixed in portage. rsync'able whenever your rsync mirror updates itself.