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