[gentoo-user] Heads-Up sys-lib/ss breaks Apps

[gentoo-user] Heads-Up sys-lib/ss breaks Apps

[Ow Mun Heng]

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.



-- 
Ow Mun Heng
Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM
98% Microsoft(tm) Free!! 
Neuromancer 11:54:59 up 19:51, 7 users, load average: 1.67, 1.49, 1.13 


-- 
gentoo-user@gentoo.org mailing list

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

[Zac Medico]

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

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

[Ow Mun Heng]

[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

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

[Zac Medico]

Ow Mun Heng wrote:
> 
> It didn't catch everything. Right now I'm recompiling xscreensaver.
> 

revdep-rebuild didn't catch everything?  Do we know why?  I wouldn't want that to happen to me ;-).

> 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.
> 
> 

That seems reasonable.

Zac
-- 
gentoo-user@gentoo.org mailing list

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

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

[Ow Mun Heng]

On Fri, 2005-07-08 at 15:38 +0800, W.Kenworthy wrote:
> This is one reason you should not do auto-updates via cron.  It adds to
> the fun in tracking down such problems. 

It wasn't cron. I did the emerge prior to heading off to bed.

Perhaps a good thing would be when the emerge -uDpv world output can be
formatted to include einfo messages, or rather include "ecriticalinfo"
outputs. (Just like IIRC updating portage will make that happen.)

Now, that would be a feature worth having.

> 
> 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.

Yeah.. I know.. I wonder if any of the devs here has anything to say on
why the issue still stands?

-- 
gentoo-user@gentoo.org mailing list

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

[Roy Wright]

Here's a perl script to display the einfo lines of packages to
be merged.  Just run it with the same options you will use for
emerge.  Example:

  einfo -uDN world >einfo.txt
  emerge -uDN world
  less einfo.txt

You will probably want to save the output to refer to after
emerging.

Enjoy,
Roy

#!/usr/bin/perl

# this script will run emerge with the given command line options plus
# "--pretend".  It will then grep all of the packages to be merged looking
# for einfo lines to display.

$portage = '/usr/portage';
$emerge = "emerge @ARGV --pretend";

open(EMERGE, "$emerge|") || die "unable to open $emerge\n";
while(<EMERGE>) {
        if(/\[[^\]]+\]\s+(\S+)\/(\S+)\-(\d\S*)\s/) {
                findInfo($1,$2,$3);
        }
}
close(EMERGE);

exit 0;

sub findInfo
{
        local ($package,$name,$ver) = @_;
        local $pkgDir = "$portage/$package/$name";
        local $ebuild = "$pkgDir/$name-$ver.ebuild";
        print "$ebuild\n";
        if(-T $ebuild) {
                open(EBUILD, "<$ebuild") || warn "unable to read $ebuild\n";
                while(<EBUILD>) {
                        if(/(einfo.*)$/) {
                                print "  $1\n";
                        }
                }
                close(EBUILD);
        }
        print "\n";
}


Ow Mun Heng wrote:

>Perhaps a good thing would be when the emerge -uDpv world output can be
>formatted to include einfo messages, or rather include "ecriticalinfo"
>outputs. (Just like IIRC updating portage will make that happen.)
>
>Now, that would be a feature worth having.
>  
>
-- 
gentoo-user@gentoo.org mailing list

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

[Peter Ruskin]

