From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "Nick Kossifidis" <mickflemm@gmail.com>,
"Thomas Bächler" <thomas@archlinux.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ANN] wireless-regdb: master-2013-10-11
Date: Wed, 20 Nov 2013 11:47:35 -0500 [thread overview]
Message-ID: <20131120164734.GD2220@tuxdriver.com> (raw)
In-Reply-To: <20131120162538.GB2220@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
On Wed, Nov 20, 2013 at 11:25:38AM -0500, John W. Linville wrote:
> On Wed, Nov 20, 2013 at 11:29:50AM +0100, Luis R. Rodriguez wrote:
> > On Mon, Nov 4, 2013 at 8:18 PM, John W. Linville <linville@tuxdriver.com> wrote:
> > > On Fri, Nov 01, 2013 at 12:32:39AM +0100, Thomas Bächler wrote:
> > >> Am 11.10.2013 22:24, schrieb John W. Linville:
> > >> > (Cutting the short log, since the original version got classified as
> > >> > SPAM on vger.kernel.org...??)
> > >> >
> > >> > A new release of wireless-regdb (master-2013-10-11) is available at:
> > >> >
> > >> > http://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2013.10.11.tar.gz
> > >> >
> > >> > Here is the short log of the changes included since the 2013-02-13
> > >> > release:
> > >> >
> > >> > SNIP -- you'll have to check it yourself:
> > >>
> > >> We can't use the database file:
> > >>
> > >> $ regdbdump regulatory.bin
> > >> Database signature verification failed.
> > >
> > > OK, I probably screwed-up something. I'll investigate, but it may
> > > take few days while I recover from some extended travel...
> >
> > Hey John, it seems other folks are reporting this as well [0].
> >
> > [0] http://forums.gentoo.org/viewtopic-p-7440278.html
>
> Sorry, I dropped the ball after I couldn't replicate the problem
> locally. Does anyone have a suggestion as to what the issue might be?
Hmmm...actually, I may have accidentally regeneratd a key. I'm not
sure why this didn't seem to cause a problem for me...
Can someone try to verify the signature on the attached regulatory.bin file?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
[-- Attachment #2: regulatory.bin --]
[-- Type: application/octet-stream, Size: 3840 bytes --]
next prev parent reply other threads:[~2013-11-20 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 20:24 [ANN] wireless-regdb: master-2013-10-11 John W. Linville
2013-10-11 20:24 ` [wireless-regdb] " John W. Linville
2013-10-11 20:39 ` John W. Linville
2013-10-11 20:39 ` [wireless-regdb] " John W. Linville
2013-10-31 23:32 ` Thomas Bächler
2013-11-04 19:18 ` John W. Linville
2013-11-20 10:29 ` Luis R. Rodriguez
2013-11-20 16:25 ` John W. Linville
2013-11-20 16:47 ` John W. Linville [this message]
2013-11-20 18:08 ` Thomas Bächler
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=20131120164734.GD2220@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mickflemm@gmail.com \
--cc=thomas@archlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.