public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Badrikesh Prusty <badrikesh.prusty@siemens.com>,
	isar-users@googlegroups.com
Cc: cedric.hombourger@siemens.com, florian.bezdeka@siemens.com,
	felix.moessbauer@siemens.com
Subject: Re: [PATCH v2] linux-kselftest: switch to libfuse3-dev for Debian forky and newer
Date: Fri, 6 Nov 2026 17:08:33 +0100	[thread overview]
Message-ID: <0015a6fe-43eb-409b-a72a-f6ff471b7624@ilbers.de> (raw)
In-Reply-To: <20261029042632.306009-1-badrikesh.prusty@siemens.com>

Applied to next, thanks.

Zhihang

On 10/29/26 05:26, 'Badrikesh Prusty' via isar-users wrote:
> In Debian forky, fuse 2 has been deprecated/removed, and packages build
> against libfuse3-dev instead of libfuse-dev.
>
> Default to `libfuse3-dev` for forky and future Debian releases, while
> retaining `libfuse-dev` for older supported Debian releases (buster,
> bullseye, bookworm, trixie) to prevent dependency resolution failures.
>
> Suggested-by: Cedric Hombourger <cedric.hombourger@siemens.com>
> Signed-off-by: Badrikesh Prusty <badrikesh.prusty@siemens.com>
> ---
>   meta/classes-recipe/linux-kselftest.bbclass | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes-recipe/linux-kselftest.bbclass b/meta/classes-recipe/linux-kselftest.bbclass
> index f8d8c170..322ec6f6 100644
> --- a/meta/classes-recipe/linux-kselftest.bbclass
> +++ b/meta/classes-recipe/linux-kselftest.bbclass
> @@ -20,7 +20,7 @@ DEBIAN_BUILD_DEPENDS ?= " \
>       libpopt-dev, \
>       libcap-dev, \
>       libmount-dev, \
> -    libfuse-dev, \
> +    ${@ 'libfuse-dev' if d.getVar('BASE_DISTRO_CODENAME') in ['buster', 'bullseye', 'bookworm', 'trixie'] else 'libfuse3-dev'}, \
>       libmnl-dev, \
>       pkg-config, \
>       clang:native, \

-- 
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/0015a6fe-43eb-409b-a72a-f6ff471b7624%40ilbers.de.

      reply	other threads:[~2026-11-06 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  4:26 'Badrikesh Prusty' via isar-users
2026-11-06 16:08 ` Zhihang Wei [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0015a6fe-43eb-409b-a72a-f6ff471b7624@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=badrikesh.prusty@siemens.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox