Re: [gentoo-user] Heads-Up sys-lib/com_err breaks Apps

[W.Kenworthy]

This is one reason you should not do auto-updates via cron.  It adds to
the fun in tracking down such problems.  

I also wish that emerges would stop whenever a message like this is
printed to the screen, but people have been cursing/moaning and getting
caught with dead systems by this bug for literally years - check out the
bugs for 2002 (einfo has some of them) for instance.  Some are marked
resolved, but its still broken - unless they never told anyone how to
enable the fix.

BillK


On Fri, 2005-07-08 at 14:28 +0800, Ow Mun Heng wrote:
> [Changed Subject. , should be com_err and not ss]
>
> On Thu, 2005-07-07 at 23:04 -0700, Zac Medico wrote:
> > 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 :-( ).
>
> It didn't catch everything. Right now I'm recompiling xscreensaver.
>
> The thing which I'm talking about is, if there are _specific_ caveats
> such as with this new app, it shouldn't even go ahead and
> compile/upgrade/update. It should just shoot the ebuild einfo and then
> force manual intervention.
>
> Updates are usually done at night. Output is not seen. That's why. If I
> knew that it might break anything, I wouldn't leave it overnight to
> update and then go to work and find Evo(or important "X" app) wouldn't
> work and cause undue frustration.
>
>
> --
> Ow Mun Heng
> Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM
> 98% Microsoft(tm) Free!!
> Neuromancer 14:25:41 up 22:22, 9 users, load average: 1.94, 1.73, 1.22
>
>

-- 
gentoo-user@g.o mailing list