The current rawhide updates include openssh-3.9p1-12 which requires, provided, openssl-0.9.7e. The catch is that this makes 'libssl.so.5' and 'libcrypt.so.5' while most anything on a system which refers to these libraries, and that is a lot, want to see 'libssl.so.4' and 'libcrypt.so.4'. So we have new packages 'openssl097a' which supply these. Rejoice.
The catch is that yum is not picking up these packages at all and does not seem to notice the above. I tried different things and no dice. Eventually I ended up with something like
yum -c local.conf install openssl097a openssl-0.9.7e
With -d5 that produced the following:
Reading Local RPMDB No other openssl097a installed, adding to list for potential install reduced installs : openssl097a.x86_64 0:0.9.7a-1 potential updates : openssl.x86_64 0:0.9.7e-2 Setting up Repos Reading repository metadata in from local files Setting up Package Sacks Building updates object Resolving Dependencies 1109719670.63 --> Populating transaction set with selected packages. Please wait. Member: openssl097a.x86_64 0-0.9.7a-1 - u Adding Package openssl097a - 0.9.7a-1.x86_64 in mode u ---> Package openssl097a.x86_64 0:0.9.7a-1 set to be updated Member: openssl.x86_64 0-0.9.7e-2 - u Adding Package openssl - 0.9.7e-2.x86_64 in mode u ---> Package openssl.x86_64 0:0.9.7e-2 set to be updated --> Running transaction check # of Deps = 1
Dep Number: 1/1 --> Processing Conflict: openssl097a conflicts openssl <= 0.9.7a openssl097a conflicts: openssl <= 0.9.7a miss = 0 conf = 1 CheckDeps = 0 --> Finished Dependency Resolution Dependency Process ending Error: openssl097a conflicts with openssl <= 0.9.7a
And that was it. So what is an "official" way to get out of that maze? I eventually gave up and did 'rpm -Uvh --nodeps ...' on these packages which allowed me to follow with the rest. Bugs in package dependencies or in yum? Or just the way that it is ...?
There is another catch. 'kdelibs', the latest one and obviously also everytning, wants explicitly 'openssl = 0.9.7a' instead of "*.so.4" and is not going to be satisfied with openssl097a. But that is yet another story.
Michal
On Tue, 1 Mar 2005 17:00:59 -0700, Michal Jaegermann michal@harddata.com wrote:
The current rawhide updates include openssh-3.9p1-12 which requires, provided, openssl-0.9.7e. The catch is that this makes 'libssl.so.5' and 'libcrypt.so.5' while most anything on a system which refers to these libraries, and that is a lot, want to see 'libssl.so.4' and 'libcrypt.so.4'. So we have new packages 'openssl097a' which supply these. Rejoice.
there is a problem with the new openssl097a package. it doesnt actually provide openssl = 0.9.7a as required by things like current kdelibs in rawhide... at least its a problem until everything in rawhide is rebuilt to require the new openssl.
rpm -q --provides -p openssl097a-0.9.7a-1.i386.rpm libcrypto.so.4 libssl.so.4 openssl097a = 0.9.7a-1
rpm -q --provides -p openssl-0.9.7e-2.i386.rpm config(openssl) = 0.9.7e-2 libcrypto.so.5 libssl.so.5 openssl = 0.9.7e-2
rpm -q --provides openssl-0.9.7a-46 as installed on my rawhide system right now config(openssl) = 0.9.7a-46 libcrypto.so.4 libssl.so.4 openssl = 0.9.7a-46
rpm -q --requires -p kdelibs-3.4.0-0.rc1.2.i386.rpm <snip> openssl = 0.9.7a <snip> libcrypto.so.5
rpm -q --requires kdelibs on my rawhide system right now. openssl = 0.9.7a libcrypto.so.4
whether this is a packaging bug or whether this is just a symptom of an inconsistent rawhide tree is an open question. But certaintly right now up2date, nor yum, nor rpm cli can resolve the issue.. simply because nothing in the rawhide tree at the moment actually provides openssl = 0.9.7a-X .
It also doesnt help that kdelibs-3.4.0-0.rc1.2.i386.rpm in rawhide at the moment requires libcrypto.so.5... basically meaning that right now kdelibs in rawhide requires openssl-0.9.7e and requires openssl-0.9.7a simultaneously.
Not sure how to file this.. this is rather amusing. Someone certaintly needs to file something as a bug report.
-jef"rawhide just ate about 20 or so babies... and is now purring contently with a full belly"spaleta
On Tue, Mar 01, 2005 at 08:35:40PM -0500, Jeff Spaleta wrote:
Not sure how to file this.. this is rather amusing. Someone certaintly needs to file something as a bug report.
Well, I filed against kdelibs
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150060
for a start. Does not necessarily means that it needs to be resolved that way but one has to begin somewhere. :-)
Michal
On Tue, 1 Mar 2005 20:35:40 -0500, Jeff Spaleta wrote:
On Tue, 1 Mar 2005 17:00:59 -0700, Michal Jaegermann michal@harddata.com wrote:
The current rawhide updates include openssh-3.9p1-12 which requires, provided, openssl-0.9.7e. The catch is that this makes 'libssl.so.5' and 'libcrypt.so.5' while most anything on a system which refers to these libraries, and that is a lot, want to see 'libssl.so.4' and 'libcrypt.so.4'. So we have new packages 'openssl097a' which supply these. Rejoice.
there is a problem with the new openssl097a package. it doesnt actually provide openssl = 0.9.7a as required by things like current kdelibs in rawhide... at least its a problem until everything in rawhide is rebuilt to require the new openssl.
rpm -q --provides -p openssl097a-0.9.7a-1.i386.rpm libcrypto.so.4 libssl.so.4 openssl097a = 0.9.7a-1
rpm -q --provides -p openssl-0.9.7e-2.i386.rpm config(openssl) = 0.9.7e-2 libcrypto.so.5 libssl.so.5 openssl = 0.9.7e-2
The usual "%name = %version-%release" Provides is automatic for a package. When you rename the package, it changes, too.
You cannot add an explicit "Provides: openssl = 0.9.7a" to the openssl097a package, because recent behaviour in RPM would remove such a package with the next update of the openssl package.
On Wed, 2 Mar 2005 07:47:46 +0100, Michael Schwendt fedora@wir-sind-cool.org wrote:
You cannot add an explicit "Provides: openssl = 0.9.7a" to the openssl097a package, because recent behaviour in RPM would remove such a package with the next update of the openssl package.
I realize now, after more investigation. I had some strange idea in my head that 'sane' packages might actually require openssl = 0.9.7a. In fact its only kdelibs that requires it and its an explicit requires. the bug here is limited to kdelibs package which needs its explicit openssl requires statement bumped up to openssl = 0.9.7e.
-jef
I just did a miminal fc3 install and trying to yum update to rawhide (i have done it like 10x) and i'm getting the openssl problem
--> Finished Dependency Resolution Error: Missing Dependency: libssl.so.4 is needed by package stunnel Error: Missing Dependency: libcrypto.so.4 is needed by package pam_ccreds Error: Missing Dependency: libcrypto.so.4 is needed by package stunnel Error: Missing Dependency: libcrypto.so.4 is needed by package wget Error: Missing Dependency: libcrypto.so.4 is needed by package xmlsec1-openssl Error: Missing Dependency: libcrypto.so.4 is needed by package lftp Error: Missing Dependency: libssl.so.4 is needed by package libwvstreams Error: Missing Dependency: libssl.so.4 is needed by package pyOpenSSL Error: Missing Dependency: libcrypto.so.4 is needed by package python Error: Missing Dependency: libcrypto.so.4 is needed by package ipsec-tools Error: Missing Dependency: libssl.so.4 is needed by package python Error: Missing Dependency: libcrypto.so.4 is needed by package pyOpenSSL Error: Missing Dependency: libssl.so.4 is needed by package wget Error: Missing Dependency: libssl.so.4 is needed by package xmlsec1-openssl Error: Missing Dependency: libcrypto.so.4 is needed by package dhcpv6_client Error: Missing Dependency: libcrypto.so.4 is needed by package libwvstreams Error: Missing Dependency: libssl.so.4 is needed by package lftp
On Wed, 2 Mar 2005 09:19:46 -0500, Jeff Spaleta jspaleta@gmail.com wrote:
On Wed, 2 Mar 2005 07:47:46 +0100, Michael Schwendt fedora@wir-sind-cool.org wrote:
You cannot add an explicit "Provides: openssl = 0.9.7a" to the openssl097a package, because recent behaviour in RPM would remove such a package with the next update of the openssl package.
I realize now, after more investigation. I had some strange idea in my head that 'sane' packages might actually require openssl = 0.9.7a. In fact its only kdelibs that requires it and its an explicit requires. the bug here is limited to kdelibs package which needs its explicit openssl requires statement bumped up to openssl = 0.9.7e.
-jef
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
-
Jef Spaleta -
Justin Conover -
Michael Schwendt -
Michal Jaegermann