On 14. 07. 21, 17:00, S. wrote:
and make sure it works. It would be nice if issues like this were considered as blocking issues so that new kernels don't appear in Tumbleweed until VirtualBox is known to work with them.
I will never postpone new kernels due to ignorance of nvidia, oracle, or any other company. It's not like the new kernel is released and they should adapt because they didn't know until then. They know, in most cases, as soon as -rc1 is released which gives them 6-8 weeks (!) to adapt. And still they repeatedly fail to. I saw evidence Larry and others let them know quite early in the development cycle w/o any feedback until the final release. So IMO there is no point to wait any longer, as users wouldn't complain to them and they wouldn't be pushed to release a fix earlier anyway. What we could do, is to add a support to libzypp for something like major-1 to be also specified in multiversion.kernels (/etc/zypp/zypp.conf). So that it keeps also 5.12.latest when 5.13.any is installed for example. We currently support only generic "latest" and "oldest", neither usable in this very context, IMO. thanks, -- js suse labs