# emerge gimp-print Calculating dependencies ...done! >>> emerge media-gfx/gimp-print-4.2.2 to / [...] make[4]: Entering directory `/var/tmp/portage/gimp-print-4.2.2/work/gimp-print-4.2.2/src/foomatic' if test -n "" ; then \ /bin/sh ../../scripts/mkinstalldirs `/usr/sbin/foomatic-kitload -l` ; \ /usr/sbin/foomatic-kitload -f -d -k foomatic-db/gimp-print ; \ else \ /usr/sbin/foomatic-kitload -f -k foomatic-db/gimp-print ; \ fi ACCESS DENIED open_wr: /usr/share/foomatic/kitload2.log sh: /usr/share/foomatic/kitload2.log: Permission denied ACCESS DENIED open_wr: /usr/share/foomatic/kitload.log tee: /usr/share/foomatic/kitload.log: Permission denied Then the ebuild hung until jugdement day. Has anyone a idea?
I do not experience this same problem. It emerges without so much as a hiccup for me. What version of portage are you using? I am using 2.0.38 without any problems.
I'm getting the same error with portage 2.0.38.
I'am using portage 2.0.38 too.
I am also experiencing this problem with portage 2.0.38.
Here is some more context: make[4]: Entering directory `/var/tmp/portage/gimp-print-4.2.2/work/gimp-print-4.2.2/src/foomatic' if test -n "" ; then \ /bin/sh ../../scripts/mkinstalldirs `/usr/local/sbin/foomatic-kitload -l` ; \ /usr/local/sbin/foomatic-kitload -f -d -k foomatic-db/gimp-print ; \ else \ /usr/local/sbin/foomatic-kitload -f -k foomatic-db/gimp-print ; \ fi ACCESS DENIED open_wr: /usr/local/share/foomatic/kitload2.log sh: /usr/local/share/foomatic/kitload2.log: Permission denied ACCESS DENIED open_wr: /usr/local/share/foomatic/kitload.log tee: /usr/local/share/foomatic/kitload.log: Permission denied Note that I have foomatic installed under /usr/local (there is no ebuild for foomatic).
same problem for me, here. i've got tar working like crazy for hours (i stopped after 12 hours...)
The reported problem appears to be due to foomatic being installed on your system (not via portage as we don't have foomatic in portage)... I am currently working on adding foomatic to portage so we can have a more complete printing system installation. I will post again on this bug when I get foomatic added and testing finished on gimp-print
foomatic has been added to portage. With this package added to portage I finally experience the problem as reported with gimp-print. I am working through install issues right now.
I have uploaded a new gimp-print-4.2.2.ebuild which should have all required fixes. It now depends on foomatic and should not be sandboxing anymore. :) Please test this new ebuild and let me know how things go.
Gimp-print compile fine now and things seems to work as they should. Nice work Nick :-)