On 8/16/25 12:59, srinuvasan.a via isar-users wrote:
> From: srinuvasan <srinuvasan.a@siemens.com>
>
> Custom kernel recipe builds were failing on Trixie due to a dependency
> on the unavailable libssl3 package. Updated to use the correct
> libssl3t64 package for Trixie builds.
>
> Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
> ---
>   meta/recipes-kernel/linux/linux-custom.inc | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
> index 01e9bff7..f55e2f29 100644
> --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -35,9 +35,10 @@ KERNEL_DEBIAN_DEPENDS ?= "initramfs-tools | linux-initramfs-tool, \
>                             kmod, \
>                             linux-base (>= 4.3~),"
>   
> -LIBSSL_DEP = "libssl3"
>   LIBSSL_DEP:buster = "libssl1.1"
>   LIBSSL_DEP:bullseye = "libssl1.1"
> +LIBSSL_DEP:bookworm = "libssl3"
> +LIBSSL_DEP = "libssl3t64"

 >   >   KERNEL_HEADERS_DEBIAN_DEPENDS ?= "libc6, \
>                                     ${LIBSSL_DEP},"


The kernel_headers should not have any dependency to libc6 or libssl*.
As the header package does not contain any binary which uses libssl3/libc6.

In Debian upstream libssl is used by the Kbuild package. After my
current analysis the binary dependency is missing in ISAR as the macro
${shlibs:Depends} does not add the dependency.

Quirin

--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/b9f497bc-68e9-4d09-9e1d-05d38399a716%40siemens.com.