Overview
Request 806055 accepted
- Version bump to 6.0.22 (released May 15 2020 by Oracle)
This is a maintenance release. The following items were fixed and/or added:
Guest Additions: Build problems fix with Oracle Linux 8.2 (Red Hat compatible kernel) / Red Hat Enterprise Linux 8.2 / CentOS 8.2 (bug #19391)
Guest Control/VBoxManage: fix handling of multiple environment variables supplied to 'VBoxManage guestcontrol VM run' (6.1.6/6.0.20 regression; bug #19518)
- Created by lwfinger
- In state accepted
-
Open review for
licensedigger
Request History
lwfinger created request
- Version bump to 6.0.22 (released May 15 2020 by Oracle)
This is a maintenance release. The following items were fixed and/or added:
Guest Additions: Build problems fix with Oracle Linux 8.2 (Red Hat compatible kernel) / Red Hat Enterprise Linux 8.2 / CentOS 8.2 (bug #19391)
Guest Control/VBoxManage: fix handling of multiple environment variables supplied to 'VBoxManage guestcontrol VM run' (6.1.6/6.0.20 regression; bug #19518)
maintbot accepted review
ok
factory-auto accepted review
Check script succeeded
msmeissn accepted request
ok
This comment has been deleted
VB on Leap 15.1 will NEVER be changed to match Factory. When I took the maintainer position, I was told that it was my option to keep an old VB series for old releases, even though I changed the series for the current release. That is the policy that I chose, and continue to use. Accordingly, Leap 15.2 will use VB from the 6.0.x releases, but 15.1 will stay with 6.0.x.
If this policy is no longer acceptable, I am more than willing to turn the VB maintainership over to someone new.
home:lwfinger:branches:openSUSE:Leap:15.1:Update/virtualbox@58277e7bb986209363d3f7eb82b54f70 -> openSUSE:Leap:15.1:Update/virtualbox
expected origin is 'openSUSE:Factory' (changed)
I tried to submit VB 6.1.10 from Factory to Leap:15.1:Update, and it was rejected because "the Maintenance Request method" had to be used. I do not know how to get an update from Factory to Leap:15.1:Update!