linux/meta-openembedded.git/meta-oe/recipes-crypto/cryptsetup, branch master-next

cryptsetup: update udev package config

2026-05-12T08:07:02+00:00

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 Signed-off-by: Khem Raj

cryptsetup: upgrade 2.8.4 -> 2.8.6

2026-04-10T14:59:52+00:00

Signed-off-by: Wang Mingyu Signed-off-by: Khem Raj

cryptsetup: upgrade 2.8.3 -> 2.8.4

2026-02-03T03:54:39+00:00

Signed-off-by: Wang Mingyu Signed-off-by: Khem Raj

cryptsetup: upgrade 2.8.1 -> 2.8.3

2025-12-24T21:18:25+00:00

Signed-off-by: Wang Mingyu Signed-off-by: Khem Raj

cryptsetup: extend licenses with Apache-2.0

2025-10-20T20:18:29+00:00

The project's readme indicates that some parts of the code is covered by Apache license - add it to the RECIPE accordingly. Reported-by: Peter Kjellerstedt Signed-off-by: Gyorgy Sarvari Signed-off-by: Khem Raj

cryptsetup: Update the license field

2025-10-20T20:18:29+00:00

The below reference clearly states that GPL-2.0-with-OpenSSL-exception is to be used with GPL 2.0 or GPL3.0 and not as a standalone license. Therefore, update the correct license. Reference: https://github.com/aboutcode-org/scancode-licensedb/blob/569d72e13e7c8d14a44380f91e80c5a2d4091f8f/docs/openssl-exception-gpl-2.0.yml#L7 Signed-off-by: Sana Kazi Signed-off-by: Khem Raj

cryptsetup: upgrade 2.8.0 -> 2.8.1

2025-09-04T17:28:21+00:00

Signed-off-by: Wang Mingyu Signed-off-by: Khem Raj

cryptsetup: upgrade 2.7.5 -> 2.8.0

2025-07-07T17:00:53+00:00

Signed-off-by: Wang Mingyu Signed-off-by: Khem Raj

cryptsetup: demote udev runtime dependency to recommendation

2024-11-20T00:59:10+00:00

We use veritysetup in our custom initramfs to verify the rootfs before mounting it. We do not use udev or run systemd as PID1 in that initramfs. This RDEPENDS on udev and lvm2, and everything that udev ends up pulling in, thus bloats the initramfs by more than 10MiB. Removing udev from PACKAGECONFIG is not really an option, because we do want the udev integration in the real rootfs. Demote it to a recommendation so that the initramfs recipe can avoid udev and lvm2 using BAD_RECOMMENDATIONS or NO_RECOMMENDATIONS. Signed-off-by: Rasmus Villemoes Signed-off-by: Khem Raj

cryptsetup: fix udev PACKAGECONFIG

2024-10-10T19:53:50+00:00

This commit removed the lvm2-udevrules package. [https://git.openembedded.org/meta-openembedded/commit/?h=master-next&id=c37c867e1adddd6fa39cf3f3d4c6688ea6dc825a] Align accordingly to avoid error at do_rootfs Error: Problem 1: package udisks2-2.10.1-r0.corei7_64 from oe-repo requires libblockdev.so.3()(64bit), but none of the providers can be installed - package udisks2-2.10.1-r0.corei7_64 from oe-repo requires libbd_utils.so.3()(64bit), but none of the providers can be installed - package udisks2-2.10.1-r0.corei7_64 from oe-repo requires libblockdev >= 3.2.0, but none of the providers can be installed - package gvfs-1.56.0-r0.corei7_64 from oe-repo requires udisks2, but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires libcryptsetup.so.12()(64bit), but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires libcryptsetup.so.12(CRYPTSETUP_2.0)(64bit), but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires libcryptsetup.so.12(CRYPTSETUP_2.4)(64bit), but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires libcryptsetup.so.12(CRYPTSETUP_2.7)(64bit), but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires cryptsetup >= 2.7.5, but none of the providers can be installed - conflicting requests - nothing provides lvm2-udevrules needed by cryptsetup-2.7.5-r0.corei7_64 from oe-repo Problem 2: package gvfs-1.56.0-r0.corei7_64 from oe-repo requires udisks2, but none of the providers can be installed - package udisks2-2.10.1-r0.corei7_64 from oe-repo requires libblockdev.so.3()(64bit), but none of the providers can be installed - package udisks2-2.10.1-r0.corei7_64 from oe-repo requires libbd_utils.so.3()(64bit), but none of the providers can be installed - package udisks2-2.10.1-r0.corei7_64 from oe-repo requires libblockdev >= 3.2.0, but none of the providers can be installed - package gvfsd-trash-1.56.0-r0.corei7_64 from oe-repo requires libgvfscommon.so()(64bit), but none of the providers can be installed - package gvfsd-trash-1.56.0-r0.corei7_64 from oe-repo requires libgvfsdaemon.so()(64bit), but none of the providers can be installed - package gvfsd-trash-1.56.0-r0.corei7_64 from oe-repo requires gvfs >= 1.56.0, but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires libcryptsetup.so.12()(64bit), but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires libcryptsetup.so.12(CRYPTSETUP_2.0)(64bit), but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires libcryptsetup.so.12(CRYPTSETUP_2.4)(64bit), but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires libcryptsetup.so.12(CRYPTSETUP_2.7)(64bit), but none of the providers can be installed - package libblockdev-3.2.0-r0.corei7_64 from oe-repo requires cryptsetup >= 2.7.5, but none of the providers can be installed - conflicting requests - nothing provides lvm2-udevrules needed by cryptsetup-2.7.5-r0.corei7_64 from oe-repo (try to add '--skip-broken' to skip uninstallable packages) Signed-off-by: Markus Volk Signed-off-by: Khem Raj