[opensuse-factory] TW snapshot of 20170324 updates kernel but does not update VirtualBox kernel modules
The subject says almost everything. After updating to this snapshot, VirtualBox will not run. What needs to be in the VirtualBox spec file to cause an automatic rebuild when the kernel changes? Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mär 27 2017, Larry Finger <Larry.Finger@lwfinger.net> wrote:
What needs to be in the VirtualBox spec file to cause an automatic rebuild when the kernel changes?
The project must be configured to use the direct or recusive rebuild strategy. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/28/2017 02:39 AM, Andreas Schwab wrote:
On Mär 27 2017, Larry Finger <Larry.Finger@lwfinger.net> wrote:
What needs to be in the VirtualBox spec file to cause an automatic rebuild when the kernel changes?
The project must be configured to use the direct or recusive rebuild strategy.
Andreas, What changes in the spec or other project files are needed to implement either of these? Googling for an answer has not been productive. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Apr 02 2017, Larry Finger <Larry.Finger@lwfinger.net> wrote:
What changes in the spec or other project files are needed to implement either of these?
The rebuild stategy is configured in the repository entry in the project meta. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-03-27 19:41 GMT+02:00 Larry Finger <Larry.Finger@lwfinger.net>:
The subject says almost everything. After updating to this snapshot, VirtualBox will not run. ...
For people needing VirtualBox (like me), can you please just drop a note if it is safe to "zypper dup" with a working VirtualBox again, please? Thanks, René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/28/2017 03:00 AM, René Krell wrote:
2017-03-27 19:41 GMT+02:00 Larry Finger <Larry.Finger@lwfinger.net>:
The subject says almost everything. After updating to this snapshot, VirtualBox will not run. ...
For people needing VirtualBox (like me), can you please just drop a note if it is safe to "zypper dup" with a working VirtualBox again, please? Thanks,
It should be OK to update now. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2017-03-28 16:58 GMT+02:00 Larry Finger <Larry.Finger@lwfinger.net>:
On 03/28/2017 03:00 AM, René Krell wrote:
2017-03-27 19:41 GMT+02:00 Larry Finger <Larry.Finger@lwfinger.net>:
The subject says almost everything. After updating to this snapshot, VirtualBox will not run. ...
For people needing VirtualBox (like me), can you please just drop a note if it is safe to "zypper dup" with a working VirtualBox again, please? Thanks,
It should be OK to update now.
Larry
I can confirm: VirtualBox is fully functional for me in 20170324, don't be afraid anybody :-) René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/28/2017 01:41 AM, Larry Finger wrote:
The subject says almost everything. After updating to this snapshot, VirtualBox will not run.
What needs to be in the VirtualBox spec file to cause an automatic rebuild when the kernel changes?
AFAICS there is no kernel source change lately, kernel packages just got rebuilt with the same source, and virtualbox's requirement is fulfilled. Can you please give more information about the error you seen? I'll trigger virtualbox a rebuild after next check-in round. Regards, Max -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/28/2017 03:45 AM, Max Lin wrote:
On 03/28/2017 01:41 AM, Larry Finger wrote:
The subject says almost everything. After updating to this snapshot, VirtualBox will not run.
What needs to be in the VirtualBox spec file to cause an automatic rebuild when the kernel changes?
AFAICS there is no kernel source change lately, kernel packages just got rebuilt with the same source, and virtualbox's requirement is fulfilled. Can you please give more information about the error you seen?
I'll trigger virtualbox a rebuild after next check-in round.
Thanks. I saw a new kernel was loaded but VB was not updated. I should have checked the version more carefully. Sorry for an unnecessary panic. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Andreas Schwab -
Larry Finger -
Max Lin -
René Krell