[ Reason ]
Provide current information about national radio regulations to the
Linux Wi-Fi stack.
[ Impact ]
Users may accidentally configure Wi-Fi hardware to use channels or
power levels that are not permitted, or may be unable to use channels
that are permitted.
[ Tests ]
- The signatures on regulatory.db are checked against the kernel trust
list by an autopkgtest test case.
- The database itself is identical to the version in unstable, and
currently identical to the upstream version.
[ Risks ]
The package is fairly trivial. The only risk I see is that the new
database could conceivably differ from the actual regulations in a
more serious way.
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
This is a backport from testing/unstable, because every suite should
get the latest rules.
Upstream changes:
- Updated the regulatory database (db.txt) following various national
radio regulatory changes.
- Regenerated the binaries and signatures (regulatory.bin,
regulatory.db, regulatory.db.p7s) and checksum (sha1sum.txt) from
db.txt.
Debian changes:
- Regenerated my signature for the regulatory database
- Removed Build-Depends: python-is-python3, which lintian flags as an
error. Reapplied the patch that was previously used to make
upstream scripts run with Python 3. I wouldn't have bothered to do
this for trixie, but this is a backport from forky.
- Disabled the uscan CI job, which would fail on trixie and doesn't
matter