Bugzilla – Bug 1040863
OpenSSL package split release number downgrade issue
Last modified: 2017-06-25 14:00:35 UTC
+++ This bug was initially created as a clone of Bug #1040862 +++ My docker build has broken because there is no x86-64 build of the latest libopenssl1. Installing python: Problem: python-2.7.13-2.2.x86_64 requires libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit), but this requirement cannot be provided uninstallable providers: libopenssl1_0_0-1.0.2k-1.2.x86_64[oss] Solution 1: downgrade of libopenssl1_0_0-1.0.2k-3.1.x86_64 to libopenssl1_0_0-1.0.2k-1.2.x86_64 Solution 2: do not install python-2.7.13-2.2.x86_64 Solution 3: break python-2.7.13-2.2.x86_64 by ignoring some of its dependencies See https://github.com/coala/docker-coala-base/issues/178 for Travis CI builds
use the downgrade option. we changed the packaging and the libopenssl1_0_0 got a lower release number (zypper dup would have done the right thing) this will resolve itself with the 1.0.2l update.
> use the downgrade option. The only install downgrade option I can find is `install --force`. Then I end up with Problem: php7-7.1.5-1.2.x86_64 requires libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit), but this requirement cannot be provided uninstallable providers: libopenssl1_0_0-1.0.2k-1.2.x86_64[oss] Solution 1: Following actions will be done: do not install php7-7.1.5-1.2.x86_64 do not install python-2.7.13-2.2.x86_64 Solution 2: downgrade of libopenssl1_0_0-1.0.2k-3.1.x86_64 to libopenssl1_0_0-1.0.2k-1.2.x86_64 Solution 3: break php7-7.1.5-1.2.x86_64 by ignoring some of its dependencies Is there another way to unbreak my Dockerfile? Or do I need to write an expect script to get this working? > (zypper dup would have done the right thing) I think dup doesnt help in this scenario. > this will resolve itself with the 1.0.2l update. Any estimate when that would be? And why upgrade to 1.0.2l? It doesnt contain anything useful for openSUSE..? https://www.openssl.org/news/cl102.txt
*** Bug 1040862 has been marked as a duplicate of this bug. ***
(In reply to Marcus Meissner from comment #1) > we changed the packaging and the libopenssl1_0_0 got a lower release number Adjust summary.
But the only approach is allowed 'zypper dup --no-allow-vendor-change' so I would say the downgrade is perfectly fine.
An updated OpenSSL 1.0.2l, which will fix this issue, was just submitted. (rq #498922)
Linky https://build.opensuse.org/request/show/498922
My problem with the docker has disappeared. It appears that all of the dependencies that I am adding are happy with the pre-installed versions of libopenssl, as that package isnt being installed any more, and libopenssl-devel-1_0_0-1.0.2k-2.2 installs happily. I guess some other change fixed this.
This is an autogenerated message for OBS integration: This bug (1040863) was mentioned in https://build.opensuse.org/request/show/505915 Factory / openssl-1_0_0
This is an autogenerated message for OBS integration: This bug (1040863) was mentioned in https://build.opensuse.org/request/show/505959 Factory / openssl-1_0_0
This is an autogenerated message for OBS integration: This bug (1040863) was mentioned in https://build.opensuse.org/request/show/506116 Factory / openssl-1_0_0