During attempt to emerge gnome I get the following error: alexhome root # emerge fam-oss Calculating dependencies ...done! >>> emerge (1 of 1) app-admin/fam-oss-2.6.10-r1 to / >>> md5 src_uri ;-) fam-2.6.10.tar.gz >>> Unpacking source... >>> Unpacking fam-2.6.10.tar.gz to /var/tmp/portage/fam-oss-2.6.10-r1/work * Applying dnotify.patch.new... [ ok ] * Applying fam-2.6.7-cleanup.patch... [ ok ] * Applying fam-oss-2.6.10-largefile.patch... [ ok ] * Applying fam-oss-2.6.10-nostatvfs.patch... [ ok ] * Working directory: /var/tmp/portage/fam-oss-2.6.10-r1/work/fam-2.6.10... * Applying libtool-relink.patch... * Applying libtool-tmp.patch... * Applying libtool-sed.patch... * Applying libtool-portage.patch... ACCESS DENIED symlink: /usr/lib/perl5/5.8.0/base.pm configure.in: installing `./missing' >>> Source unpacked. --------------------------- ACCESS VIOLATION SUMMARY ---------------------------LOG FILE = "/tmp/sandbox-fam-oss-2.6.10-r1-18638.log" symlink: /usr/lib/perl5/5.8.0/base.pm --------------------------------------------------------------------------------alexhome root # I've tried to reinstall the whole thing and received the same result. I also received the same error message from attempts to emerge some kde packages, about the same 'base.pm' file. My settings include: FEATURES="sandbox ccache userpriv"
Created attachment 17275 [details] The result of 'emerge info'
Created attachment 17276 [details] The result of 'emerge info'
Created attachment 17277 [details] The result of emerge info
Created attachment 17279 [details] The result of emerge info
Created attachment 17280 [details] The result of emerge info
please don't set all sorts of stuff, we can very well assess importance of a bug ourselves, probably better than you. And don't assign it directly to gnome just because it happens in a gnome emerge. We are not the fam maintainers really and this very much looks like a perl problem. Thank you.
I had the same error with Abiword. See Bug 27225. I also read that some people at the forums reported the same issue with exactly the same error message. Come on Perl Team, wake up!
We are starting to get a lot of bugs on this. Can someone either look into it or suggest a point of attack?
*** Bug 29675 has been marked as a duplicate of this bug. ***
*** Bug 29715 has been marked as a duplicate of this bug. ***
*** Bug 30218 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 29846 ***
