[KLUG Members] rpm wierdness

[Richard Zimmerman]

> I have run into this many times before - especially when stalling
> 'out-of-my-distribution' RPMs (i.e. install mandrake, suse or mirror-contrib
> rpm's on a redhat install, etc).  Don't quote me on this, but I think that
rpm
> refers to its database rather than the actual presence of the file(s) it
needs.
>  If for some reason it doesn't see an entry for libpq.so.2.0, it will think
> it's not installed.  Simply override the dependencies (the second try) with
> --nodeps once you have verified the file exists on your system.

   Ah, I see.... I had done the install with the --nodeps  option and it is
working fine now. I had also verified that the file did in fact exist. OK, it
was a symbolic link to a newer one <G>.

> The clean way to fix this in many cases is to get the .src.rpm and do a:
>  --rebuild

    I'll keep this in mind for the next time!

   Thanks for the insight.

   Richard