https://bugzilla.suse.com/show_bug.cgi?id=1228659 https://bugzilla.suse.com/show_bug.cgi?id=1228659#c36 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com --- Comment #36 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Andrei Borzenkov from comment #35)

The problem is dependencies are computed once for the whole transaction. So, when transaction starts, all dependencies are correct. Now, in the middle of transaction zypper updates systemd from v255 to v256 and it immediately invalidates all computed dependencies involving other systemd subpackages.

Yes, if zypper computed dependencies *now* it probably would have noticed that existing systemd-boot v255 has missing dependency on systemd v255 and would first update systemd-boot to version v256. But it is too late. To implement it, zypper (or libzypp or libsolv) would effectively need to recompute dependencies after every package. I wonder what zypper maintainers think about it :)

If a lot of other packages rely on systemd functionality but not vice-versa, would it make sense to hardcode that systemd/udev packages get update before all others? -- You are receiving this mail because: You are on the CC list for the bug.