From: Sergei Trofimovich <slyich@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org,
Chen-Yu Tsai <wens@kernel.org>,
Seth Forshee <sforshee@kernel.org>
Subject: wireless-regdb key change broke crda tests after 37dcea0e6e5
Date: Tue, 6 Feb 2024 11:25:14 +0000 [thread overview]
Message-ID: <ZcIXGjzrZrXPCBcp@nz.home> (raw)
Hi `crda` and `wireless-regdb` maintainers!
`nixpkgs` attempted to update to latest `wireless-regdb-2024.01.23` from
`2024.01.23` and got `crda` verification failures at
https://github.com/NixOS/nixpkgs/pull/286012:
crda> make verify
crda> CHK ...-wireless-regdb-2024.01.23/lib/crda/regulatory.bin
crda> Database signature verification failed.
crda> Invalid or empty regulatory file, note: a binary regulatory file should be used.
crda> make: *** [Makefile:161: verify] Error 234
Bisect says the suspect is key change at done by https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=37dcea0e6e5effb4228fe385e906edba3cbee389
"wireless-regdb: Update keys and maintainer information".
Both `git` `master` version of `crda` and `wireless-regdb` still fail
`crda`'s `make verify`.
Should `crda` key the key update as well?
Thanks!
--
Sergei
next reply other threads:[~2024-02-06 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 11:25 Sergei Trofimovich [this message]
2024-02-06 11:47 ` wireless-regdb key change broke crda tests after 37dcea0e6e5 Johannes Berg
2024-02-06 22:27 ` Sergei Trofimovich
2024-02-07 7:58 ` Johannes Berg
2024-02-07 9:19 ` Kalle Valo
2024-02-07 9:22 ` Johannes Berg
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=ZcIXGjzrZrXPCBcp@nz.home \
--to=slyich@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sforshee@kernel.org \
--cc=wens@kernel.org \
--cc=wireless-regdb@lists.infradead.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