NOTE: This is on a new install of 1.2 with portage upgraded Captured error data: make[2]: Entering directory `/var/tmp/portage/gdk-pixbuf-0.18.0-r1/work/gdk-pixbuf-0.18.0/doc' make[2]: Nothing to be done for `install-exec-am'. /bin/sh ../mkinstalldirs /usr/share/gnome/html/gdk-pixbuf mkdir /usr/share/gnome/html/gdk-pixbuf ACCESS DENIED mkdir: /usr/share/gnome/html/gdk-pixbuf mkdir: cannot create directory `/usr/share/gnome/html/gdk-pixbuf': Permission denied make[2]: *** [install-data-local] Error 1 make[2]: Leaving directory `/var/tmp/portage/gdk-pixbuf-0.18.0-r1/work/gdk-pixbuf-0.18.0/doc' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/var/tmp/portage/gdk-pixbuf-0.18.0-r1/work/gdk-pixbuf-0.18.0/doc' make: *** [install-recursive] Error 1 !!! ERROR: The ebuild did not complete successfully. !!! Function src_install, Line 4, Exitcode 2 !!! (no error message) --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-gdk-pixbuf-0.18.0-r1-19465.log" mkdir: /usr/share/gnome/html/gdk-pixbuf -------------------------------------------------------------------------------- !!! emerge aborting on /usr/portage/media-libs/gdk-pixbuf/gdk-pixbuf-0.18.0-r1.ebuild . Will attach the log file as well
Created attachment 2591 [details] Log of sandbox viloation
when did you emerge rsync last, because this problem was fixed about 2 days ago..
You mean I just spent the last few hours fixing this for nothing! Well I should say I tried to fix it as the emerge just blew up again :) I will rsync right now and try again and report back... Oh if anyone is waching this I did create a patch to mkinstalldirs that will semi deterime if sandbox path was passed to it if not it modifies the path so it points into the sandbox verses the real system.
Yes that did it. But a question why wasn't the ebuild rev'ed?
This should now be marked as fixed....