hi, Am 22.02.23 um 16:07 schrieb Johannes Meixner:
Hello,
On 2023-02-22 11:50, Rainer Klier wrote (excerpt)
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.
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.
this is exactly what i was talking about, and what i was expecting.
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.
this is exactly how it felt for me. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development