On 19. 07. 19, 5:38, simonizor wrote:
The kernel releases for Tumbleweed have been coming out pretty slowly lately. When I started using Tumbleweed in November of 2017, it was not at all uncommon for Tumbleweed to get a new kernel release before Arch got the same kernel release. Now, it seems like we get new kernel releases a week after they are released upstream at best. I personally have been using kernel:stable because of this, but due to the kmp setup and not using dkms, not everyone can do this.
Is there a reason for this? I personally have not had a single issue with the kernels from the kernel:stable repo (I'm using 5.2.1 right now without a single hiccup), so the quality of the kernels does not seem to be the issue.
I, as a maintainer of that kernel, can only say, that the process from my side hasn't changed. The submit requests are still as quick as they used to be. I guess the culprit is the change in staging process performed few weeks ago. Kernel used to be a single package in a staging project before that. Now, 5.2.1 (superseding earlier 5.2 submission) is sitting in Staging:C with gcc9, linux-glibc-devel, libreoffice and dozen of other packages since 07/08. Some of the mentioned broke the staging, so they were removed (like linux-glibc-devel breaking firefox). And that triggered a full rebuild. Actually a full double-rebuild as kernel usually triggers a second full rebuild on its own. libreoffice was still broken in the staging this morning (even though it was removed from the staging 3 days ago). Libuv was removed this morning, perhaps to fix that, and given cmake depends on libuv, almost full rebuild was triggered by that again. And so on :). Now, we will see in a day or so, if the staging is working or not... Note that this is pretty usual and normal with stagings and changes in core packages like the above, I am not accusing anybody. I would only not put gcc9, linux-glibc-devel, and kernel together in a single staging ;). I usually don't mind (or care) as I personally use Kernel:stable anyway (*). But due to this, recently, the TCP SACK CVE fixes landed to Tumbleweed long after the EMBARGO was dropped and long after many other distributions already had a fixed kernel. Given users like you are complaining staging managers might consider a change :). (*) Note that packman also have a Factory repo which builds against Kernel:stable. regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org