From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] wireless-regdb: Update to version 2026.02.04
Date: Fri, 27 Feb 2026 19:18:38 +0100 [thread overview]
Message-ID: <20260227181838.3716442-10-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260227181838.3716442-1-adolf.belka@ipfire.org>
- Update from version 2025.10.07 to 2026.02.04
- No change to rootfile
- Changelog
2026.02.04
wireless-regdb: Update broken link in regulatory.bin(5) manpage
wireless-regdb: Update regulatory info for Malaysia (MY) for 2024
wireless-regdb: Update regulatory info for Malaysia (MY) for 2025
wireless-regdb: Update regulatory info for Canada (CA) for 2025
wireless-regdb: update regulatory database based on preceding changes
wireless-regdb: Update regulatory info for Tunisia (TN) on 6GHz for 2025
wireless-regdb: Update regulatory info for Australia (AU) for 2025
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/wireless-regdb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/wireless-regdb b/lfs/wireless-regdb
index 29ea579f9..72c644591 100644
--- a/lfs/wireless-regdb
+++ b/lfs/wireless-regdb
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2025 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2026 IPFire Team <info@ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 2025.10.07
+VER = 2026.02.04
# https://mirrors.edge.kernel.org/pub/software/network/wireless-regdb/
THISAPP = wireless-regdb-$(VER)
@@ -42,7 +42,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 655c637ca2a9269b6b17bc374c7d09dcbbc5228aaefcbe60cd0c24dc78d778a56848a338f830cac8deed7930100a0fffcfdc2d694513c4afa5d537ccf9397f97
+$(DL_FILE)_BLAKE2 = 51b528effd27bef82337babc911e85586a105efce758264d52065b8b2137f08a803e0962ef07a600fec36fd110eecacd1b88d2569aa73ad2a289702164d88581
install : $(TARGET)
--
2.53.0
prev parent reply other threads:[~2026-02-27 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 18:18 [PATCH] core201: Ship iptables Adolf Belka
2026-02-27 18:18 ` [PATCH] core201: Ship lua Adolf Belka
2026-02-27 18:18 ` [PATCH] core201: Ship wireless-regdb Adolf Belka
2026-02-27 18:18 ` [PATCH] ddrescue: Update to version 1.30 Adolf Belka
2026-02-27 18:18 ` [PATCH] fping: Update to version 5.5 Adolf Belka
2026-02-27 18:18 ` [PATCH] iptables: Update to version 1.8.12 Adolf Belka
2026-02-27 18:18 ` [PATCH] lua: Update to version 5.4.8 Adolf Belka
2026-02-27 18:18 ` [PATCH] minicom: Update to version 2.11 Adolf Belka
2026-02-27 18:18 ` [PATCH] tshark: Update to version 4.6.4 Adolf Belka
2026-02-27 18:18 ` Adolf Belka [this message]
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=20260227181838.3716442-10-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