__register_frame_info, cont'd.



I think this is the trick:  Get SRPMs for the broken items, plus gtk+.
Rebuild and reinstall gtk+ and gtk+-devel, then have at the rest.
Hopefully gnome-libs is okay...

Hackers do this sometimes - they install bleeding-edge stuff (e.g. 
Starbuck) on their machines, create binaries with it, then give those
hinky binaries away to unsuspecting citizens.  RPM usually manages
this situation okay, but it misses it here, maybe because both
glibc-2.0.x and glibc-2.1.x contain an object called "libc.so.6" -
different from one version of glibc to the other, but RPM doesn't know
that.  Guess that's why the RPMS are described as "unsupported".  Even
so, it would be good for GNOME's credibility if they worked right.

--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
    ___
   /.  \    Gregory Fall                Phone: 734-913-4662
   \/  /    University of Michigan      Fax:   734-763-7130
     \ \    2455 Hayward Street         email: gmfall@engin.umich.edu
   __/_/    Ann Arbor, MI 48109                gmf@dweezil.dynip.com



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]