The same way I always do:
rpm -Uvh Mesa-*
This time I did a --force, since it was already
installed.
I do not know much about how rpm works, but I think
there is a problem there.
--- Axalon Bloodstone <[EMAIL PROTECTED]>
wrote:
> On Thu, 4 Nov 1999, Eugenio Diaz wrote:
>
> > --- Axalon Bloodstone <[EMAIL PROTECTED]>
> > ...
> > > > I don't see them.
> > > (stoned@Elminster)[Mandrake/RPMS]-% rpm -q Mesa
> > > Mesa-3.1cvs-6mdk
> > > (stoned@Elminster)[Mandrake/RPMS]-% rpm -V Mesa
> > > (stoned@Elminster)[Mandrake/RPMS]-% rpm -qplv
> > > Mesa-3.1cvs-6mdk.i586.rpm|grep libMesa
> > > lrwxrwxrwx root root 14 Nov 2
> > > 21:53 /usr/X11R6/lib/libMesaGL.so.3 ->
> > > libGL.so.3.1.2
> > > lrwxrwxrwx root root 15 Nov 2
> > > 21:53 /usr/X11R6/lib/libMesaGLU.so.3 ->
> > > libGLU.so.3.1.2
> > > (stoned@Elminster)[Mandrake/RPMS]-%
> >
> > I did an "rpm --force Mesa-*" and now there they
> are!
>
> how did it get installed the first time?
>
> > What is going on?
> >
> > Why didn't they got installed the first time?
> >
> > Wow, now I wonder how many other packages that I
> > upgraded may have had a similar problem. May be
> that's
> > in part the reason there are so many packages
> failing
> > on loading shared libs.
=====
Eugenio Diaz, BSEE/BSCE
Linux Engineer
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
