https://bugzilla.suse.com/show_bug.cgi?id=1228415 https://bugzilla.suse.com/show_bug.cgi?id=1228415#c7 --- Comment #7 from Michael Andres <ma@suse.com> --- @Anuj This kind of explains your issue, if you actually use just the update/leap/15.5/sle repo and not the complete set of 15.5 repos. The basic issue with both libraries (yaml and protobuf) is the fact that the dependencies of the installed version as well as the available updates claim to be compatible with the new libzypp's requirements. If you do a 'zypper up zypper' or 'zypper up libzypp' there is no need for the resolver to update these libraries as well, because the installed ones appear to be sufficient. The new libzypp used together with the old version of the libraries however fails at runtime. In fact the new versions - which were used to compile the new libzypp - are different and should have indicated this, so updating libzypp would have required updating them as well. A 'zypper up' or 'zypper dup' however updates all packages - zypp as well as yaml and protobuf. So this command usually does not lead to the issue. In your case - if you actually use just update/leap/15.5/sle repo - 'zypper dup' may not be able to update to the newest libraries. The matching libyaml for 15.5 e.g. is in the 15.5. Main Repository. If this repo is not available as well, you stay with the old version from 15.3 leading to the runtime error. In general it's not advisable to mix the repos of different distributions. One should either use the repository set for 15.3, 15.4 or the set for 15.5. (and one should never mix Leap and Tumbleweed repos). -- You are receiving this mail because: You are on the CC list for the bug.