Ow Mun Heng wrote: > If you guys did a emerge -uDav world anytime these past few days. I'm > sure you'll be hit by the libcom_err.so.3 error. > > This was really bad. Ruined half my working day since I can't get Evo to > come up. > > Anyway, the ebuild _does_ mentioned breaking compatibility and stuffs. > > > $grep einfo /usr/portage/sys-libs/com_err/*.ebuild > > einfo "PLEASE PLEASE take note of this" > einfo "Please make *sure* to run revdep-rebuild now" > einfo "Certain things on your system may have linked against a" > einfo "different version of com_err -- those things need to be" > einfo "recompiled. Sorry for the inconvenience" > > Which is a huge bummer since most of us don't go checking the ebuilds > for these specific lines. How I wish It would just abort and BLAST the > Einfo on the screen for me to see the next day and decide to do it > manually. > > Oh well... It's fixed. > > >
Shouldn't revdep-rebuild solve issues like that? I always run revdep-rebuild after updates and I don't recall having any problem with this com_err update ( I know lots of others did though :-( ). Zac -- [email protected] mailing list
