Am Freitag, 7. Februar 2020, 08:27:29 CET schrieb Jiri Slaby:
On 07. 02. 20, 8:12, Hans-Peter Jansen wrote:
can we have a late 5.4 kernel for TW before going to 5.5, *please*.
Hi,
no, why would we? Unless there is a serious bug or problem, of course...
Well, obviously, that happened already. I didn't checked that: https://build.opensuse.org/package/revisions/openSUSE:Factory/kernel-source
The virtualbox woes with 5.5 will keep that move more painful than ever.
You have to complain to virtualbox authors. It's apparently their fault not to upstream the modules in the past decade. It cannot stop new kernels to roll in openSUSE.
I didn't ask you to stop, Jiri. This was meant as a polite request to arrange the timing a bit, and to fill the gap with another revision of 5.4 in order to avoid the trap, that we were captured in transition of 5.3 to 5.4 on TW, where we bobbed up and down with 5.3.12, while Leap got up to 5.3.16 at the same time. https://lists.opensuse.org/opensuse-factory/2019-12/msg00205.html
The other option is to politely ask our vbox maintainer to keep vbox up with 5.5. What's the problem, actually?
https://www.virtualbox.org/ticket/19145 Larry knows about this already, but given the convoluted code in question, even the code owners seems to struggle with this.. :-( Fun fact, the evil bits from nvidia suffered from the same issue, but it took a couple of hours to get fixed. This is a fine example, how code quality pays off in the long run.
While at it, is KVM fully tested with 5.5 on both sides?
Provided openQA runs on KVM -- and trust me, the kernel is massaged there -- I believe the answer is: as much as possible.
Sorry, Jiri, it wasn't my intention to patronize you or your colleges, just to make you aware of some issues, that affects quite a few users, and which can lead to bad timing effects from the users POV (in the *best* case, that is). Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org