On Friday 08 July 2005 16:56, Roy Wright wrote:
> Here's a perl script to display the einfo lines of packages to
> be merged.  Just run it with the same options you will use for
> emerge.  Example:
>
>   einfo -uDN world >einfo.txt
>   emerge -uDN world
>   less einfo.txt
>
> You will probably want to save the output to refer to after
> emerging.
>
> Enjoy,
> Roy
>
> #!/usr/bin/perl
>
> # this script will run emerge with the given command line options
> plus # "--pretend".  It will then grep all of the packages to be
> merged looking # for einfo lines to display.
>
> $portage = '/usr/portage';
> $emerge = "emerge @ARGV --pretend";
>
> open(EMERGE, "$emerge|") || die "unable to open $emerge\n";
> while(<EMERGE>) {
>         if(/\[[^\]]+\]\s+(\S+)\/(\S+)\-(\d\S*)\s/) {
>                 findInfo($1,$2,$3);
>         }
> }
> close(EMERGE);
>
> exit 0;
>
> sub findInfo
> {
>         local ($package,$name,$ver) = @_;
>         local $pkgDir = "$portage/$package/$name";
>         local $ebuild = "$pkgDir/$name-$ver.ebuild";
>         print "$ebuild\n";
>         if(-T $ebuild) {
>                 open(EBUILD, "<$ebuild") || warn "unable to read
> $ebuild\n"; while(<EBUILD>) {
>                         if(/(einfo.*)$/) {
>                                 print "  $1\n";
>                         }
                        if(/(ewarn.*)$/) {
                                print "  $1\n";
                        }
                        if(/(eerror.*)$/) {
                                print "  $1\n";
                        }
>                 }
>                 close(EBUILD);
>         }
>         print "\n";
> }
>
Thanks, nice script Roy.  With the ewarn and eerror additions above 
you get even more information.

I use the following in root's crontab:
# sync Gentoo nightly and check for updates
0 0 * * 1-6 /usr/sbin/esync -ns && /usr/bin/update-eix -q 
&& /usr/bin/emerge world -uNvplt && /usr/local/bin/einfo -uN world
# sync Gentoo weekly and check (deep) for updates
0 0 * * 7 /usr/sbin/esync -ns && /usr/bin/update-eix -q 
&& /usr/bin/emerge world -uNDvtpl && /usr/local/bin/einfo -uND 
world

-- 
Peter
========================================================================
Gentoo Linux: Portage 2.0.51.19.	kernel-2.6.12-gentoo.
i686 AMD Athlon(tm) XP 3200+.		gcc(GCC): 3.3.5-20050130.
KDE: 3.4.1.				Qt: 3.3.4.
========================================================================
-- 
gentoo-user@gentoo.org mailing list

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

[Peter Ruskin]

On Saturday 09 July 2005 12:21, Peter Ruskin wrote:
> I use the following in root's crontab:
> # sync Gentoo nightly and check for updates
> 0 0 * * 1-6 /usr/sbin/esync -ns && /usr/bin/update-eix -q
> && /usr/bin/emerge world -uNvplt && /usr/local/bin/einfo -uN
> world # sync Gentoo weekly and check (deep) for updates
> 0 0 * * 7 /usr/sbin/esync -ns && /usr/bin/update-eix -q
> && /usr/bin/emerge world -uNDvtpl && /usr/local/bin/einfo -uND
> world

Forgot to mention, I also have this in root's crontab:
MAILTO=peter
...so when I get up in the morning and check my mail I have all the 
details I need.

This is much better than waiting for Bug #11359 to be properly 
resolved.

-- 
Peter
========================================================================
Gentoo Linux: Portage 2.0.51.19.	kernel-2.6.12-gentoo.
i686 AMD Athlon(tm) XP 3200+.		gcc(GCC): 3.3.5-20050130.
KDE: 3.4.1.				Qt: 3.3.4.
========================================================================
-- 
gentoo-user@gentoo.org mailing list

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

[Roy Wright]

Thanks for the extension (checking for ewarn & eerror).  I'm
still getting a handle on gentoo ;-)

I borrowed a portage.cron script from off of this list and run
it under cron.daily.  One of my changes to the script is to run
einfo (I also pull down the files so they are ready for compile
after I receive the cron email and review).

Have fun,
Roy

-- 
gentoo-user@gentoo.org mailing list

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

[Ron Bickers]

On Fri July 8 2005 01:38 am, Ow Mun Heng wrote:

> 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.

I have this concern as well.  Also, when emerging multiple packages, the 
helpful and sometimes necessary output at the end of each merge is easily 
missed as the next package begins.  It would be nice to at least have these 
messages logged somewhere.  Are they?  Can they be without patching portage?

-- 
Ron
-- 
gentoo-user@gentoo.org mailing list

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

[Uwe Thiem]

On Friday 08 July 2005 16:52, Ron Bickers wrote:
> On Fri July 8 2005 01:38 am, Ow Mun Heng wrote:
> > 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.
>
> I have this concern as well.  Also, when emerging multiple packages, the
> helpful and sometimes necessary output at the end of each merge is easily
> missed as the next package begins.  It would be nice to at least have these
> messages logged somewhere.  Are they?  Can they be without patching
> portage?

emerge --update world > /var/log/world_update.log 2>&1

or if you want to see it on screen as well:

emerge --update world | tee /var/log/world_update.log 2>&1

Uwe

-- 
95% of all programmers rate themselves among the top 5% of all software 
developers. - Linus Torvalds

http://www.uwix.iway.na (last updated: 20.06.2004)
-- 
gentoo-user@gentoo.org mailing list

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

[kashani]

Ron Bickers wrote:
> On Fri July 8 2005 01:38 am, Ow Mun Heng wrote:
> 
> 
>>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.
> 
> 
> I have this concern as well.  Also, when emerging multiple packages, the 
> helpful and sometimes necessary output at the end of each merge is easily 
> missed as the next package begins.  It would be nice to at least have these 
> messages logged somewhere.  Are they?  Can they be without patching portage?
> 

mkdir /var/log/portage
echo "PORT_LOGDIR=/var/log/portage" >> /etc/make.conf

kashani
-- 
gentoo-user@gentoo.org mailing list

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

[Allan Gottlieb]

At Fri, 08 Jul 2005 12:47:51 -0500 kashani <kashani-list@badapple.net> wrote:

> Ron Bickers wrote:
>> On Fri July 8 2005 01:38 am, Ow Mun Heng wrote:
>>
>>>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.
>> I have this concern as well.  Also, when emerging multiple packages,
>> the helpful and sometimes necessary output at the end of each merge
>> is easily missed as the next package begins.  It would be nice to at
>> least have these messages logged somewhere.  Are they?  Can they be
>> without patching portage?
>>
> mkdir /var/log/portage
> echo "PORT_LOGDIR=/var/log/portage" >> /etc/make.conf

Although I didn't check this particular case, it is normally true that
emerge generates *two* logs in the directory for each build.  The
large one contains the normal stuff (e.g., compiler output); the small
one contains the important tidbits such as those mentioned above.

allan
-- 
gentoo-user@gentoo.org mailing list

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

[Ow Mun Heng]

On Fri, 2005-07-08 at 21:56 -0400, Allan Gottlieb wrote:
> At Fri, 08 Jul 2005 12:47:51 -0500 kashani <kashani-list@badapple.net> wrote:
> 
> > Ron Bickers wrote:
> >> On Fri July 8 2005 01:38 am, Ow Mun Heng wrote:
> >>
> >>>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.

> .  It would be nice to at
> >> least have these messages logged somewhere.  Are they?  Can they be
> >> without patching portage?
> >>
> > mkdir /var/log/portage
> > echo "PORT_LOGDIR=/var/log/portage" >> /etc/make.conf
> 
> Although I didn't check this particular case, it is normally true that
> emerge generates *two* logs in the directory for each build.  The
> large one contains the normal stuff (e.g., compiler output); the small
> one contains the important tidbits such as those mentioned above.

Yes.. I have this set-up as well, however the caveat here is that this
will be _after_ the fact. Hence, to me, it's largely useless.

Roy Wright has written a nice util which does do nice things,
essentially just grepping the ebuild files for einfo lines and putting
it onto the screen. nice.

-- 
Ow Mun Heng
Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM
98% Microsoft(tm) Free!! 
Neuromancer 09:41:41 up 2 days, 17:38, 2 users, load average: 0.29,
0.55, 0.57 


-- 
gentoo-user@gentoo.org mailing list

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

[Rumen Yotov]

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

Ron Bickers wrote:

>On Fri July 8 2005 01:38 am, Ow Mun Heng wrote:
>
>  
>
>>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.
>>    
>>
>
>I have this concern as well.  Also, when emerging multiple packages, the 
>helpful and sometimes necessary output at the end of each merge is easily 
>missed as the next package begins.  It would be nice to at least have these 
>messages logged somewhere.  Are they?  Can they be without patching portage?
>
>  
>
Hi,
Using two tools to handle this.
First is "enotice"-tool, search for it don't have the link now.
Second as was already mentioned is: PORTLOG_DIR in make.conf.
PS: their functions are overlapping but just in case ;)
HTH. Rumen

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3397 bytes --]