From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] xfsprogs: Update to version 5.16.0
Date: Wed, 11 May 2022 10:40:30 +0200 [thread overview]
Message-ID: <20220511084030.4045-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
- Update from 5.14.2 to 5.16.0
- Update of rootfile
- Changelog
5.16.0
This release is almost 100% a libxfs sync. I'm trying to catch up, and the
next release will be 5.18.0-rc0, with both 5.17 and 5.18 libxfs changes synced.
(there are very few).
At that point I'll finally start pulling in more functional changes.
xfsprogs-5.16.0 (04 May 2022)
- libxfs: remove kernel stubs from xfs_shared.h (Eric Sandeen)
- debian: Generate .gitcensus instead of .census (Bastian Germann))
xfsprogs-5.16.0-rc0 (28 Apr 2022)
- libxfs changes merged from kernel 5.16
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
config/rootfiles/common/xfsprogs | 7 +++++++
lfs/xfsprogs | 4 ++--
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/config/rootfiles/common/xfsprogs b/config/rootfiles/common/xfsprogs
index de76ca0db..fab8b67cb 100644
--- a/config/rootfiles/common/xfsprogs
+++ b/config/rootfiles/common/xfsprogs
@@ -103,3 +103,10 @@ usr/sbin/xfs_spaceman
#usr/share/man/man8/xfs_scrub.8
#usr/share/man/man8/xfs_scrub_all.8
#usr/share/man/man8/xfs_spaceman.8
+#usr/share/xfsprogs
+#usr/share/xfsprogs/mkfs
+#usr/share/xfsprogs/mkfs/dax_xxxMACHINExxx.conf
+#usr/share/xfsprogs/mkfs/lts_4.19.conf
+#usr/share/xfsprogs/mkfs/lts_5.10.conf
+#usr/share/xfsprogs/mkfs/lts_5.15.conf
+#usr/share/xfsprogs/mkfs/lts_5.4.conf
diff --git a/lfs/xfsprogs b/lfs/xfsprogs
index bbff6d701..fb2047800 100644
--- a/lfs/xfsprogs
+++ b/lfs/xfsprogs
@@ -24,7 +24,7 @@
include Config
-VER = 5.14.2
+VER = 5.16.0
THISAPP = xfsprogs-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 04083bf7952015d64f16e1aec0fa74be1957543e2264914f69defe45a3dc9f2524d941abc064a25a2fd760ebd6dcdcdc2404fd305e08fff7f6be6c5fc11d4d2f
+$(DL_FILE)_BLAKE2 = da328fe0c146a7b8ba866c5872f26ce95010939e05da51c73ed6374f00474605a81f4a822d65b60a132a4de47fff286e9f5f1ac809c1aa29420633f573b61aef
install : $(TARGET)
--
2.36.0
next reply other threads:[~2022-05-11 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 8:40 Adolf Belka [this message]
2022-05-30 19:16 ` Peter Müller
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=20220511084030.4045-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