This report is a reminder for users :whoever emerged sphinx3 will emerge kdelibs against /usr/lib/libutil.so.0 (and using /usr/lib/libutil.la)... that's the vrong version. This may have impredictable results, in the future (compiletime or runtime bugs). The report of the issue is at bug# 145667. To who emerged sphinx3 : To check if you're affected you can do an #equery b /usr/lib/libutil.so if the result is only glibc you're safe, if is sphinx3 too you need to correct that (and wait an upgrade to sphinx3 before re-emerging it!) you can correct doin an: #emerge -C sphinx3 ; emerge -1 glibc ; revdep-rebuild --library libutil.so.0 (CARE: After removing sphinx3 you'll need to emerge glibc before rebooting.) Please do not close this report until the bug it depends on is fixed.
As a note to anyone who needs to run the emerge sequence documented in comment #0: it would be safer to emerge glibc into a .tbz2, then unmerge sphinx3, then emerge the glibc tbz2 into the live filesystem. By doing so, you reduce the window of time in which a reboot would be bad from the length of a glibc build to just a few seconds. To implement the modified approach, run: emerge -1B glibc && emerge -C -a sphinx3 && emerge -1k glibc && revdep-rebuild --library libutil.so.0 Notes: * This leaves behind a glibc binary package in your $PKGDIR. This is harmless, but you may want to clean it up to recover disk space. You should leave it around until you are confident your C library has survived the upgrade. * I do not have sphinx3 merged, so I cannot attest to whether this pipeline works. I am going simply on the approach that glibc should be built and ready to install before sphinx3 is unmerged. * I switched the command chain from semicolons to ampersands to ensure that a failure in one step avoids execution of the next step. You may find it preferable to execute each fragment in turn, stopping to review the results after each step. Just beware the warning in the "CARE:" line in comment #0.
I'll be closing this in a week to give opputinity to anyone who updated sphinx3 and now has issues in kde to read....
Ok, could be enough, closing.
