I just sponsored lvm2 2.03.16-3ubuntu1 which should fix the FTBFS. On including libdm-propagate-ioctl-errors-back-to-caller.patch: I am not sure this bug is important enough to grant that. The patch may apply cleanly to 2.03.16, but still it comes from 2.03.23, which is not a trivial change in the upstream codebase.
I can see that better error messages on ENOKEY will result in an overall better UX, however most commits in an upstream devel repo will somehow improve something, still we try to rely on releases as cut by upstream when possible, for the many reasons I certainly don't have to tell you about. :-) However: I may have missed the point here, and maybe the current UX is both (1) terrible, or at least quite bad (2) affecting many users, and not only users with an niche disk encryption configuration. If you think this is the case, can you please update the bug and elaborate a bit more on it? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
