Hola, Short version is that via bug 112082 plus glibc upstream doing something stupid, a lovely bug has reared it's head. Basically, users upgrading from glibc-2.3.5.200*.ebuild have libc.so-2.3.90.so, and glibc-2.3.6.ebuild has libc.so-2.3.6.so .
ldconfig views 2.3.90 as greater then 2.3.6; during merge, portage views 2.3.5.200* -> 2.3.6 as an upgrade, and triggers an ldconfig call. Said call, and said upstream weird lib versioning results in ld.so.6 being reset from libc-2.3.6.so to libc-2.3.90.so , which obviously gets a bit screwed up when unmerge comes around and yanks the lib. Az split off a patch for it (after lots of fun digging) to correct it; we're going to need a rc8 covering this one offhand, since it's invalid linking in certain cases. Thoughts/complaints/issues/further testing? ~harring
pgpvktNhMeOtF.pgp
Description: PGP signature
