https://bugzilla.suse.com/show_bug.cgi?id=1221322 https://bugzilla.suse.com/show_bug.cgi?id=1221322#c15 --- Comment #15 from Michael Andres <ma@suse.com> --- (In reply to Stefan Hundhammer from comment #14)

But didn't we keep the package updates for the package/update stack closer together to avoid this kind of thing?

The ordering is solely based on dependencies and disrupted by cyclic dependencies. It's not always easy 'to keep things together'. The preferred strategy for CLASSIC_RPMTRANS would be to try to continue on an error rather than to abort immediately. With SINGLE_RPMTRANS this happens automatically, because the librpm transaction is not interruptible at all. It will try to do as much as possible. -- You are receiving this mail because: You are on the CC list for the bug.