Problem Updating to openssl-0.9.6a-41.i386.rpm
hi... I've got a problem updating to openssl-0.9.6a-41.i386.rpm: pizza:/var/spool/autoupdate # rpm -Uhv openssl-0.9.6a-41.i386.rpm error: failed dependencies: libcrypto.so.0 is needed by lynx-2.8.3dev9-268 libcrypto.so.0 is needed by mod_php-3.0.17RC1-29 libcrypto.so.0 is needed by mod_ssl-2.8.1-0 libssl.so.0 is needed by lynx-2.8.3dev9-268 libssl.so.0 is needed by mod_php-3.0.17RC1-29 libssl.so.0 is needed by mod_ssl-2.8.1-0 (base: SuSE 7.1 pro on intel) A update with --nodeps will work (the libs are inside the package), but it should be corrected never the less - I don't like to use --nodeps or --force on my production systems. c'ya sven -- The Internet treats censorship as a routing problem, and routes around it. (John Gilmore on http://www.cygnus.com/~gnu/)
On Fri, 20 Jul 2001, Sven Koch wrote:
I've got a problem updating to openssl-0.9.6a-41.i386.rpm:
pizza:/var/spool/autoupdate # rpm -Uhv openssl-0.9.6a-41.i386.rpm error: failed dependencies: libcrypto.so.0 is needed by lynx-2.8.3dev9-268 libcrypto.so.0 is needed by mod_php-3.0.17RC1-29 libcrypto.so.0 is needed by mod_ssl-2.8.1-0 libssl.so.0 is needed by lynx-2.8.3dev9-268 libssl.so.0 is needed by mod_php-3.0.17RC1-29 libssl.so.0 is needed by mod_ssl-2.8.1-0
(base: SuSE 7.1 pro on intel)
replying to myself: SuSE 6.4 got the same problem if the update-package w3m_ssl-0.2.1-0 is installed. SuSE 6.3, 7.0 and 7.2 brought no errors. And one side-question: Is openssl-0.9.6a-12.alpha.rpm for SuSE 6.4 AXP now compiled with "no-asm"? Every openssl-using program just segfaults on my DEC Alpha XL300 with the normal suse-packages - got to compile it for myself (can't try the new package now as it would destroy my ssh connection to the box if not working) c'ya sven -- The Internet treats censorship as a routing problem, and routes around it. (John Gilmore on http://www.cygnus.com/~gnu/)
* Sven Koch wrote on Fri, Jul 20, 2001 at 15:44 +0200:
Is openssl-0.9.6a-12.alpha.rpm for SuSE 6.4 AXP now compiled with "no-asm"?
You could view the spec file from the source RPM. Usually it
should reflect the options. If you're really paraniod, use
"rpm --rebuild
participants (3)
-
Steffen Dettmer
-
Sven Koch
-
Sven Koch