
On 2/23/23 01:37, Johannes Meixner wrote:
Hello,
On 2023-02-22 11:50, Rainer Klier wrote (excerpt)
if, for example, there are new packages available for yast or systemd, i select in yast software manager all related packages to be updated.
and i don't want to update the whole tumbleweed system, only because for example yast2-fonts is released in a new version. that's the main reason for using that approach.
so i select everything, which is needed to be able to update, and i trust/rely that yast resolves all dependencies and auto-selects all those packages which are additional needed.
most of the time this approach works.
but sometimes (like this time, when ruby was updated/upgraded the dependency auto-select didn't also mark libstorage-ng-ruby and ruby-solv), that fails.
I am wondering why it seems on Tumbleweed "zypper dup" is told here to be the only right way to update something?
Shouldn't package management work same on Tumbleweed and openSUSE Leap and SLES and others so that the user can select an arbitrary package to be updated (when a package update is available) and then the package management would do "the right thing" to ensure that afterwards the system is again in an consistent state regarding package dependencies.
Technically every Tumbleweed update is the same as doing an Upgrade from Leap 15.3 to Leap 15.4 because here you are getting a new version of the distro where as a Leap update is just applying delta's from an update repo.
I think in this particular case here package management did "the right thing" so afterwards the system was again in an consistent state regarding package dependencies.
But because afterwards things did no longer work the root cause was likely inproperly defined package dependencies so it seems there is a bug of missing package dependencies.
Yep the main downside to doing things differently is eventually you'll find bugs that no one else has discovered yet, i'm sure there are a bunch of places where bugs like this exist that occasionally pop up when someone does partial updates or skips recommends. Yes we should fix them if we find them but we don't generally have a good way of finding them. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B