Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 9014 - gimp-print 4.2.2 doesn't install because ACCESS DENIED
Summary: gimp-print 4.2.2 doesn't install because ACCESS DENIED
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Nick Hadaway
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-11 06:17 UTC by Alex
Modified: 2003-02-04 19:42 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2002-10-11 06:17:42 UTC
# 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?
Comment 1 Nick Hadaway 2002-10-11 17:23:46 UTC
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. 
Comment 2 Regin Larsen 2002-10-12 07:36:12 UTC
I'm getting the same error with portage 2.0.38.
Comment 3 Alex 2002-10-13 13:44:46 UTC
I'am using portage 2.0.38 too. 
Comment 4 Ryan Shaw 2002-10-13 20:42:02 UTC
I am also experiencing this problem with portage 2.0.38.
Comment 5 Ryan Shaw 2002-10-13 20:45:05 UTC
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).
Comment 6 Marc Cousin 2002-10-16 02:16:55 UTC
same problem for me, here. i've got tar working like crazy for hours (i stopped
after 12 hours...)
Comment 7 Marc Cousin 2002-10-16 02:17:46 UTC
same problem for me, here. i've got tar working like crazy for hours (i stopped
after 12 hours...)
Comment 8 Nick Hadaway 2002-10-17 13:43:11 UTC
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
Comment 9 Nick Hadaway 2002-10-17 14:40:07 UTC
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.
Comment 10 Nick Hadaway 2002-10-17 15:08:03 UTC
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.
Comment 11 Regin Larsen 2002-10-18 06:27:33 UTC
Gimp-print compile fine now and things seems to work as they should.

Nice work Nick :-)