On Mon, 2023-02-20 at 17:33 +0100, Rainer Klier wrote:
Am 20.02.23 um 17:16 schrieb Dominique Leuenberger:
On Mon, 2023-02-20 at 17:11 +0100, Rainer Klier wrote:
or zypper trips over a case of a package that does not exist (as said, zypper dup would have cleaned that up) and does not continue the check.
To get your TW install somewhat in line, try at least:
zypper dup -r repo-oss (repo-oss being the alias defined on your TW main repo)
-r will instruct zypper to only take the TW repo into account and ignore all the rest. Some stuff might end up not updatable as 3rd party repos might block stuff.
cool, thanks.
this sounds the right option for me!
this should do the job for me.
but with all your tips i solved it.
thank you very much!
i thought, if all the yast packages are already updated to the latest available versions, maybe i missed one of the ruby packages.
and i tried
zypper up *ruby*
which resulted in
The following 14 packages are going to be upgraded: libruby3_1-3_1 libstorage-ng-ruby ruby-solv ruby3.1-rubygem-abstract_method ruby3.1-rubygem-cfa ruby3.1-rubygem-cheetah ruby3.1-rubygem-fast_gettext ruby3.1-rubygem-gem2rpm ruby3.1-rubygem-nokogiri ruby3.1-rubygem-ruby-augeas ruby3.1-rubygem-ruby-dbus ruby3.1-rubygem-simpleidn ruby3.1-rubygem- unf ruby3.1-rubygem-unf_ext
when updating yast and ruby before, i didn't update those, because i thought as they are ruby 3.1 packages only new rebuilt, i don't need them, and as the yast dependency check didn't automatically mark them for update, i thought they are not needed to be updated.
The relevant ones in this list are not the ruby3.1-*, but rather these two: * libstorage-ng-ruby * ruby-solv Depending on what you do on your machine, you can actually "zypper rm - u ruby3.1" (you likely don't need it anymore)