-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Harry Putnam wrote: > Volker Armin Hemmann <volkerar...@googlemail.com> writes: > >>> On next boot, the problem with hal daemon reported above started. >> and you did etc-update/cfg-update after the update? Have you read the >> messages >> with elogv? Same hal versions here - no problems at all. > > I've completed the cfg-update -u and there was only one file really > changed. sshd_config which I left alone. > > > However I did remember to make sure the package I had trouble with > `glibc' did get installed. It did not and will not. > > Ending with this stuff below... I'm not at all sure what to make of > it. > Is it related to hal daemon problem? > emerge -vuD glibc > [...] > usr/lib/libc_nonshared.a >>>> Completed installing glibc-2.9_p20081201-r2 into >>>> /var/tmp/portage/sys-libs/glibc-2.9_p20081201-r2/image/ > [snip sandbox error]
That actually is completely separate, and is due to a bad version of sandbox (if I'm not mistaken) - you probably need to either upgrade or downgrade sys-apps/sandbox to 1.6-r2 (1.7 appears to be broken in this regard). If I'm right, then this probably is bug 264399. - -- ABCD -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknYNroACgkQOypDUo0oQOo2uQCgmpl2YRJbKnDr7TghvcFt5Gu5 WNUAoMUctbHHxr/3LDggyqQhi4D1URJZ =IZpq -----END PGP SIGNATURE-----
