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?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1936255

Title:
  New upstream release 2021.07.14

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Trusty:
  In Progress
Status in wireless-regdb source package in Xenial:
  In Progress
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Groovy:
  Won't Fix
Status in wireless-regdb source package in Hirsute:
  Fix Committed
Status in wireless-regdb source package in Impish:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to