From: Fiona Klute via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/fakeroot: bump to version 2.1.4
Date: Sun, 2 Aug 2026 21:53:15 +0200 [thread overview]
Message-ID: <ebcf9049-2f6d-459a-a542-aabcbf3fd055@gmx.de> (raw)
In-Reply-To: <8553c8ecd56b953f697e767deedfa7c7@free.fr>
Hi Julien!
Am 02.08.26 um 15:38 schrieb Julien Olivain:
> Hi Fiona,
>
> On 12/07/2026 17:17, Fiona Klute via buildroot wrote:
>> The source archive does not contain a pre-build configure script any
>> more, so enable autoreconf. Fakeroot also contains an experimental
>> Meson build definition since 2.1, but Buildroot should keep using
>> autotools until the Meson build is stable.
>>
>> Since v6.10.1 btrfs-progs uses nftw() [1], which package/fakeroot did
>> not support before v2.0 [2]. This update allows updating btrfs-progs
>> past v6.10 without breaking build of btrfs rootfs images.
>>
>> Upstream changes:
>> https://salsa.debian.org/clint/fakeroot/-/compare/
>> upstream%2F1.37.2...upstream%2F2.1.4
>>
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-
>> progs.git/commit?id=c6464d3f99ed1dabceff1168eabb207492c37624
>> [2] https://salsa.debian.org/clint/fakeroot/-/
>> commit/3502c515c73ee02e7f557e6a3bfc1af675dd3d34
>>
>> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
>> ---
>> Changes v1 -> v2:
>> * commit message: explicitly state why Buildroot should keep using
>> autotools for now
>> * add comment explaining why autoreconf is needed
>>
>> package/fakeroot/fakeroot.hash | 6 +++---
>> package/fakeroot/fakeroot.mk | 9 ++++++---
>> 2 files changed, 9 insertions(+), 6 deletions(-)
>>
>> diff --git a/package/fakeroot/fakeroot.hash b/package/fakeroot/
>> fakeroot.hash
>> index 82a6214380..0c330b7792 100644
>> --- a/package/fakeroot/fakeroot.hash
>> +++ b/package/fakeroot/fakeroot.hash
>> @@ -1,5 +1,5 @@
>> -# From https://deb.debian.org/debian/pool/main/f/fakeroot/
>> fakeroot_1.37.2-1.dsc
>> -sha1 1a721c2b4093a4e83dc091dc41a028f19340c1b3
>> fakeroot_1.37.2.orig.tar.gz
>> -sha256
>> 0eea60fbe89771b88fcf415c8f2f0a6ccfe9edebbcf3ba5dc0212718d98884db
>> fakeroot_1.37.2.orig.tar.gz
>> +# From https://snapshot.debian.org/archive/debian/20260711T202405Z/
>> pool/main/f/fakeroot/fakeroot_2.1.4-1.dsc
>> +sha1 9d55e62a34612316058166f7c528d9fc2f30c719
>> fakeroot_2.1.4.orig.tar.xz
>> +sha256
>> 0822bd5a9f0cf19d2ba0546b88b0432d4d3d9917db62c57b74044ccadba06e49
>> fakeroot_2.1.4.orig.tar.xz
>> # License files, locally calculated
>> sha256
>> fc82ca8b6fdb18d4e3e85cfd8ab58d1bcd3f1b29abe782895abd91d64763f8e7 COPYING
>> diff --git a/package/fakeroot/fakeroot.mk b/package/fakeroot/fakeroot.mk
>> index 12d7f1c4a1..8354f994ee 100644
>> --- a/package/fakeroot/fakeroot.mk
>> +++ b/package/fakeroot/fakeroot.mk
>> @@ -4,9 +4,9 @@
>> #
>>
>> ################################################################################
>>
>> -FAKEROOT_VERSION = 1.37.2
>> -FAKEROOT_SOURCE = fakeroot_$(FAKEROOT_VERSION).orig.tar.gz
>> -FAKEROOT_SITE = https://snapshot.debian.org/archive/
>> debian/20260401T000000Z/pool/main/f/fakeroot
>> +FAKEROOT_VERSION = 2.1.4
>
> While testing this new fakeroot version, I found an issue on hosts
> with SELinux enabled.
>
> For info, it is working well in the Buildroot Docker image,
> in the Gitlab infra:
> https://gitlab.com/jolivain/buildroot/-/jobs/15663849325
>
> When running on my Fedora 44 host (with selinux enabled),
> mkfs.btrfs is failing with this error:
>
> ERROR: zoned: unable to stat /buildroot/output_folder/TestBtrfs/images/
> rootfs.btrfs
> ERROR: getting a xattr value failed for /buildroot/output_folder/
> TestBtrfs/build/buildroot-fs/btrfs/target attr security.selinux: No data
> available
> ERROR: failed to add xattr item for the top level inode: Operation not
> permitted
> ERROR: unable to traverse directory /buildroot/output_folder/TestBtrfs/
> build/buildroot-fs/btrfs/target: -1
> ERROR: error while filling filesystem: Operation not permitted
>
> I was able to workaround the issue with the following patch I proposed in:
> https://salsa.debian.org/clint/fakeroot/-/merge_requests/38
>
> Could you check on your side this fakeroot patch is working for you?
Thanks for testing and writing a patch! Unfortunately it breaks building
a Buildroot system with selinux enabled on a non-selinux host, with
error messages similar to the ones you saw building on an selinux host:
ERROR: zoned: unable to stat
/home/fiona/development/buildroot/output/selinux/images/rootfs.btrfs
NOTE: default settings have changed in version 6.19 (supported since
linux 6.1):
- enable block-group-tree (-O bgt)
Rootdir from:
/home/fiona/development/buildroot/output/selinux/build/buildroot-fs/btrfs/target
Compress: no
ERROR: getting a xattr value failed for
/home/fiona/development/buildroot/output/selinux/build/buildroot-fs/btrfs/target
attr security.selinux: No data available
ERROR: failed to add xattr item for the top level inode: Operation not
permitted
ERROR: unable to traverse directory
/home/fiona/development/buildroot/output/selinux/build/buildroot-fs/btrfs/target:
-1
ERROR: error while filling filesystem: Operation not permitted
I assume the first line (zoned error) is a red herring, because it also
appears in a btrfs image build that works fine. Same build without your
patch produces:
ERROR: zoned: unable to stat
/home/fiona/development/buildroot/output/selinux/images/rootfs.btrfs
NOTE: default settings have changed in version 6.19 (supported since
linux 6.1):
- enable block-group-tree (-O bgt)
Rootdir from:
/home/fiona/development/buildroot/output/selinux/build/buildroot-fs/btrfs/target
Compress: no
Shrink: no
Label:
UUID: 12756174-b7d8-40af-a2a8-f27681f8108c
Node size: 16384
Sector size: 4096 (CPU page size: 4096)
Filesystem size: 512.00MiB
Block group profiles:
Data: single 200.00MiB
Metadata: DUP 32.00MiB
System: DUP 8.00MiB
SSD detected: no
Zoned device: no
Features: extref, skinny-metadata, no-holes, free-space-tree,
block-group-tree
Checksum: crc32c
Number of devices: 1
Devices:
ID SIZE PATH
1 512.00MiB
/home/fiona/development/buildroot/output/selinux/images/rootfs.btrfs
> If it does, could you send a v3 including my patch?
>
> There is also a new btrfs-progs v7.1:
> https://github.com/kdave/btrfs-progs/releases/tag/v7.1
> So while at it, maybe you could update to it to.
I have sent a v3 with that update.
Best regards,
Fiona
>> +FAKEROOT_SOURCE = fakeroot_$(FAKEROOT_VERSION).orig.tar.xz
>> +FAKEROOT_SITE = https://snapshot.debian.org/archive/
>> debian/20260711T202405Z/pool/main/f/fakeroot
>>
>> HOST_FAKEROOT_DEPENDENCIES = host-acl
>> # Force capabilities detection off
>> @@ -18,4 +18,7 @@ HOST_FAKEROOT_CONF_ENV = \
>> FAKEROOT_LICENSE = GPL-3.0+
>> FAKEROOT_LICENSE_FILES = COPYING
>>
>> +# source archive does not contain pre-generated configure script
>> +FAKEROOT_AUTORECONF = YES
>> +
>> $(eval $(host-autotools-package))
>> --
>> 2.53.0
>
> Best regards,
>
> Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-02 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 15:17 [Buildroot] [PATCH v2 1/2] package/fakeroot: bump to version 2.1.4 Fiona Klute via buildroot
2026-07-12 15:17 ` [Buildroot] [PATCH v2 2/2] package/btrfs-progs: bump to version 7.0 Fiona Klute via buildroot
2026-08-02 13:38 ` [Buildroot] [PATCH v2 1/2] package/fakeroot: bump to version 2.1.4 Julien Olivain via buildroot
2026-08-02 19:53 ` Fiona Klute via buildroot [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=ebcf9049-2f6d-459a-a542-aabcbf3fd055@gmx.de \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=ju.o@free.fr \
/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