From: Peter Marko <[email protected]> Commit 1ca8df16af411871e10f268064570146cdef54cb fixed a build problem in wrong way. Relevant rules from lvm2-udevrules were merged into libdevmapper (which was previously pulled by the rules package), however instead of that, the whole lvm2 package was added as dependency (which then pulls the needed libdevmapper). That is a huge package completely unneeded and due to that, this new dependency was later changed to recommendation.
Switch to libdevmapper instead of whole lvm2. Keep recommendation for now as it gives more flexibility. Signed-off-by: Peter Marko <[email protected]> --- meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.8.6.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.8.6.bb b/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.8.6.bb index c74b7a1f35..c754131e3f 100644 --- a/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.8.6.bb +++ b/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.8.6.bb @@ -57,7 +57,7 @@ PACKAGECONFIG[veritysetup] = "--enable-veritysetup,--disable-veritysetup" PACKAGECONFIG[luks2-reencryption] = "--enable-luks2-reencryption,--disable-luks2-reencryption" PACKAGECONFIG[integritysetup] = "--enable-integritysetup,--disable-integritysetup" PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux" -PACKAGECONFIG[udev] = "--enable-udev,--disable-udev,,,udev lvm2" +PACKAGECONFIG[udev] = "--enable-udev,--disable-udev,,,udev libdevmapper" PACKAGECONFIG[kernel_crypto] = "--enable-kernel_crypto,--disable-kernel_crypto" # gcrypt-pkbdf2 requries --with-crypto_backend=gcrypt or the flag isn't # recognized.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#126811): https://lists.openembedded.org/g/openembedded-devel/message/126811 Mute This Topic: https://lists.openembedded.org/mt/119193846/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
