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] wireless-regdb: Update to version 2026.05.30
Date: Wed, 10 Jun 2026 21:02:00 +0200	[thread overview]
Message-ID: <20260610190208.3662425-15-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260610190208.3662425-1-adolf.belka@ipfire.org>

- Update from version 2026.02.04 to 2026.05.30
- No change in rootfile
- Changelog
2026.05.30
	wireless-regdb: Update regulatory rules for Sri Lanka (LK)
	wireless-regdb: Update regulatory info for Brunei Darussalam (BN) for 2022
	wireless-regdb: allow 320MHz channel width for Russia
	wireless-regdb: Update 6 GHz rules for South Korea (KR)
	wireless-regdb: Update 6 GHz rules for South Africa (ZA)
	wireless-regdb: Fix 60 GHz power unit for Ukraine (UA)
	wireless-regdb: Update 5/6 GHz power rules for Russia (RU)
	wireless-regdb: Update 6 GHz rules for Hong Kong (HK)
	wireless-regdb: Add regulatory info for CEPT countries FO, GI, IM, SM and VA ...
2026.03.18
	wireless-regdb: Update regulatory rules for India (IN) on 6GHz
	wireless-regdb: Replace M2Crypto with cryptography package
	wireless-regdb: Fix regulatory.bin signing with new M2Crypto

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 lfs/wireless-regdb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lfs/wireless-regdb b/lfs/wireless-regdb
index 72c644591..f8d9733b5 100644
--- a/lfs/wireless-regdb
+++ b/lfs/wireless-regdb
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2026.02.04
+VER        = 2026.05.30
 #            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 = 51b528effd27bef82337babc911e85586a105efce758264d52065b8b2137f08a803e0962ef07a600fec36fd110eecacd1b88d2569aa73ad2a289702164d88581
+$(DL_FILE)_BLAKE2 = 81aa422097580319e6088d0a52a2c4007696331df175c3aed1ce6b6c750e9b7bda08a4aa4ee6249abaa3f283f8a942803eefca8334020de68c33f5e7e35a57e0
 
 install : $(TARGET)
 
-- 
2.54.0



      parent reply	other threads:[~2026-06-10 19:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 19:01 [PATCH] alsa: Update to version 1.2.16 Adolf Belka
2026-06-10 19:01 ` [PATCH] bash: Update to version 5.3 patch 15 Adolf Belka
2026-06-10 19:01 ` [PATCH] core204: Ship bash Adolf Belka
2026-06-10 19:01 ` [PATCH] core204: Ship harfbuzz Adolf Belka
2026-06-10 19:01 ` [PATCH] core204: Ship hwdata Adolf Belka
2026-06-10 19:01 ` [PATCH] core204: Ship kbd Adolf Belka
2026-06-10 19:01 ` [PATCH] core204: Ship less Adolf Belka
2026-06-10 19:01 ` [PATCH] core204: Ship sqlite Adolf Belka
2026-06-10 19:01 ` [PATCH] core204: Ship wireless-regdb Adolf Belka
2026-06-10 19:01 ` [PATCH] harfbuzz: Update to version 14.2.1 Adolf Belka
2026-06-10 19:01 ` [PATCH] hwdata: Update to version 0.408 Adolf Belka
2026-06-10 19:01 ` [PATCH] kbd: Update to version 2.10.0 Adolf Belka
2026-06-10 19:01 ` [PATCH] less; Update to version 704 Adolf Belka
2026-06-10 19:01 ` [PATCH] sqlite: Update to version 3530200 Adolf Belka
2026-06-10 19:02 ` 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=20260610190208.3662425-15-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