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 6.16
Date: Tue, 26 Aug 2025 20:48:42 +0200 [thread overview]
Message-ID: <20250826184904.6229-1-adolf.belka@ipfire.org> (raw)
- Update from version 6.15 to 6.16
- Update of rootfile not required
- Changelog
6.16
* mkfs:
* print label of existing filesystem if attempting to overwrite
* remove note about changed defaults in 6.15
* discard support detection uses the ioctl and not sysfs, this should
work for all types of block devices
* device usage: fix printing units of partition sizes, used to be in 512B
sectors
* defrag: new option --nocomp to request no compression (kernel 6.17)
* check: detect missing orphan items for deleted subvolumes
* subvol delete: don't print warning if filesystem is mounted with
user_subvol_rm_allowed
* build: add build support for Android
* other:
* cleanups and refactoring
* sync sources with kernel
* documentation updates
* CI and test 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 952a59909..652ae34ea 100644
--- a/lfs/btrfs-progs
+++ b/lfs/btrfs-progs
@@ -24,7 +24,7 @@
include Config
-VER = 6.15
+VER = 6.16
# 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 = 5e79b7606fb236bc21e5b2401f5d6b27ad0ffb1b8ceef3ed9c7042b384508b1e1cc2a3a451d94e5369fa1592d91da78264caabe74bf1d907ac8e513a86b6fed8
+$(DL_FILE)_BLAKE2 = 375c60a93bc5b62d7c3a94d5ed108b81786b27f2beba27d85bcede94a892d84e71b1fe00a1574cc53066fe77bb37408b2b382db4a1664fefcc676c1c3efa1c60
install : $(TARGET)
--
2.51.0
next reply other threads:[~2025-08-26 18:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 18:48 Adolf Belka [this message]
2025-08-26 18:48 ` [PATCH] core198: Ship btrfs-progs Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship gdbm Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship harfbuzz Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship hwdata Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship libinih Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship lsof Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship nano Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship sudo Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship whois Adolf Belka
2025-08-26 18:48 ` [PATCH] fping: Update to version 5.4 Adolf Belka
2025-08-26 18:48 ` [PATCH] gdbm: Update to version 1.26 Adolf Belka
2025-08-26 18:48 ` [PATCH] git: Update to version 2.51.0 Adolf Belka
2025-08-26 18:48 ` [PATCH] harfbuzz: Update to version 11.4.3 Adolf Belka
2025-08-26 18:48 ` [PATCH] hwdata: Update to version 0.398 Adolf Belka
2025-08-26 18:48 ` [PATCH] libinih: Update to version 61 Adolf Belka
2025-08-26 18:48 ` [PATCH] lsof: Update to version 4.99.5 Adolf Belka
2025-08-26 18:48 ` [PATCH] nano: Update to version 8.6 Adolf Belka
2025-08-26 18:49 ` [PATCH] postfix: Update to version 3.10.4 Adolf Belka
2025-08-26 18:49 ` [PATCH] rpcbind: Update to version 1.2.8 Adolf Belka
2025-08-26 18:49 ` [PATCH] sudo: Update to version 1.9.17p2 Adolf Belka
2025-08-26 18:49 ` [PATCH] whois: Update to version 5.6.4 Adolf Belka
2025-08-26 18:49 ` [PATCH] wsdd: Update to version 0.9 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=20250826184904.6229-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