On 28.09.21 12:44, Mathias Homann wrote:
Just as the actual culprit when my attempted rollback died was *not* tumbleweed-cli, it was basically because zypper installs every single rpm in a separate transaction - which dies horribly when you try to downgrade essential libraries like glibc.
What actually needs fixing is how zypper uses rpm.
Even with a single RPM transaction, downgrading a library that almost everything else depends upon will not work well. Think about %post scriptlets etc. Heck, I usually even upgrade rpm / libzypp stack separately from the rest of the system when doing Leap updates, just to avoid crazy "old bug in the package stack prevents update to work properly" scenarios. The only way I would attempt to do this is: * downgrade everything else * then downgrade glibc And you certainly know, that that's the way it should be done, you just did not look closely enough what that "rollback" command was going to do ;-) On a well maintained system, it would have just been "restore the backup and try again" ;-) Actually, your downgrade failure might be a bug, because zypper downgraded glibc while packages needing the newer version were still installed. The dependency solver should have prevented that IMHO. It should have installed the old glibc as one of the last packages. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman