thank you alaa for your reply but i don\t use mandrake i'm using centos so io have yum and doing yum gives the same error. and i also want to know how to it manually (for the sake of knowledge)
binary package management systems do not scan the file system for dependencies, they only know whats in the package database.
so this either means you installed the dependency manually from source code, or you mixed RPMs that are not specifically made for your distro or version or you're using badly packaged RPMs
I still don't understand why you don't let the package manager handle software installation and dependencies for you.
Alaa
"i`m feeling for the 2nd time like alice in wonderland reading el wafd"
News Feed
Blogs
Event Photos
Screen Shots
Polls
Popular Content
Search
Wall Papers
depends on your distro
but why the hell are you resolving dependencies manually, you should use your distros package management tools to do updates for you.
in mandrake its enough to run
to upgrade after you configure the proper package sources
also in mandrake you can query the uninstalled packages database to see which package provides any particular file.
here is the result on my installation
$ urpmf liblber libldap2:/usr/lib/liblber.so.2this means libldap2 contains the file you're looking for.
Alaa
"i`m feeling for the 2nd time like alice in wonderland reading el wafd"
thank you alaa for your reply
thank you alaa for your reply but i don\t use mandrake i'm using centos so io have yum and doing yum gives the same error. and i also want to know how to it manually (for the sake of knowledge)
the best things in life are free --- so as myself
If you are sure that the shar
If you are sure that the shared object is there, force no dependencies when installing the RPM via the "--nodeps" switch.
thanks for the tip it worked
thanks for the tip it worked :) but i wonder about why if it is thee the system can't see it
the best things in life are free --- so as myself
system knows what its told
binary package management systems do not scan the file system for dependencies, they only know whats in the package database.
so this either means you installed the dependency manually from source code, or you mixed RPMs that are not specifically made for your distro or version or you're using badly packaged RPMs
I still don't understand why you don't let the package manager handle software installation and dependencies for you.
Alaa
"i`m feeling for the 2nd time like alice in wonderland reading el wafd"
actually it is YUM that is ma
the best things in life are free --- so as myself
hrmf
Alaa
"i`m feeling for the 2nd time like alice in wonderland reading el wafd"