zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Retrieving repository 'KDE:Frameworks5' metadata ...................................................................................[done]
Building repository 'KDE:Frameworks5' cache ........................................................................................[done]
Retrieving repository 'KDE:Extra' metadata .........................................................................................[done]
Building repository 'KDE:Extra' cache ..............................................................................................[done]
Retrieving repository 'packman' metadata ...........................................................................................[done]
Building repository 'packman' cache ................................................................................................[done]
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Problem: libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 conflicts with libopenssl-devel > 1.0.2m provided by libopenssl-devel-1.1.0g-1.1.noarch
Solution 1: deinstallation of libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64
Solution 2: deinstallation of libopenssl-devel-1.0.2m-1.1.noarch
Solution 3: keep obsolete libopenssl-devel-1.0.2m-1.1.noarch
Choose from above solutions by number or cancel [1/2/3/c] (c):
Bad/missing obsoletes field in rpm spec and/or unfinished rebuilds of rpms depending on those two packages. Safe option is to wait until packages are fixed and dependencies are in a consistent state. If you are feeling reckless, you can always rpm -e --nodeps the two offending packages and do a dup afterwards. Done this on my computers and have not noticed any bad side effects. This is no recommendation, though. If anything breaks, do not blame me.
BTW, you show zypper lr -P instead of what is always asked here:
zypper lr -d
Now there are no URLs in the list and that is what is the most important. All other identifications like Name and Alias can be whatever you like and thus different on every system. The URLs show where the repos are.
i had the same problem and chose to remove the libopenssl-1_0_0-devel-1.0.2m-1.1.x86_64 :
Thereafter zypper found more problems related to qt4 development package. I chose to answer every time to remove the development packages (qt4 devel and ssl1.0.0 devel) and ended with 18 packages that should be removed (all devel). Thereafter the Zypper dup ran without problem an no problems after reboot
To be true I have no idea which application required this devel-thing and therefore I have no idea what might break. I will wait some days and how things develop… :shame:
Hi
Nothing will change until the development package is removed, they cannot co-exist these days with the openssl update… any runtime stuff will be fine.
Not quite so simple. It turns out that there are other devel packages that depend on the libopenssl-1.0.0-devel and you will probably have to uninstall those too. I bumped into that with the qt4 devel package, and two or three others that depended on qt4. Not really a big problem, but not quite “simple” either.