Hi List,
Well, I must need glasses. That worked great with 'sftp' and 'slynx',
when I went
to install mod_ssl-2.6.3-1mdk it began to install just fine and then
threw an 'execution of script failed' error at me and stalled. The
unsatisfied dependency with this mod I noticed was apache >=
1.3.12-12mdk (I have 1.3.12 running under windows) and I checked my
Linux version found I have 1.3.9-17mdk.
I am at apache web site now and also gftp'd into Mandrake again to look
but I only locate apache 1.3.9-17mdk, where can I find apache
1.3.12-12mdk?
Thanks,
b/web
Wade
Dan Jones wrote:
>
> I have had similar experiences, and think the problem has to do with the
> way that the RPMs (and the RPM database) specify dependencies. It
> appears to me that when an RPM is installed, an entry is made in the
> database of what files have been installed (e.g.
> "/usr/lib/libexample.so.1") When another RPM checks for dependencies,
> it checks that database (e.g. for "libexample.so.1".
>
> Alas, as far as the database is concerned, "/usr/lib/libexample.so.1" is
> *different* that "libexample.so.1".
>
> A similar problem can occur when one of your dependencies was installed
> from a tar file (or anything that isn't an RPM). In this case no entry
> at all occurs in the RPM database.
>
> IF you really have the necessary files/packages installed, just use
> --nodeps when you install using RPM.