[opensuse-factory] Leap 15 VirtualBox still requires libvpx.so.1 rather than using libvpx4
Hello, When installing VirtualBox (downloaded from the virtualbox.org) the Leap 15 installation is looking for the old libvpx 1.6 rather than using libvpx4. Until Oracle addresses this situation (this is a slow process) you can use virtualbox that comes with Leap 15. Or you can search for libvpx 1.6 package and store it locally. Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2018-06-01 at 15:02 -0400, Roman Bysh wrote:
Hello,
When installing VirtualBox (downloaded from the virtualbox.org) the Leap 15 installation is looking for the old libvpx 1.6 rather than using libvpx4. Until Oracle addresses this situation (this is a slow process) you can use virtualbox that comes with Leap 15.
Or you can search for libvpx 1.6 package and store it locally.
This is DEFINITVELY a candidate mail that would belong to opensuse@opensuse.org or opensuse-support@opensuse.org. It has no relevance to the development of future openSUSE releases (Leap 15.1 and Tumbleweed). Cheers Dominique
On 01/06/18 03:35 PM, Dominique Leuenberger / DimStar wrote:
On Fri, 2018-06-01 at 15:02 -0400, Roman Bysh wrote:
Hello,
When installing VirtualBox (downloaded from the virtualbox.org) the Leap 15 installation is looking for the old libvpx 1.6 rather than using libvpx4. Until Oracle addresses this situation (this is a slow process) you can use virtualbox that comes with Leap 15.
Or you can search for libvpx 1.6 package and store it locally.
This is DEFINITVELY a candidate mail that would belong to opensuse@opensuse.org or opensuse-support@opensuse.org.
It has no relevance to the development of future openSUSE releases (Leap 15.1 and Tumbleweed).
Cheers Dominique
Agreed. Thanks. -- Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2018-06-01 21:02, Roman Bysh wrote:
Hello,
When installing VirtualBox (downloaded from the virtualbox.org) the Leap 15 installation is looking for the old libvpx 1.6 rather than using libvpx4. Until Oracle addresses this situation (this is a slow process) you can use virtualbox that comes with Leap 15.
It's obvious they did not make a package for 15. The most recent entry they have is still 13.2 (of all things!)/42. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/01/2018 04:20 PM, Jan Engelhardt wrote:
On Friday 2018-06-01 21:02, Roman Bysh wrote:
Hello,
When installing VirtualBox (downloaded from the virtualbox.org) the Leap 15 installation is looking for the old libvpx 1.6 rather than using libvpx4. Until Oracle addresses this situation (this is a slow process) you can use virtualbox that comes with Leap 15.
It's obvious they did not make a package for 15. The most recent entry they have is still 13.2 (of all things!)/42.
I know this thread should be in opensuse-support, but since it was started here, I'm keeping this reply in the factory ML. It is a real pain to generate the kernel modules for Leap 15.0. The problem is a relatively old kernel with some APIs backported from newer kernels. The usual way to handle builds against multiple kernel versions is to use the macros built into the kernel to select code that will work with that version. When the kernel suddenly has features that come from much newer versions, those tests break down. I have long had this kind of problem with Ubuntu kernels, and I have stopped supporting them for some wireless modules. Obviously, as the VirtualBox maintainer for openSUSE, I am allowed to grumble a lot, but I have to make the official packages build and work. Within the RPM build process, the source can be selectively modified for Leap 15.0 through the conditional application of patches. Even if the Oracle RPM had not required a different version of libvpx, I'm quite sure it would have stumbled when it tried to build the kernel modules. @Roman: Why are you trying to use the Oracle RPM? Is there something that our packages are missing? Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/06/18 09:20 PM, Larry Finger wrote:
On 06/01/2018 04:20 PM, Jan Engelhardt wrote:
On Friday 2018-06-01 21:02, Roman Bysh wrote:
Hello,
When installing VirtualBox (downloaded from the virtualbox.org) the Leap 15 installation is looking for the old libvpx 1.6 rather than using libvpx4. Until Oracle addresses this situation (this is a slow process) you can use virtualbox that comes with Leap 15.
It's obvious they did not make a package for 15. The most recent entry they have is still 13.2 (of all things!)/42.
I know this thread should be in opensuse-support, but since it was started here, I'm keeping this reply in the factory ML.
It is a real pain to generate the kernel modules for Leap 15.0. The problem is a relatively old kernel with some APIs backported from newer kernels. The usual way to handle builds against multiple kernel versions is to use the macros built into the kernel to select code that will work with that version. When the kernel suddenly has features that come from much newer versions, those tests break down. I have long had this kind of problem with Ubuntu kernels, and I have stopped supporting them for some wireless modules. Obviously, as the VirtualBox maintainer for openSUSE, I am allowed to grumble a lot, but I have to make the official packages build and work. Within the RPM build process, the source can be selectively modified for Leap 15.0 through the conditional application of patches. Even if the Oracle RPM had not required a different version of libvpx, I'm quite sure it would have stumbled when it tried to build the kernel modules.
@Roman: Why are you trying to use the Oracle RPM? Is there something that our packages are missing?
Larry Larry,
I was using the Oracle package out of habit because everything was contained in one package. The Oracle support is very slow so I dropped the Oracle package and switched to using virtualbox that comes with openSUSE. If I have any problems I can always ask you. I trust your judgment. ;-) Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/04/2018 01:00 PM, Roman Bysh wrote:
I was using the Oracle package out of habit because everything was contained in one package. The Oracle support is very slow so I dropped the Oracle package and switched to using virtualbox that comes with openSUSE. If I have any problems I can always ask you. I trust your judgment. ;-)
Thanks for the compliment. Depending on the circumstances, it may take a few weeks from the time that Oracle has a new release until it builds on openSUSE Factory, and then it gets pushed through to Tumbleweed. The worst so far was the jump from VB 5.1.x to 5.2.x, which required an update to kbuild. As VB was the only openSUSE package that needed the new code, I had to generate and push the kbuild package as well. That added to the time. Despite these problems, we try to get the latest VB available for openSUSE users. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/06/18 03:24 PM, Larry Finger wrote:
On 06/04/2018 01:00 PM, Roman Bysh wrote:
I was using the Oracle package out of habit because everything was contained in one package. The Oracle support is very slow so I dropped the Oracle package and switched to using virtualbox that comes with openSUSE. If I have any problems I can always ask you. I trust your judgment. ;-)
Thanks for the compliment.
Depending on the circumstances, it may take a few weeks from the time that Oracle has a new release until it builds on openSUSE Factory, and then it gets pushed through to Tumbleweed. The worst so far was the jump from VB 5.1.x to 5.2.x, which required an update to kbuild. As VB was the only openSUSE package that needed the new code, I had to generate and push the kbuild package as well. That added to the time.
Despite these problems, we try to get the latest VB available for openSUSE users.
Larry
Oracle's VirtualBox Q&A team should have upgraded libvpx1 to libvpx4. Unfortunately they are very slow in upgrading to Leap 15.0. They still show openSUSE 13.2 and 42.2 as downloads. -- Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Dominique Leuenberger / DimStar -
Jan Engelhardt -
Larry Finger -
Roman Bysh