From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] btrfs-progs: Update to version 7.1
Date: Fri, 24 Jul 2026 19:43:52 +0200 [thread overview]
Message-ID: <20260724174412.3827472-1-adolf.belka@ipfire.org> (raw)
- Update from version 7.0 to 7.1
- No change to the rootfile
- Changelog
7.1
* mkfs:
* use GET_CSUMS ioctl (if provided by kernel, 7.2) to reuse existing
checksums for --rootdir, works with --reflink to avoid reading file data
* fix last block handling for reflink
* fix handling of incompressible data extents
* fix --rootdir size estimation when using hardlinks
* fi mkswapfile: add option to specify page size, useful on ARM64
* check: add option to skip qgroup verification to speed up check
* in experimental build, use V2 of tree search ioctl, this can use larger
buffer
* preliminary fscrypt support
* enhance filesystem opening modes with more fine-grained support of
partially damaged trees and allow to skip non-essential trees
* other:
* stability and error handling fixes
* CI updates
* updated tests
* documentation updates
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/btrfs-progs | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/btrfs-progs b/lfs/btrfs-progs
index dfe01bace..b2b87287d 100644
--- a/lfs/btrfs-progs
+++ b/lfs/btrfs-progs
@@ -24,7 +24,7 @@
include Config
-VER = 7.0
+VER = 7.1
# https://mirrors.edge.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = a0e8ef7a5bca5c4f4deb5487215a3543ae99759ffec191cd23b776d21621fb9aba173115a47ae34ebd0e6e38d720d430e5092151e938b0b65cff4aabffd9c607
+$(DL_FILE)_BLAKE2 = b72e5a027261953fba7915a1f5242a1804c6d4335c4261391a938e1aca6314c193051a52a8c6e315cd8714fe7763a0b20564c67fc654492e4df6ac42daff04a4
install : $(TARGET)
--
2.55.0
next reply other threads:[~2026-07-24 17:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 17:43 Adolf Belka [this message]
2026-07-24 17:43 ` [PATCH] core205: Ship btrfs-progs Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship cmake Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship findutils Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship fontconfig Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship gawk Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship libffi Adolf Belka
2026-07-24 17:44 ` [PATCH] core205: Ship libtool Adolf Belka
2026-07-24 17:44 ` [PATCH] core205: Ship meson Adolf Belka
2026-07-24 17:44 ` [PATCH] core205: Ship p11-kit Adolf Belka
2026-07-24 17:44 ` [PATCH] core205: Ship xorriso Adolf Belka
2026-07-24 17:44 ` [PATCH] findutils: Update to version 4.11.0 Adolf Belka
2026-07-24 17:44 ` [PATCH] fontconfig: Update to version 2.18.2 Adolf Belka
2026-07-24 17:44 ` [PATCH] gawk: Update to ver5sion 5.4.1 Adolf Belka
2026-07-24 17:44 ` [PATCH] libffi: Update to version 3.7.1 Adolf Belka
2026-07-24 17:44 ` [PATCH] libtool: Update to version 2.6.2 Adolf Belka
2026-07-24 17:44 ` [PATCH] meson: Update to version 1.11.2 Adolf Belka
2026-07-24 17:44 ` [PATCH] p11-kit: Update to version 0.26.4 Adolf Belka
2026-07-24 17:44 ` [PATCH] taglib: Update to version 2.3.1 Adolf Belka
2026-07-24 17:44 ` [PATCH] xorriso: Update to version 1.5.8.pl02 Adolf Belka
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=20260724174412.3827472-1-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/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