Re: Failed dependencies

[Jeff Biss]

Lau,

Thanks for the quick reply.

1. For the files that are on my system but the RPM could not find:

    Yes they had the same name.
    - In some cases such as with rhn_register (identified when trying to rpm an update of up2date), it does exist but it must be the wrong version number because the failed dependencies error specifically identified a version number; I do not know how to retrieve the version numbers of the files.
    - In other cases such as with libreadline.so.4 (identified when trying to rpm python) it exists on my system. There is no version number or date provided.

2. I sort of understand the files dependencies thing and did run rpm --rebuilddb to attempt to get the system to "see" the files found missing but that are on my system. This did not seem to do much in my situation.

3. I have performed both types of installations: tar -zxvf filename.tar.gz and rpm -i filename.rpm but I am limiting this question specifically to using the supposedly simple rpm. I have searched for missing files using google and would get nothing in many instances, especially with what appeared to be library files (libxxx.xx.x).

4. I am now reading what I can find on Red Hat regarding RPM.

I can only assume that this is a bigger problem than I can see on the list. Why doesn't Red Hat have more information on solving RPM problems since this is the "simple" method offered as an alternative to Microsoft's Install programs?

Any other suggestions for avenues for finding missing system files that I can try?

Do most people just give up and go back to Windows OSes?

Thanks, Jeff Biss

Lau wrote:

Hi,

First, to check about something,

I have attempted to install some RPMs and had them fail with the failed 
dependencies error message. Some packages can be found on Red Hat such 
as Pythonxxx.rpm but there are files that cannot be found such as 
libxxx.xx.x. Sometimes the files are on my machine yet the RPM fails to 
find them even after I "fix" the manager database.

Are you sure the exactly version number is the same?
i.e. libfoobar.so.2 is different from libfoobar.so.1

1. Where do I find the missing files/programs? The RPM downloads did not 
list entire categories of RPMs such as System libraries.

Yes, it is really a very troublesome work for beginner.
But usually, where get a pkg, you will also find the dependency information on there.
For example, if you grab a licq.*.rpm from licq.org, you probably can find some other
information about licq's dependency pkg / files.
Another approache, (if the last one doesn't work), you can search the gooble 
with exactly the filename which make you in trouble. You usually got the neccessary
information there.

2. Where is the documentation that explicitly details the procedure for 
providing one's system with all requisite files/programs?

First, there is no rules to gover the completeness of files in a system. As different
pkgs will require differ files. E.g. if you install a Gnome2 desktop, you will need gtk2, 
pango, atk, gnome-desktop, etc. however, if you install KDE, you will need another
files.
Basically, if you are using RedHat, and installing all the software through "rpm -Uvh"
all the files dependency info in the system should be well maintained in the rpm 
database. 

3. How do I point the RPM to files on my system it claims are not there? 
(I have regenerated the database and this still happens)

Did you install something by manually compile and install it? (i.e. something ./configure
make, make install, etc procedure).

Anyway, a last option for this is rpm -Uvh --nodeps xxx.rpm
However, it is only useful if you know what you are doing.

Sure, you can also provide more detail information here, ask for advice.

Cheers,
Lau