Re: rpmlib error

["Kenneth Porter" <shiva well com>]

On Fri, 22 Sep 2000 17:07:01 -0400, Stan Bubrouski wrote:

>> Well, I try to upgrade to rpm 3.0-6.0 and I get the error:
>> librpm.so.0 is needed by grpmi-7.1-9mdk
>
>The error message speaks for itself.  To upgrade rpm you will need to upgrade
>all the packages that depend on the old rpmlib as well in order not to break
>your system.  That's all.

I just ran into the same problem trying to upgrade procps from Rawhide:
The rusers-server package was linked against libproc.so.2.0.0, and the
new procps provides libproc.so.2.0.7. Now I see in /lib a lot of
libraries that have multiple instances (via symlinks) with different
version "levels" (eg. a base libxxx.so, then libxxx.so.1, then
libxxx.so.1.2, etc.). Where do those extra symlinks come from, and
which one should a given client link to? Shouldn't rusers-server bind
to a libproc.so.2, for example? Who's responsible for creating that
link?

(Reference bugzilla bug ID's 17786 and 17787.)

To upgrade procps and retain rusers-server, I had to uninstall
rusers-server, upgrade procps, and build a new rusers-server against
the new library. This tight coupling between packages looks like a Bad
Thing to me.

Ken
mailto:shiva@well.com
http://www.sewingwitch.com/ken/
http://www.harrybrowne2000.org/