From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] kmod: Update to version 34.1
Date: Tue, 18 Mar 2025 22:20:12 +0100 [thread overview]
Message-ID: <20250318212018.3324141-9-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250318212018.3324141-1-adolf.belka@ipfire.org>
- Update from version 0.34 to 0.34.1
- Update of rootfile not required
- Changelog
0.34.1
It's mostly a build system fix release, the first .1 we are releasing.
My goal is to mimic what is done in the kernel and propagate the
critical fixes to a stable release, which should help distros to get the
fixes ahead of a new release, without having to patch it themselves.
Shortlog is below:
meson: Use short options for ln everywhere
meson: Fix setting an absolute customdir
NEWS: ditch mention of libxz.so
meson: Fix build with glibc 2.31
kmod 34.1
build: support missing gtkdocize in releases
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/kmod | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/kmod b/lfs/kmod
index bf2e393ec..e311dd649 100644
--- a/lfs/kmod
+++ b/lfs/kmod
@@ -24,7 +24,7 @@
include Config
-VER = 34
+VER = 34.1
# https://www.kernel.org/pub/linux/utils/kernel/kmod/
@@ -42,7 +42,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 115e7e84efd33bfc3e16b57a27ba8cb1b56056800b4d86664188cf2a5d7a5f59484b1b536b6760d153fec5ca89c9da5fd7a1df31a3c9d95e1c6cec9afd3eb1fe
+$(DL_FILE)_BLAKE2 = 87fc5c62ce16c9ce90cfff1b7b77169908773eaa29138d1c31da4d7d28fbd7bb82f116cf76ec7901ab93ca3d6fc75141855f4130bf3f740901e0e8b0dbb4f68e
install : $(TARGET)
--
2.49.0
next prev parent reply other threads:[~2025-03-18 21:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 21:20 [PATCH] ca-certificates: Update to 20250317 Adolf Belka
2025-03-18 21:20 ` [PATCH] cairo: Update to version 1.18.4 Adolf Belka
2025-03-18 21:20 ` [PATCH] dbus: Update to version 1.16.2 Adolf Belka
2025-03-18 21:20 ` [PATCH] gettext: Update to version 0.24 Adolf Belka
2025-03-18 21:20 ` [PATCH] git: Update to version 2.49.0 Adolf Belka
2025-03-18 21:20 ` [PATCH] harfbuzz: Update to version 10.4.0 Adolf Belka
2025-03-18 21:20 ` [PATCH] hwdata: Update to version 0.393 Adolf Belka
2025-03-18 21:20 ` [PATCH] iana-etc: Update to version 20250311 Adolf Belka
2025-03-18 21:20 ` Adolf Belka [this message]
2025-03-18 21:20 ` [PATCH] libcap: Update to version 2.75 Adolf Belka
2025-03-18 21:20 ` [PATCH] libedit: Update to version 20250104-3.1 Adolf Belka
2025-03-18 21:20 ` [PATCH] libseccomp: Update to version 2.6.0 Adolf Belka
2025-03-18 21:20 ` [PATCH] liburcu: Update to version 0.15.1 Adolf Belka
2025-03-18 21:20 ` [PATCH] lvm2: Update to version 2.03.31 Adolf Belka
2025-03-18 21:20 ` [PATCH] pango: Update to version 1.56.3 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=20250318212018.3324141-9-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