New upstream release 2022.06.06

Bug #1980145 reported by Seth Forshee
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wireless-regdb (Ubuntu)
Fix Released
Undecided
Seth Forshee
Bionic
Fix Released
Undecided
Seth Forshee
Focal
Fix Released
Undecided
Seth Forshee
Impish
Won't Fix
Undecided
Seth Forshee
Jammy
Fix Released
Undecided
Seth Forshee
Kinetic
Fix Released
Undecided
Seth Forshee

Bug Description

[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.

Seth Forshee (sforshee)
Changed in wireless-regdb (Ubuntu Bionic):
assignee: nobody → Seth Forshee (sforshee)
status: New → In Progress
Changed in wireless-regdb (Ubuntu Focal):
status: New → In Progress
assignee: nobody → Seth Forshee (sforshee)
Changed in wireless-regdb (Ubuntu Impish):
status: New → In Progress
assignee: nobody → Seth Forshee (sforshee)
Changed in wireless-regdb (Ubuntu Jammy):
status: New → In Progress
assignee: nobody → Seth Forshee (sforshee)
Revision history for this message
Seth Forshee (sforshee) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
wireless-regdb (2022.06.06-0ubuntu1) kinetic; urgency=medium

  * New upstream version 2022.06.06 (LP: #1980145)

 -- Seth Forshee <email address hidden> Wed, 29 Jun 2022 08:23:01 -0500

Changed in wireless-regdb (Ubuntu Kinetic):
status: In Progress → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Seth, or anyone else affected,

Accepted wireless-regdb into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless-regdb/2022.06.06-0ubuntu1~22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

Changed in wireless-regdb (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

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/2022.06.06-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.

Changed in wireless-regdb (Ubuntu Focal):
status: In Progress → Fix Committed
tags: added: verification-needed-focal
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

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/2022.06.06-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.

Changed in wireless-regdb (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed-bionic
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

One thing that can be a bit confusing for the focal and bionic uploads - the backport includes the change from kinetic that was removing the Suggests: crda (as the package is no longer available there). I think this change, even though it's in the changelog, might be missing from the backports - at least I didn't see those in the debdiff (but maybe the suggests was never there..?). It's not too relevant as it's only a suggests and the crda package is still available in the series. But still, something to keep in mind.

Also, note to other SRU members: this package needs to be kept in sync in -security.

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (wireless-regdb/2022.06.06-0ubuntu1~20.04.1)

All autopkgtests for the newly accepted wireless-regdb (2022.06.06-0ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

linux-oracle-5.15/5.15.0-1013.17~20.04.1 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#wireless-regdb

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Seth Forshee (sforshee) wrote :

I can see how that's a bit confusing; possibly I should be handling the backport changelogs differently. But yes, I did not remove the Suggests: crda in the backports except in jammy where the crda package had also been removed.

Revision history for this message
Seth Forshee (sforshee) wrote :

The autopkgtest failure for linux-oracle is a timeout during the rebuild test. Clearly this isn't caused by the wireless-regdb update, so the test should be retried or hinted (I can do neither).

Revision history for this message
Seth Forshee (sforshee) wrote :

I tested the jammy, focal, and bionic patches as described in the test case from the description. The kernel was able to load the database, and I was able to successfully query and change the regulatory domain. Marking verification as done.

tags: added: verification-done verification-done-bionic verification-done-focal verification-done-jammy
removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Thanks! I'll release it for both -updates and -security. The package has been built against -proposed, but that should be fine as this is a pure-data package.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package wireless-regdb - 2022.06.06-0ubuntu1~22.04.1

---------------
wireless-regdb (2022.06.06-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport to jammy (LP: #1980145)

 -- Seth Forshee <email address hidden> Wed, 29 Jun 2022 09:12:48 -0500

Changed in wireless-regdb (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

  * Backport to focal (LP: #1980145)

 -- Seth Forshee <email address hidden> Sat, 02 Jul 2022 15:59:36 -0500

Changed in wireless-regdb (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

  * Backport to bionic (LP: #1980145)

 -- Seth Forshee <email address hidden> Sat, 02 Jul 2022 16:08:13 -0500

Changed in wireless-regdb (Ubuntu Bionic):
status: Fix Committed → Fix Released
Seth Forshee (sforshee)
Changed in wireless-regdb (Ubuntu Impish):
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.