RPM checks the dependancies against it's database of installed packages.
If you've updated your libs thru some other means the RPM will be unaware of
this and issue dependancy errors, even though you may actually have the
correct library loaded.
Also did you include the entry for any new libs in /etc/ld.so.conf and
rebuild?
Lastly, the rpm builder script in the RPM itself may be checking version
numbers and inserting them as dependancies.
-JMS
[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tri D. Hoang
Sent: Wednesday, March 28, 2001 9:03 AM
To: [EMAIL PROTECTED]
Subject: [expert] HELP! Mysterious RPM problem
Hi all,
I downloaded a bunch of RPMs from cooker and build a system from
scratch (i.e. manually install all the required packages). The new
system works fine.
>From there, I recompile some RPM packages using the SRPMs. However,
when I try to install these newly compiled packages, RPM complains
about dependencies such as glibc and such. Obviously I compiled the
package on the same box as the one I install them to. If I ignore
the complains with --nodeps then these packages will install and
work fine.
My question is: what could cause RPM to exhibit this kind of behavior?
I am using RPM 4.0.22. I begin installing the new system by using
rpm --initdb and then proceed to install filesytem, setup...
Any ideas?
Tri
[EMAIL PROTECTED]
