Am 20.02.23 um 18:04 schrieb Rainer Klier:
so, for example, if in the tumbleweed snapshot email is written, that "GraphicsMagick" ist updated, i enter "magick" in the search-text-box of yast, or when systemd is mentioned in the tumbleweed snapshot email, i enter "systemd" and "udev" in the search-text-box of yast.
then i select all packages and yast autoselects all dependent packages.
this then usually resolves in a list of all packages which i need/want to update.
for some unknown reason, this time the packages "libstorage-ng-ruby" and "ruby-solv" where not auto-selected, which i don't understand.
Let's take ruby-solv: this contains /usr/lib64/ruby/vendor_ruby/3.2.0/x86_64-linux-gnu/solv.so, so it's tied to a specific Ruby version. We could probably add something like Provides: ruby-solv(ruby%{rb_ver}) and then add this as requirement to yast2-packager. In fact we already have requirements there like rubygem(%{rb_default_ruby_abi}:nokogiri), where %{rb_default_ruby_abi} = ruby:3.2.0. But finding and modelling all dependencies is difficult (not all dependencies are as obvious as this), and it's even more difficult to properly test that. (For a start, there might be a lot of combinations when considering partial updates.) Then there is little benefit in making partial updates work, since Tumbleweed will usually not ship new package versions unless it needs to, so you might understand why not many package maintainers want to invest a lot of effort into that. Aaron