public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads-Up sys-lib/com_err breaks Apps
Date: Fri, 08 Jul 2005 14:28:27 +0800	[thread overview]
Message-ID: <1120804108.29226.70.camel@neuromancer.home.net> (raw)
In-Reply-To: <42CE1775.4030503@gmail.com>

[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@gentoo.org mailing list



  reply	other threads:[~2005-07-08  6:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08  5:38 [gentoo-user] Heads-Up sys-lib/ss breaks Apps Ow Mun Heng
2005-07-08  6:04 ` Zac Medico
2005-07-08  6:28   ` Ow Mun Heng [this message]
2005-07-08  7:11     ` [gentoo-user] Heads-Up sys-lib/com_err " Zac Medico
2005-07-08  7:38     ` W.Kenworthy
2005-07-08  7:53       ` Ow Mun Heng
2005-07-08 15:56         ` Roy Wright
2005-07-09 11:21           ` Peter Ruskin
2005-07-09 12:04             ` Peter Ruskin
2005-07-10  1:24               ` Roy Wright
2005-07-08 15:52 ` [gentoo-user] Heads-Up sys-lib/ss " Ron Bickers
2005-07-08 16:51   ` Uwe Thiem
2005-07-08 17:47   ` kashani
2005-07-09  1:56     ` Allan Gottlieb
2005-07-10  1:41       ` Ow Mun Heng
2005-07-08 19:17   ` Rumen Yotov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1120804108.29226.70.camel@neuromancer.home.net \
    --to=ow.mun.heng@wdc.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox