Comment # 9 on bug 1045396 from Dominique Leuenberger

I see two valid ways out of it, one seemingly a bit 'hacky', the other one
introducing a cycle which we could only hope that zypp breaks it up at the
right point

Option 1 (a small hack):
have libcryptsetup4 conflict with device-mapper < 1.02.97

option 2:
have libdevmapper1_03 conflict with device-mapper < %{version}


Option 1 is obviously tailored at exactly this issue seen, there might be other
libs suffering from the same fallout at any point in time

Option 2: is already implemented, but zypp seems not to handle the installation
of the two pckages in a timely fashion to have the system is a broken state as
short as poossible (II'd expect the two to be updated alongside)

@zypp folkgs: did I miss something?


(moving off systemd's queue - systemd is only the poor messener that broke)