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 6.14
Date: Thu, 24 Apr 2025 15:43:44 +0200	[thread overview]
Message-ID: <20250424134354.3440212-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250424134354.3440212-1-adolf.belka@ipfire.org>

- Update from version 6.13 to 6.14
- Update of rootfile not required
- Changelog
    6.14
	   * mkfs:
	      * allow --sectorsize to be 2K for testing purposes of subpage mode (needs
	        the same block size supported by kernel)
	      * fix false error when no compression is requested and lzo is not
		compiled in
	   * convert: support 2K block size in the source filesystem
	   * defrag: new parameter -L/--level to specify compression levels (kernel 6.15),
	     also supports the realtime levels
	   * subvol delete: show names of recursively deleted child subvolumes
	   * qgroup show: use sysfs to detect up to date consistency status
	   * zoned mode: support zone capacity tracking
	   * other:
	      * CI new and updated workflows
	      * 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 82473dbef..cbeb179f3 100644
--- a/lfs/btrfs-progs
+++ b/lfs/btrfs-progs
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 6.13
+VER        = 6.14
 
 # 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 = aaf536e17977c052dd0828501f5a91b85403d561301f10d8c7bf2f5abae30a323f781ef8727f8ca48efc6edf16000b3ee8435fd6a89d6d047dda289ad87e3f64
+$(DL_FILE)_BLAKE2 = fae9bdbacc093ba260d7740001eef98f4ffb72c30631c789a34fbd5f34283cbdfb9f1e6b2f6112fb769b90892b47ea2bcc0bcdab37748b8d23e3588051620b2a
 
 install : $(TARGET)
 
-- 
2.49.0



  reply	other threads:[~2025-04-24 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 13:43 [PATCH] alsa: Update to version 1.2.14 Adolf Belka
2025-04-24 13:43 ` Adolf Belka [this message]
2025-04-24 13:43 ` [PATCH] coreutils: Update to version 9.7 Adolf Belka
2025-04-24 13:43 ` [PATCH] fontconfig: Update to version 2.16.2 Adolf Belka
2025-04-24 13:43 ` [PATCH] gzip: Update to version 1.14 Adolf Belka
2025-04-24 13:43 ` [PATCH] libcap: Update to version 2.76 Adolf Belka
2025-04-24 13:43 ` [PATCH] libffi: Update to version 3.4.8 Adolf Belka
2025-04-24 13:43 ` [PATCH] libgpg-error: Update to version 1.54 Adolf Belka
2025-04-24 13:43 ` [PATCH] nano: Update to version 8.4 Adolf Belka
2025-04-24 13:43 ` [PATCH] nfs: Update to version 2.8.3 Adolf Belka
2025-04-24 13:43 ` [PATCH] openssh: Update to version 10.0p1 Adolf Belka
2025-04-24 13:43 ` [PATCH] openssl: Update to version 3.5.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=20250424134354.3440212-2-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