public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Badrikesh Prusty' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-kselftest: use libfuse3-dev for Debian forky
Date: Wed, 28 Oct 2026 21:36:18 -0700 (PDT)	[thread overview]
Message-ID: <afbe6275-2c32-439d-9202-c6a8ae91b37fn@googlegroups.com> (raw)
In-Reply-To: <6855448400c0df2be2328c44d7919e7cb45be9fd.camel@siemens.com>


[-- Attachment #1.1: Type: text/plain, Size: 2464 bytes --]

Hi,

Thanks for the feedback. Addressed in v2 by inverting the check to list 
older Debian releases instead:
https://groups.google.com/g/isar-users/c/ZmYTolXaO4A


Many thanks,
Badrikesh


On Wednesday, October 21, 2026 at 7:07:31 PM UTC+5:30 Florian Bezdeka wrote:

> Hi Badrikesh,
>
> On Wed, 2026-10-21 at 06:36 -0400, 'Badrikesh Prusty' via isar-users
> wrote:
> > In Debian forky, fuse 2 has been deprecated, and packages build against
> > libfuse3-dev instead of libfuse-dev.
> > 
> > Conditionally depend on `libfuse3-dev` when `BASE_DISTRO_CODENAME` is
> > `forky`, while retaining `libfuse-dev` for older Debian releases to
> > avoid build dependency resolution failures.
> > 
> > Suggested-by: Cedric Hombourger <cedric.h...@siemens.com>
> > Signed-off-by: Badrikesh Prusty <badrikes...@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..d875e33a 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, \
> > + ${@ 'libfuse3-dev' if d.getVar('BASE_DISTRO_CODENAME') in ['forky'] 
> else 'libfuse-dev'}, \
>
> I think that this approach will not scale. We have to touch that for
> each new Debian release.
> Listing the old (= still supported) Debian releases seems easier. No?
>
> > libmnl-dev, \
> > pkg-config, \
> > clang:native, \
> > -- 
> > 2.39.5
> > 
> > -- 
> > 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+...@googlegroups.com.
> > To view this discussion visit 
> https://groups.google.com/d/msgid/isar-users/20261021103638.156904-1-badrikesh.prusty%40siemens.com
> .
>

-- 
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/afbe6275-2c32-439d-9202-c6a8ae91b37fn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3821 bytes --]

      reply	other threads:[~2026-10-29  4:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 10:36 'Badrikesh Prusty' via isar-users
2026-10-21 10:46 ` 'MOESSBAUER, Felix' via isar-users
2026-10-21 13:37 ` 'Florian Bezdeka' via isar-users
2026-10-29  4:36   ` 'Badrikesh Prusty' via isar-users [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=afbe6275-2c32-439d-9202-c6a8ae91b37fn@googlegroups.com \
    --to=isar-users@googlegroups.com \
    --cc=badrikesh.prusty@siemens.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