Bug 26840

Summary:	Please update VirtualBox to 6.1.10 on Mageia 7
Product:	Mageia	Reporter:	Chris B <shybluenight>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	fri
Version:	7
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	virtualbox	CVE:
Status comment:

Description Chris B 2020-06-21 13:29:45 CEST

This is a request to update VirtualBox for Mageia 7 to the stable version 6.1.10.

Needed by the qa-team to test MGA8 flavours and applications. 
M8 has already the most recent version.
We should have the same versions on the host and the guest.
For M8 beta's and the final, reviewers and testers and new users most likely will use 6.1.10 as their host.

Comment 1 David Walser 2020-06-21 15:09:57 CEST

Actually they don't need to be the same version, and it would be fine for Mageia 7 to stay on the 6.0.x branch while Mageia 8 is on 6.1.x (and not unusual generally speaking).  Unfortunately we recently lost our maintainer for this package too, so hopefully someone will step forth for future updates, but 6.0.22 doesn't look too important right now.

Severity: normal => enhancement
Source RPM: virtualbox 6.0.20 => virtualbox

Comment 2 Chris B 2020-06-21 15:45:17 CEST

For proper testing we do need the 6.1.10 version on our host which is for many Mageia 7, M8 should work and being tested on a 6.1.10 host. A lot has changed.
I did not asked for 6.0.22.

Sad to hear that Virtual Box is now unmaintained.

Morgan Leijström 2020-06-22 02:07:58 CEST

CC: (none) => fri

Comment 3 Lewis Smith 2020-07-16 22:11:58 CEST

Jumping in late, ignorant of VB.
I wonder why it so matters that an M7 host to an M8 guest needs to be the same version. What matters is that it works. To test VB 6.1.10 host, necessary, this can be done on an M8 system. It is already stable enough for that, I think.
See also bug 26868.

> A lot has changed
Chris, did you mean in VirtualBox or Mageia?

This bug is a legitimate request, currently difficult to honour. In the current circumstances, assigning this globally.

Assignee: bugsquad => pkg-bugs

Comment 4 Thomas Backlund 2020-07-16 22:28:09 CEST

Just happend to see this.... my 2 cents...

The better option this time around imho would be to add 6.1 branch to backports, not updates...

One big change from 6.0 to 6.1 branch is dropping 32bit host support, so it would cause a regression in a stable Mageia release... something "we" usually have tried to avoid...

Comment 5 Chris B 2020-07-16 23:03:42 CEST

Thanks, Thomas.
Yes, that is one change.
Another one are the settings of the graphics controller.

@Lewis - I'm trying again to explain what this is about.
It is not that we -as qa team- are unable to test M8 internally with the existing Vbox 6.0.20. It works fine with this version.

This is about making sure that M8 will work as a guest on a Vbox 6.1.10 or 6.1.12 host, because that is what people will be using on their host when the final release of M8 is out in the wild.

There is only one tester on the qa team with M8 as host, who is using VirtualBox.
For example, I'm unable to run Cauldron/M8 on real hardware, I have limited resources.

Comment 6 David Walser 2020-07-17 00:55:24 CEST

Thanks for the clarification Chris.  Obviously as we near Mageia 8, people are going to have to test it on real hardware, so they can test virtualbox too.

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED