Re: SV: [cobalt-users] Latest glibc package breaks vim

[phoenix hawk <phawk@xxxxxxxxxxxxxxx>]

Henrik Bro wrote:

> Anyone found a solution to this problem?
>
> /henrik
>
> -----Oprindelig meddelelse-----
> Fra: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx] På vegne af Leslie Herps
> Sendt: 22. maj 2003 11:01
> Til: cobalt-users@xxxxxxxxxxxxxxx
> Emne: Re: [cobalt-users] Latest glibc package breaks vim
>
>
>  
>
> > I've upgraded the patches in the order that the Bluelinq system has
> >    
> emailed me.
>  
>
> > In this case I updated vim a while ago, and received an email from my
> >    
> Cobalt
>  
>
> > this morning telling me a new glibc patch was available.
> >    
>
> Sorry, I thought we were talking RAQ4, that is how I did it...
> RAQ550:
> http://sunsolve.sun.com/pub-cgi/show.pl?target=cobalt/raq550.eng&nav=patchpa
> ge
>
> vim update comes AFTER glibc...
>
> You COULD try and take apart the vim package, and manually reinstall the
> RPMs..??
>
>  
Leslie, I think Henrik was talking about this patch:
RaQ550-All-Security-0.0.2-15578
Version 2 of the glibc update for RAQ 550.

Sun's quality control has been steadily going
downhill, the recent kernel patch for the ptrace
vulnerability was not that stable, and now that
glibc patch has broken my vim as well.

*sigh* It's a new box too... (of course we could
uninstall and reinstall vim via rpm, etc), but why can't
Sun do it? A single test/effort on their part could
save hundreds of us from going through "Sun's
Updates (from) Hell" ie. wondering if you should be the first
to patch *or* wait and see if someone else has tried it
and it breaks his box first.


Regards.