On Fri, 2007-11-09 at 12:55 -0800, [EMAIL PROTECTED] wrote: > An esync and emerge resulted in 62 out of 113 packages failing emerge > with errors about no write access to /etc/passwd and /etc/group. This > is a dual opteron system, ~amd64, with both kernels 2.6.22-gentoo-r8 > and 2.6.23-gentoo-r1. This particular esync began fine, 113 packages > to build. The last package to build before the first failure was > glib-2.7. The system seems to be running fine; I have rebooted, > logged in, etc. Is this some glib 2.7 feature? Should I just keep > running and wait for glib-2.7-r1? > > > > ================ example emerge log > >>> Emerging (1 of 62) dev-libs/glib-2.14.3 to / > * glib-2.14.3.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ > ok ] > * checking ebuild checksums ;-) ... [ > ok ] > * checking auxfile checksums ;-) ... [ > ok ] > * checking miscfile checksums ;-) ... [ > ok ] > * checking glib-2.14.3.tar.bz2 ;-) ... [ > ok ] > ACCESS DENIED open_wr: /etc/passwd > ... > ACCESS DENIED open_wr: /etc/passwd > --------------------------- ACCESS VIOLATION SUMMARY > --------------------------- > LOG FILE = "/var/log/sandbox/sandbox-dev-libs_-_glib-2.14.3-11618.log" > > open_wr: /etc/passwd > ... > open_wr: /etc/passwd >
Wow, I don't understand how running checksums on the distfile would attempt to open /etc/passwd :| What version of portage are you running? Nevertheless, I was able to able to emerge dev-libs/glib-2.14.3 just fine, and I'm running glibc 2.7. -a -- [EMAIL PROTECTED] mailing list
