Hi,
I have the Publishing repo enabled,
http://download.opensuse.org/repositories/Publishing/openSUSE_Leap_15.2/
and since a few days I experience a weird package conflict. I have from Publishing
libzzip 0.13.71-lp152.2.3-x86_64
YaST2 wants to install, also from Publishing, version 0.13.72-lp152.2.1-x86_64
What I get is (I’m translating from the Spanish messages)
texlive-luatex-bin-2017.20170520.svn4449-lp152.15.2.x86_64 requires libzzip-0.so.13()(64bit), but this requirement cannot be met
suppressed providers: libzzip-0-13-0.13.71-lp152.2.3.x86_64
non-installable providers: libzzip-0-13-0.13.69-lp152.5.3.x86_64[repo-oss]
What YaST2 offers as “solution” is to uninstall 29 packages, basically all texlive-luatex and some other packages, which seems wrong. Any idea? Thanks!
When you post in English speaking forum, always run commands in English locale and copy-paste exact command invocation and full output enclosed in [noparse]
...
[/noparse] tags. Never describe what you have seen.
Or post in Spanish speaking forum.
texlive-luatex-bin-2017.20170520.svn4449-lp152.15.2.x86_64 requires libzzip-0.so.13()(64bit), but this requirement cannot be met
libzzip-0-13-0.13.72 does not provide this string; it provides
libzzip-0-13(x86-64)
libzzip.so.13()(64bit)
may be something changed in the way this software is packaged. Contact maintainers of this package.
non-installable providers: libzzip-0-13-0.13.69-lp152.5.3.x86_64[repo-oss]
this comes from different repository and zypper will not switch repository by default.
What YaST2 offers as “solution” is to uninstall 29 packages
And what magic did you expect? Installing new version of package replaces old version, but according to information for this new version it is not compatible with old version (it does not provide the same features as old version). If other packages require old version, choices are either to not update or to remove packages that require old version. And zypper suggests both solutions. Zypper cannot read your mind, it cannot decide for you. Zypper even suggests the third solution - ignore this dependency problem and update.
Anyway - this sounds like a bug in packaging of libzzip which you need to report to maintainers. Of course, at some point other packages depending on libzzip will be rebuilt against new version and so this issue disappears, but it still does not sound right.
Ok, thanks, I’ll try to contact the package maintainers through the corresponding OBS page.