dev-libs/libgcrypt-1.6.0 update changed soname of libgcrypt; this triggered a @preserved-libs event for sys-fs/cryptsetup. Please consider adding a slot operator on the dev-libs/libgcrypt atom in the next revbump of sys-fs/cryptsetup so that an update of dev-libs/libgcrypt will trigger a rebuild of sys-fs/cryptsetup when necessary. E.g. changing gcrypt? ( dev-libs/libgcrypt[static-libs(+)] ) to gcrypt? ( dev-libs/libgcrypt[static-libs(+)]:= ) in the ebuild. Thanks! Reproducible: Always
this has been fixed in cryptsetup-1.6.6