Package: release.debian.org Severity: normal Tags: buster User: release.debian....@packages.debian.org Usertags: pu
I failed to update wireless-regdb for some time, as it needed some significant work to prepare for the regulatory database being directly loaded by the kernel (instead of by crda). This was introduced in Linux 4.15, but is currently disabled in all Debian suites. It will be enabled starting with 5.5. The version now in unstable has: 1. regulatory.bin: loadable by crda, trusted by Debian crda 2. regulatory.db-debian, regulatory.db.p7s-debian: loadable by kernel, trusted by future Debian kernels 3. regulatory.db-upstream, regulatory.db.p7s-upstream: loadable by kernel, trusted by upstream and future Debian kernels 4. regulatory.db, regulatory.db.p7s: alternative links for either (2) or (3) So this should be backward-compatible with all supported Debian releases, with one exception: On a system that has a recent kernel and (3) from elsewhere, *and* also a currently unused wireless-regdb package, upgrading wireless-regdb will effectively replace (3) with (2), which is not trusted by their kernel. They will need to run update-alternatives to fix this (this is documented in README.Debian). The update for (1) definitely should be delivered to all suites, but I'm undecided whether the other files should be included. Please advise what I should do. Ben. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
