On 8/18/20 1:16 PM, Manfred Hollstein wrote:
here's the point. I cannot see why/how Oracle/VB developers got
involved to find a solution for this issue - and, I completely agree
cannot see how they got involved or responded at all! This
was my main intention to bring over...
The Oracle/VB developers are the ones that have made the decision to keep their
modules outside the kernel. I presume that they are doing this to keep the Linux
version of VB as compatible as possible with that for Windows or OS X.
Why would they not be responsible to fix the issue? It is not as if openSUSE has
written VB. Our involvement is to keep the packages building and running on the
various openSUSE releases. For some time, I have been providing patches for new
kernels to Oracle. In this case, the fix was beyond my abilities.
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org