From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org, Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH v3 2/2] package/btrfs-progs: bump to version 7.1
Date: Wed, 19 Aug 2026 13:43:08 +0200 [thread overview]
Message-ID: <aoWWo5NkaaGC3opC@windsurf> (raw)
In-Reply-To: <05fa60ef-a53f-4581-8845-0faa1b549919@gmx.de>
On Wed, Aug 19, 2026 at 01:35:42AM +0200, Fiona Klute wrote:
> Yes, that looks like the problem Julien described. He tried to patch it, the
> problem is that the patch breaks building a target with SELinux (at least on
> a non-SELinux host, haven't tested with):
> https://salsa.debian.org/clint/fakeroot/-/merge_requests/38
>
> I suspect the permission would have to faked by default on a non-SELinux
> host (and possibly inside fakeroot with SELinux), but I haven't had time to
> dig into it.
OK, thanks. On my side I don't care that much about btrfs support, but
obviously it would be nice to not have it broken in Buildroot :-)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-19 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 19:44 [Buildroot] [PATCH v3 1/2] package/fakeroot: bump to version 2.1.4 Fiona Klute via buildroot
2026-08-02 19:44 ` [Buildroot] [PATCH v3 2/2] package/btrfs-progs: bump to version 7.1 Fiona Klute via buildroot
2026-08-18 21:48 ` Thomas Petazzoni via buildroot
2026-08-18 23:35 ` Fiona Klute via buildroot
2026-08-19 11:43 ` Thomas Petazzoni via buildroot [this message]
2026-08-18 21:46 ` [Buildroot] [PATCH v3 1/2] package/fakeroot: bump to version 2.1.4 Thomas Petazzoni via buildroot
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=aoWWo5NkaaGC3opC@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.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