From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e91c83490be8d248796d50b0c9bca3976199551c
Date: Tue, 16 Apr 2019 17:06:49 +0100 [thread overview]
Message-ID: <20190416160649.B743284FDAF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3439 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via e91c83490be8d248796d50b0c9bca3976199551c (commit)
from fea27a56f7ef299fa2793971ef6e49f3a423fdc3 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit e91c83490be8d248796d50b0c9bca3976199551c
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Apr 16 18:05:18 2019 +0200
wireless-regdb: update to 2019.03.01
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/wireless-regdb | 5 ++++-
config/rootfiles/{oldcore/51 => core/131}/filelists/wireless-regdb | 0
lfs/wireless-regdb | 6 +++---
3 files changed, 7 insertions(+), 4 deletions(-)
copy config/rootfiles/{oldcore/51 => core/131}/filelists/wireless-regdb (100%)
Difference in files:
diff --git a/config/rootfiles/common/wireless-regdb b/config/rootfiles/common/wireless-regdb
index 2dcdbca32..7e830ae1f 100644
--- a/config/rootfiles/common/wireless-regdb
+++ b/config/rootfiles/common/wireless-regdb
@@ -1,5 +1,8 @@
+lib/firmware/regulatory.db
+lib/firmware/regulatory.db.p7s
#usr/lib/crda
#usr/lib/crda/pubkeys
-usr/lib/crda/pubkeys/linville.key.pub.pem
+usr/lib/crda/pubkeys/sforshee.key.pub.pem
usr/lib/crda/regulatory.bin
#usr/share/man/man5/regulatory.bin.5.gz
+#usr/share/man/man5/regulatory.db.5.gz
diff --git a/config/rootfiles/core/131/filelists/wireless-regdb b/config/rootfiles/core/131/filelists/wireless-regdb
new file mode 120000
index 000000000..c9205b3cf
--- /dev/null
+++ b/config/rootfiles/core/131/filelists/wireless-regdb
@@ -0,0 +1 @@
+../../../common/wireless-regdb
\ No newline at end of file
diff --git a/lfs/wireless-regdb b/lfs/wireless-regdb
index 84cad32ea..182f0371f 100644
--- a/lfs/wireless-regdb
+++ b/lfs/wireless-regdb
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2019 IPFire Team <info(a)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 = 2014.11.18
+VER = 2019.03.01
THISAPP = wireless-regdb-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -41,7 +41,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = d750c402c5510add7380edcb1d9b75b2
+$(DL_FILE)_MD5 = b5eb2d0cc23f5e495a59405e34ce437f
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-04-16 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190416160649.B743284FDAF@people01.i.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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