On Sat, Jul 21, 2018 at 11:53:51AM +0200, Nicolas Chauvet wrote:
> 2018-07-20 20:47 GMT+02:00 John W. Linville :
> [...]
> > QUESTIONS
> >
> > Are there reasons to oppose the Obsolete/Provides upgrade path from
> > crda to wireless-regdb?
+1 to the upgrade.
> Would it be desirable to require
On 07/21/2018 09:46 AM, Howard Howell wrote:
Your idea suffers from one thing... Who will build, maintain and ensure
that the database is accurate. World RF spectrum is a tough nut. It
flunctuates due to the birth and death of nations, ideology and
technology. Moreover some of the standards
On Fri, 2018-07-20 at 14:47 -0400, John W. Linville wrote:
> A mostly "behind the scenes" aspect of the Linux wireless LAN
> (IEEE802.11) subsystem has changed upstream with some system-level
> effects. Replacing an existing package with a cleaner but
> functionally
> equivalent package is an
John W. Linville wrote:
> Is it acceptable to trust the upstream signature of the wireless
> regulatory database? Or do we need to use some sort of Fedora
> signature? If the latter, can it be a (semi-)permanent (e.g. per
> release) signature, which could be maintained in the kernel sources? Or
>
2018-07-20 20:47 GMT+02:00 John W. Linville :
[...]
> QUESTIONS
>
> Are there reasons to oppose the Obsolete/Provides upgrade path from
> crda to wireless-regdb? Would it be desirable to require users to
> manually intervene by installing wireless-regdb by hand? FWIW, I do not
> see any benefit
On Fri, Jul 20, 2018 at 7:47 PM, John W. Linville wrote:
> A mostly "behind the scenes" aspect of the Linux wireless LAN
> (IEEE802.11) subsystem has changed upstream with some system-level
> effects. Replacing an existing package with a cleaner but functionally
> equivalent package is an
Package renaming using Obsoletes/Provides will be a problem *ONLY* if
applications confuse the version of the package with the CRDB format version:
these are intrinsically different versions even if there is a single package
renaming event that is coincident with the CRDB format change.
A mostly "behind the scenes" aspect of the Linux wireless LAN
(IEEE802.11) subsystem has changed upstream with some system-level
effects. Replacing an existing package with a cleaner but functionally
equivalent package is an attractive option, but there are questions
regarding the update path, how
