| Summary: | >=sys-fs/udisks-2.7.4 pulls in cryptsetup unconditionally | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Erik Quaeghebeur <gentoo> |
| Component: | Current packages | Assignee: | Freedesktop bugs <freedesktop-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | kensington |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Starting with version 2.7.0, udisks really has a hard dependency (build and runtime) on the libblockdev crypto plugin, meaning libblockdev[cryptsetup]. I suppose we should remove the USE flag from udisks since the dependency on cryptsetup is now effectively unconditional. See https://github.com/storaged-project/udisks/pull/195/files for the upstream PR that introduced the hard dependency. (In reply to Alexandre Rostovtsev from comment #1) > Starting with version 2.7.0, udisks really has a hard dependency (build and > runtime) on the libblockdev crypto plugin, meaning libblockdev[cryptsetup]. Ok, thanks for the info. > I suppose we should remove the USE flag from udisks since the dependency on > cryptsetup is now effectively unconditional. I agree. This report can be closed then. fixed in 2.8.0 |
With a recent update, all of a sudden, cryptsetup and related packages were being pulled in. It seems this is due to the update to sys-fs/udisks-2.7.4, which contains the dependency >=sys-libs/libblockdev-2.14[cryptsetup,lvm?] Should this be >=sys-libs/libblockdev-2.14[cryptsetup?,lvm?] so with a conditional for cryptsetup as well?