Bug 1161814 - Not work Yast and Zypper openSUSE Tumbleweed
Summary: Not work Yast and Zypper openSUSE Tumbleweed
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Security (show other bugs)
Version: Current
Hardware: x86-64 Other
: P2 - High : Major (vote)
Target Milestone: Current
Assignee: Vítězslav Čížek
QA Contact: E-mail List
URL:
Whiteboard:
Keywords: All_Languages
Depends on:
Blocks:
 
Reported: 2020-01-25 10:25 UTC by Yums Yums
Modified: 2020-03-30 07:28 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yums Yums 2020-01-25 10:25:01 UTC
openSUSE Tumbleweed

Not work Not work Yast(2) and Zypper after last update from Yast2 today (25/01/2020)!

>zypper up
zypper: symbol lookup error: /usr/lib64/libssh.so.4: undefined symbol: EVP_KDF_CTX_new_id, version OPENSSL_1_1_1d

yast

Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.
Caller:  /usr/lib64/ruby/vendor_ruby/2.6.0/yast/yast.rb:186:in `import_pure'
Details: component cannot import namespace 'Pkg'
Start the Ruby debugger now and debug the issue? (Experts only!)
Comment 1 Yums Yums 2020-01-25 10:30:34 UTC
Please help
Comment 2 Yums Yums 2020-01-25 10:41:11 UTC
$ git pull
/usr/lib/git/git-remote-https: symbol lookup error: /usr/lib64/libssh.so.4: undefined symbol: EVP_KDF_CTX_new_id, version OPENSSL_1_1_1d
Comment 3 Yums Yums 2020-01-25 12:08:21 UTC
Please help
Comment 4 Yums Yums 2020-01-25 12:33:27 UTC
NetworkNanager - not work
Comment 5 Vítězslav Čížek 2020-01-28 09:32:12 UTC
We replaced our KDF backport patch by the one from Fedora and the EVP_KDF_CTX_new_id symbol version has changed from 1.1.1d to 1.1.1b. We need to keep it at 1.1.1d for backward compatibility.

This should be fixed by https://build.opensuse.org/request/show/767785
Comment 6 Vítězslav Čížek 2020-01-28 09:44:11 UTC
The breaking change hasn't reached Factory yet. I guess you're using the security:tls repo. The problem is already fixed there.
Comment 7 Vítězslav Čížek 2020-03-30 07:28:36 UTC
This should be fixed.