New upstream release 2021.07.14

[Seth Forshee]

[Impact]

New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to-date regulatory information.

[Test Case]

Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'.

[Where problems could occur]

If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug.

[Launchpad Janitor (janitor)]

This bug was fixed in the package wireless-regdb - 2021.07.14-0ubuntu1

---------------
wireless-regdb (2021.07.14-0ubuntu1) impish; urgency=medium

  * New upstream version 2021.07.14 (LP: #1936255)
  * debian/gbp.conf: Add upstream tag format
  * debian/control: Update maintainer email address

 -- Seth Forshee <email address hidden> Wed, 14 Jul 2021 15:47:05 -0500

[Łukasz Zemczak (sil2100)]

Hello Seth, or anyone else affected,

Accepted wireless-regdb into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless-regdb/2021.07.14-0ubuntu1~21.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Seth, or anyone else affected,

Accepted wireless-regdb into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless-regdb/2021.07.14-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Seth, or anyone else affected,

Accepted wireless-regdb into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless-regdb/2021.07.14-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Okay, accepted all of those that I could (groovy is now EOL and xenial is almost-ESM). But only after accepting them I noticed that those were source syncs (and anyway the PPA had -updates enabled) - wireless-regdb is usually kept in sync between updates and security. So normally I'd say we need this to be built in a security-enabled PPA. So if we want to release this to both updates and security, we either need to do a rebuild now or ask the security team to do one and release it to their pockets.

That being said, I wonder if that's actually necessary. This feels like rather no-build-stuff package, so maybe it's still safe to get this into -security without a rebuild? Is the package actually doing any 'building', or just copying files around?

[Dimitri John Ledkov (xnox)]

It's pure datafiles arch:all package without any runtime deps, thus it is safe to copy to -security as is.

[Dimitri John Ledkov (xnox)]

I wonder if we should really just do binary copies of it, just like we do with shim. If we set it to be compressed with xz.

[Dimitri John Ledkov (xnox)]

$ dpkg-query -W wireless-regdb
wireless-regdb 2021.07.14-0ubuntu1~18.04.1

$ sudo iw reg set 00
$ sudo iw reg get
global
country 00: DFS-UNSET
 (2402 - 2472 @ 40), (N/A, 20), (N/A)
 (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
 (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
 (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
 (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
 (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
 (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
 (57240 - 63720 @ 2160), (N/A, 0), (N/A)

$ sudo iw reg set US
$ sudo iw reg get
global
country US: DFS-FCC
 (2400 - 2472 @ 40), (N/A, 30), (N/A)
 (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
 (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
 (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS
 (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
 (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
 (57240 - 71000 @ 2160), (N/A, 40), (N/A)

[Seth Forshee (sforshee)]

$ dpkg-query -W wireless-regdb
wireless-regdb 2021.07.14-0ubuntu1~20.04.1
$ iw reg get
global
country 00: DFS-UNSET
 (2402 - 2472 @ 40), (N/A, 20), (N/A)
 (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
 (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
 (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
 (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
 (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
 (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
 (57240 - 63720 @ 2160), (N/A, 0), (N/A)

$ sudo iw reg set US
$ iw reg get
global
country US: DFS-FCC
 (2400 - 2472 @ 40), (N/A, 30), (N/A)
 (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
 (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
 (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS
 (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
 (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
 (57240 - 71000 @ 2160), (N/A, 40), (N/A)

[Seth Forshee (sforshee)]

$ dpkg-query -W wireless-regdb
wireless-regdb 2021.07.14-0ubuntu1~21.04.1
$ iw reg get
global
country 00: DFS-UNSET
 (2402 - 2472 @ 40), (6, 20), (N/A)
 (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
 (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
 (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
 (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
 (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
 (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
 (57240 - 63720 @ 2160), (N/A, 0), (N/A)

$ sudo iw reg set US
$ iw reg get
global
country US: DFS-FCC
 (2400 - 2472 @ 40), (N/A, 30), (N/A)
 (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
 (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
 (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS
 (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
 (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
 (57240 - 71000 @ 2160), (N/A, 40), (N/A)

[Seth Forshee (sforshee)]

What about the trusty/xenial packages?

[Łukasz Zemczak (sil2100)]

Hey! I have no power over ESM packages - I assume that's something the security team needs to handle. Well, potentially I *could* get that into xenial still, but in theory xenial should be closed now.

[Launchpad Janitor (janitor)]

This bug was fixed in the package wireless-regdb - 2021.07.14-0ubuntu1~21.04.1

---------------
wireless-regdb (2021.07.14-0ubuntu1~21.04.1) hirsute; urgency=medium

  * Backport to hirsute (LP: #1936255)

 -- Seth Forshee <email address hidden> Wed, 14 Jul 2021 16:02:21 -0500

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for wireless-regdb has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package wireless-regdb - 2021.07.14-0ubuntu1~20.04.1

---------------
wireless-regdb (2021.07.14-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport to focal (LP: #1936255)

 -- Seth Forshee <email address hidden> Wed, 14 Jul 2021 16:13:38 -0500

[Launchpad Janitor (janitor)]

This bug was fixed in the package wireless-regdb - 2021.07.14-0ubuntu1~18.04.1

---------------
wireless-regdb (2021.07.14-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport to bionic (LP: #1936255)

 -- Seth Forshee <email address hidden> Thu, 15 Jul 2021 08:52:51 -0500

[Brian Murray (brian-murray)]

I've released this but it could use copying to -security (something I can't do).