Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #206693 > unrolled thread

kernel policy vs bug handling (how to followup #919227 ?)

Back to article view | Back to linux.debian.user

Contents

  kernel policy vs bug handling (how to followup #919227 ?) Andrea Borgia <andrea@borgia.bo.it> - 2019-03-27 21:30 +0100
    Re: kernel policy vs bug handling (how to followup #919227 ?) Andrei POPESCU <andreimpopescu@gmail.com> - 2019-06-08 12:20 +0200
      Re: kernel policy vs bug handling (how to followup #919227 ?) Andrea Borgia <andrea@borgia.bo.it> - 2019-06-08 16:10 +0200
        Re: kernel policy vs bug handling (how to followup #919227 ?) Andrei POPESCU <andreimpopescu@gmail.com> - 2019-06-09 09:30 +0200
          Re: kernel policy vs bug handling (how to followup #919227 ?) deloptes <deloptes@gmail.com> - 2019-06-09 22:30 +0200

#206693 — kernel policy vs bug handling (how to followup #919227 ?)

Hi.

In an earlier post[1] I mentioned an ACPI LID issue with my laptop, 
which has been fixed in the current 5.x series[2].

My questions:

1) other than commenting on my own bugreport[3] with this information, 
should I do anything else, like closing it or adding some special tags? 
As far as current "testing" branch is concerned, this bug is still 
present, unless you install a kernel from "experimental"[4] or upstream.

2) maybe I am not using the proper keywords but I can't seem to find 
information on Debian kernel policy, specifically: when does a new 
kernel from upstream enter "unstable"? Later on it would move to 
"testing" and then "stable", this part I know how it works, but I am 
missing the initial step. I already have a working kernel package so 
this is just curiosity regarding the process, no begging :)

Thanks,
Andrea.


[1] https://lists.debian.org/debian-user/2019/01/msg00249.html

[2] https://bugzilla.kernel.org/show_bug.cgi?id=202421

[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919227

[4] 
https://qa.debian.org/developer.php?login=debian-kernel%40lists.debian.org

[toc] | [next] | [standalone]

#209756

[Multipart message — attachments visible in raw view] — view raw

On Mi, 27 mar 19, 21:22:18, Andrea Borgia wrote:
> Hi.
> 
> In an earlier post[1] I mentioned an ACPI LID issue with my laptop, which
> has been fixed in the current 5.x series[2].
> 
> My questions:
> 
> 1) other than commenting on my own bugreport[3] with this information,
> should I do anything else, like closing it or adding some special tags? As
> far as current "testing" branch is concerned, this bug is still present,
> unless you install a kernel from "experimental"[4] or upstream.

If there is a fixed version in Debian you can mark the bug accordingly.

> 2) maybe I am not using the proper keywords but I can't seem to find
> information on Debian kernel policy, specifically: when does a new kernel
> from upstream enter "unstable"?

Usually quite soon after the upstream kernel is released as "stable".

During the freeze only packages meant for the next stable should be 
uploaded to unstable (as per Release Team policy), so new versions might 
go to experimental or not be packaged at all until after the release.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#209757

Il 08/06/19 12:18, Andrei POPESCU ha scritto:

> On Mi, 27 mar 19, 21:22:18, Andrea Borgia wrote:
>> 2) maybe I am not using the proper keywords but I can't seem to find
>> information on Debian kernel policy, specifically: when does a new kernel
>> from upstream enter "unstable"?
> 
> Usually quite soon after the upstream kernel is released as "stable".
> 
> During the freeze only packages meant for the next stable should be
> uploaded to unstable (as per Release Team policy), so new versions might
> go to experimental or not be packaged at all until after the release.

"Unstable" still has 4.19 whereas 5.0.x and 5.1.x are marked as stable 
upstream, so I guess we'll see them in the next release.

Thanks,
Andrea.

[toc] | [prev] | [next] | [standalone]

#209768

[Multipart message — attachments visible in raw view] — view raw

On Sb, 08 iun 19, 16:08:27, Andrea Borgia wrote:
> Il 08/06/19 12:18, Andrei POPESCU ha scritto:
> 
> > On Mi, 27 mar 19, 21:22:18, Andrea Borgia wrote:
> > > 2) maybe I am not using the proper keywords but I can't seem to find
> > > information on Debian kernel policy, specifically: when does a new kernel
> > > from upstream enter "unstable"?
> > 
> > Usually quite soon after the upstream kernel is released as "stable".
> > 
> > During the freeze only packages meant for the next stable should be
> > uploaded to unstable (as per Release Team policy), so new versions might
> > go to experimental or not be packaged at all until after the release.
> 
> "Unstable" still has 4.19 whereas 5.0.x and 5.1.x are marked as stable
> upstream, so I guess we'll see them in the next release.

Debian is typically using LTS kernels for stable releases, so buster 
will most likely release with 4.19.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#209779

Andrei POPESCU wrote:

> Debian is typically using LTS kernels for stable releases, so buster
> will most likely release with 4.19.

This is a good choice - running custom 4.19 I can say that I will not intend
to upgrade it in near feature.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web