Bug#1006127: wireless-regdb stable policy
Hi,
On Sat, Feb 19, 2022 at 04:30:35PM +0000, Jiaxun Yang wrote:
>
>
> 在 2022/2/19 16:27, Salvatore Bonaccorso 写道:
> > Hi,
> >
> > On Sat, Feb 19, 2022 at 02:49:32PM +0000, Jiaxun Yang wrote:
> > > Package: wireless-regdb
> > > Version: 2021.08.28-1
> > > Severity: grave
> > >
> > > Dear Maintainer
> > >
> > > wireless-regdb stores regulation information for various regions. It's
> > > importatnt to keep
> > > it updated on every system to ensure legal compliance on user's system.
> > >
> > > For example, China resctrcted transmission power for 5150 - 5350 MHz to 20
> > > dBm, while
> > > the version in stable is still using the old 23 dBm limitation. System
> > > running stable can
> > > be accused violation of laws.
> > >
> > > Thus this package needs to be a part of security update to all stable
> > > release to prevent
> > > legal issues for users.
> > In avoidance of doubts, no this is not material to be shipped via a
> > security update, but it can in fact be updated in stable through the
> > stable point releases (and when needed updated earlier through the
> > updates suites).
> Hi,
>
> I see tzdata updates is shipping through security in strectch, I think
> wireless-regdb is in similiar situation.
You are mentioning stretch, which is supported by the LTS project. In
fact this is true there, because for the LTS suite there is no point
release approach. You will notice that tzdata for stable is released
at point releases times, and when needed earlier through the updates
suite, see for example
https://lists.debian.org/debian-stable-announce/2021/10/msg00002.html
.
Anyway, the point is it can be updated for stable, but the channel
would be another one. It first should be updated in unstable and
testing, and then the other suites can follow via the mentioned
approach.
HTH,
Regards,
Salvatore
Reply to: