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 1/2] btrfs-progs: Update to version 6.17
Date: Tue, 14 Oct 2025 15:07:53 +0200	[thread overview]
Message-ID: <20251014130807.3469514-1-adolf.belka@ipfire.org> (raw)

- Update from veresion 6.16 to 6.17
- No change to rootfile
- Changelog
    6.17
	   * inspect list-chunks: more sorting keys, descending order
	   * fi resize: add support for offline (unmounted) growing of single device
	   * device stats: add support for offline (unmounted) reads
	   * quota status: new command, overview what mode is enabled, tunables
	   * fi commit-stats: new command, print various commit stats from sysfs (since
	     kernel 6.1)
	   * balance start: print warning and delay start if there's a missing device
	     in the filesystem
	   * mkfs:
	      * print zoned mode (native, emulated)
	   * check:
	      * verify device bytes in super block item and in chunk tree
	   * other
	      * updated CI, new and updated tests
	      * cleanups, refactoring
	      * 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 652ae34ea..d5b4fa812 100644
--- a/lfs/btrfs-progs
+++ b/lfs/btrfs-progs
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 6.16
+VER        = 6.17
 
 # 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 = 375c60a93bc5b62d7c3a94d5ed108b81786b27f2beba27d85bcede94a892d84e71b1fe00a1574cc53066fe77bb37408b2b382db4a1664fefcc676c1c3efa1c60
+$(DL_FILE)_BLAKE2 = 301409e4f0e17c25620070bab0aedc1e57ad672bc7b4e4c1f9db2cd34c6104667800df2979ff456554c94e415be649dd7b8f43859d6539f84a1c050c2db27dd4
 
 install : $(TARGET)
 
-- 
2.51.0



             reply	other threads:[~2025-10-14 13:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 13:07 Adolf Belka [this message]
2025-10-14 13:07 ` [PATCH] fetchmail: Update to version 6.5.6 Adolf Belka
2025-10-14 13:07 ` [PATCH 1/2] hwdata: Update to version 0.400 Adolf Belka
2025-10-14 13:07 ` [PATCH 1/2] kbd: Update to version 2.9.0 Adolf Belka
2025-10-14 13:07 ` [PATCH 1/2] libgpg-error: Update to version 1.56 Adolf Belka
2025-10-14 13:07 ` [PATCH 1/2] openssh: Update to version 10.2p1 Adolf Belka
2025-10-14 13:07 ` [PATCH 1/2] p11-kit: Update to version 0.25.10 Adolf Belka
2025-10-14 13:08 ` [PATCH 1/2] vim: Update to version 9.1.1854 Adolf Belka
2025-10-14 13:08 ` [PATCH 2/2] core199: Ship btrfs-progs Adolf Belka
2025-10-14 13:08 ` [PATCH 2/2] core199: Ship hwdata Adolf Belka
2025-10-14 13:08 ` [PATCH 2/2] core199: Ship kbd Adolf Belka
2025-10-14 13:08 ` [PATCH 2/2] core199: Ship libgpg-error Adolf Belka
2025-10-14 13:08 ` [PATCH 2/2] core199: Ship openssh Adolf Belka
2025-10-14 13:08 ` [PATCH 2/2] core199: Ship p11-kit Adolf Belka
2025-10-14 13:08 ` [PATCH 2/2] core199: Ship vim 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=20251014130807.3469514-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