public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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.0
Date: Tue, 19 May 2026 23:28:22 +0200	[thread overview]
Message-ID: <20260519212838.3147035-1-adolf.belka@ipfire.org> (raw)

- Update from version 6.19.1 to 7.0
- No change in rootfile
- Changelog
   * btrfstune: add ability to do offline conversion to the remap tree
     (experimental feature)
   * mkfs: add hole detection when precalculating size for --rootdir
   * fixes: recognize fs-verity tree items in various tools (check)
   * enable PCLMUL implementation on Musl (previously using SSE 4.2 at best)
   * help format changed to be in line with common packages like util-linux
   * reject writes to filesystem during check/btrfstune in case there's pending
     state of device replace or balance
   * other:
      * build ARM64 static binaries (attached to GH release) backward
         compatibility level is 'archv8-a'
      * CI updates
      * 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 f469afa3a..dfe01bace 100644
--- a/lfs/btrfs-progs
+++ b/lfs/btrfs-progs
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 6.19.1
+VER        = 7.0
 
 # 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 = 555bf1c0625afd30dae3cc38f293de195450133cea701096010cadde3d8be405681ed2c4b5e43db777df146e1d2d90697746bc9eea253211df216bd4456e04a1
+$(DL_FILE)_BLAKE2 = a0e8ef7a5bca5c4f4deb5487215a3543ae99759ffec191cd23b776d21621fb9aba173115a47ae34ebd0e6e38d720d430e5092151e938b0b65cff4aabffd9c607
 
 install : $(TARGET)
 
-- 
2.54.0



             reply	other threads:[~2026-05-19 21:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 21:28 Adolf Belka [this message]
2026-05-19 21:28 ` [PATCH] core203: Ship btrfs-progs Adolf Belka
2026-05-19 21:28 ` [PATCH] core203: Ship elfutils Adolf Belka
2026-05-19 21:28 ` [PATCH] core203: Ship gdb Adolf Belka
2026-05-19 21:28 ` [PATCH] core203: Ship libedit Adolf Belka
2026-05-19 21:28 ` [PATCH] core203: Ship libksba Adolf Belka
2026-05-19 21:28 ` [PATCH] core203: Ship libunistring Adolf Belka
2026-05-19 21:28 ` [PATCH] core203: Ship openvpn Adolf Belka
2026-05-19 21:28 ` [PATCH] elfutils: Update to version 0.195 Adolf Belka
2026-05-19 21:28 ` [PATCH] gdb: Update to version 17.2 Adolf Belka
2026-05-19 21:28 ` [PATCH] libedit: Update to version 20260512-3.1 Adolf Belka
2026-05-19 21:28 ` [PATCH] libksba: Update to version 1.8.0 Adolf Belka
2026-05-19 21:28 ` [PATCH] libunistring: Update to version 1.4.2 Adolf Belka
2026-05-19 21:28 ` [PATCH] openvpn: Update to version 2.7.4 Adolf Belka
2026-05-19 21:28 ` [PATCH] postfix: Update to version 3.11.3 Adolf Belka
2026-05-19 21:28 ` [PATCH] samba: Update to version 4.24.2 Adolf Belka
2026-05-19 21:28 ` [PATCH] xfsprogs: Update to version 7.0.0 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=20260519212838.3147035-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