[opensuse-factory] Selecting Kernel_HEAD_standard with osc build
Since kernel 4.10-rc2 was released, the VirtualBox modules have failed to build with the KOTD packages. The message is something like "Package Virtualization/virtualbox failed to build in Kernel_HEAD_standard/x86_64". The problem is due to a kernel API change in get_pages_remote(). Oracle has fixed this problem with VB 5.1.14, and the modules build locally against the mainline 4.10-rc5 kernel; however, the OBS builds continue to fail! The result is that the fixes for at least four CVE vulnerabilities have not been added to TW, To be able to troubleshoot this problem, I would like to force osc to use the kernel that fails rather than the regular Factory/TW kernel. What options should I use with the "osc build" command to accomplish this? Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, 27 January 2017 11:05 Larry Finger wrote:
Since kernel 4.10-rc2 was released, the VirtualBox modules have failed to build with the KOTD packages. The message is something like "Package Virtualization/virtualbox failed to build in Kernel_HEAD_standard/x86_64". The problem is due to a kernel API change in get_pages_remote(). Oracle has fixed this problem with VB 5.1.14, and the modules build locally against the mainline 4.10-rc5 kernel; however, the OBS builds continue to fail! The result is that the fixes for at least four CVE vulnerabilities have not been added to TW,
To be able to troubleshoot this problem, I would like to force osc to use the kernel that fails rather than the regular Factory/TW kernel. What options should I use with the "osc build" command to accomplish this?
You should be able to pass repository name as an argument, i.e. osc build ... Kernel_HEAD_standard Just don't forget to clean the buildroot if you did build against a different one before. Michal Kubecek -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On vendredi, 27 janvier 2017 18.17:29 h CET Michal Kubecek wrote:
On Friday, 27 January 2017 11:05 Larry Finger wrote:
Since kernel 4.10-rc2 was released, the VirtualBox modules have failed to build with the KOTD packages. The message is something like "Package Virtualization/virtualbox failed to build in Kernel_HEAD_standard/x86_64". The problem is due to a kernel API change in get_pages_remote(). Oracle has fixed this problem with VB 5.1.14, and the modules build locally against the mainline 4.10-rc5 kernel; however, the OBS builds continue to fail! The result is that the fixes for at least four CVE vulnerabilities have not been added to TW,
To be able to troubleshoot this problem, I would like to force osc to use the kernel that fails rather than the regular Factory/TW kernel. What options should I use with the "osc build" command to accomplish this?
You should be able to pass repository name as an argument, i.e.
osc build ... Kernel_HEAD_standard
Just don't forget to clean the buildroot if you did build against a different one before.
Michal Kubecek
build clean is translasted by osc build --clean Kernel_HEAD_standard Larry, don't forget to keep us informed if you face any difficulties. Thanks again for your hard work on this piece of software. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/27/2017 12:29 PM, Bruno Friedmann wrote:
On vendredi, 27 janvier 2017 18.17:29 h CET Michal Kubecek wrote:
On Friday, 27 January 2017 11:05 Larry Finger wrote:
Since kernel 4.10-rc2 was released, the VirtualBox modules have failed to build with the KOTD packages. The message is something like "Package Virtualization/virtualbox failed to build in Kernel_HEAD_standard/x86_64". The problem is due to a kernel API change in get_pages_remote(). Oracle has fixed this problem with VB 5.1.14, and the modules build locally against the mainline 4.10-rc5 kernel; however, the OBS builds continue to fail! The result is that the fixes for at least four CVE vulnerabilities have not been added to TW,
To be able to troubleshoot this problem, I would like to force osc to use the kernel that fails rather than the regular Factory/TW kernel. What options should I use with the "osc build" command to accomplish this?
You should be able to pass repository name as an argument, i.e.
osc build ... Kernel_HEAD_standard
Just don't forget to clean the buildroot if you did build against a different one before.
Michal Kubecek
build clean is translasted by osc build --clean Kernel_HEAD_standard
Larry, don't forget to keep us informed if you face any difficulties. Thanks again for your hard work on this piece of software.
Thanks to Bruno and Michal, I was able to fix the problems with the build. Factory/TW should be updated soon. Larry -- If I was stranded on an island and the only way to get off the island was to make a pretty UI, I’d die there. Linus Torvalds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Bruno Friedmann -
Larry Finger -
Michal Kubecek