On 02/18/2016 07:03 PM, Mike Latimer wrote:
Hi Stephan,
On Thursday, February 18, 2016 03:14:46 PM Stephan Uhlmann wrote:
in http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/x86_6 4/ the last update for virtualbox-{host|guest}-kmp-* is for kernel 3.11.10-29.
openSUSE 13.1 was recently updated to kernel 3.11.10-34. Will there be an update of the Virtualization-repo?
Seems to affect 13.2 as well.
Larry is the official maintainer for virtualbox in OBS. A couple of weeks ago he commented (on the project directly) that openSUSE 13.2 will stay with VirtualBox 4.3, and therefore builds for the older versions of openSUSE (including 13.1) were being disabled in the project.
Larry - I don't know the whole history here, but I did a couple of local builds of the current code (5.0.14) using 13.1 and 13.2 targets, and everything did seem to build okay. As the download repos already contain the 5.x version built against old kernels, does it make sense to enable 13.1/13.2 and update the builds in these repos (assuming the code does build fine in OBS) to match current kernels?
I know the newer version of VB will build on 13.1 and 13.2. The only problem has been that the builds of the 32-bit variant of 5.0.x have regularly crashed in OBS. It takes a long time for the crash to occur, AND it keeps the updated VB from making it to either TW or Leap. If it were a matter of running out of resources, the problem would be easily fixed. Instead, it seems that the qemu-based build just stops building and gets kicked off the system after 28000 sec. When I first took over as maintainer, I asked about updating to a new version and received the following answer: =================================================
As 13.1 has stayed with VB 4.2.X, should I infer that 13.2 should stay with 4.3.X? The reason for asking is that VB 5.0.2 has just been released with a fix for the problem listed in bsc#939299. I'm not sure that Oracle will release a new 4.3.X version to fix this problem. If they do, then I'll make the appropriate commit, but if not, then I would favor pushing 5.0.2 for oS 13.2. I have already done the build locally.
It is mostly problem of balancing new features/fixes with regressions caused by other changes. For that reason we try to keep the version updates at least just in range of the same branch (4.3, 4.2, 5.0) for the respective products. ================================================= As I have no possibility of doing any testing on 13.1, I feel that it is necessary to make as few changes as possible there. Similarly, I prefer to keep 13.2 at 4.3.x. Combining the policy as stated above, and the failures of 32-bit builds, I have decided not to try to build 5.0.x for 13.1 or 13.2. I would, of course, relinquish the maintainership to anyone that objects. :) Larry -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org