Am 22.02.23 um 16:07 schrieb Johannes Meixner:
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.
Leap after GA does usually not see version updates of packages, let alone ABI changes. When it comes to the SLE base, that might in fact be forbidden by policy (but you know that better than I do). Why else would we still be on Python 3.6 or whatever old version that is currently? So even if things like ABI versions are not correctly tracked, there is no way to mess it up. That's different on Tumbleweed, where ABI changes are quite frequent, and happen in numerous places. Leap pre-GA, even after Beta, still "requires" dup to my knowledge, in the sense that it's recommended to use. Basically as long as Leap is open to submit requests and not locked down and limited to maintenance requests.
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.
Sure, I agree that the ABI dependency should be added. I was just arguing that it's not of the highest priority to maintainers, since the "workaround" is simply to do a complete update. Aaron