Bug 2493 - Backport Request: virtualbox package
Summary: Backport Request: virtualbox package
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Backport
Depends on:
Blocks:
 
Reported: 2011-08-22 19:55 CEST by Stefano Negro
Modified: 2012-02-27 21:41 CET (History)
1 user (show)

See Also:
Source RPM: virtualbox
CVE:
Status comment:


Attachments

Description Stefano Negro 2011-08-22 19:55:59 CEST
Description of problem:
old version of virtualbox in Mageia 1. 
Now the most updated available version is 4.1.2 in the website www.virtualbox.org   , in Mageia 1 is 4.0.6.
In Cauldron there is the 4.1.2 and could be pushed in update.

Version-Release number of selected component (if applicable):
4.0.8


How reproducible:
rpm -qa virtualbox


Steps to Reproduce:
1.
2.
3.
Comment 1 Manuel Hiebel 2011-08-22 20:00:20 CEST
I change the summary for the update see bug 1940

Summary: Update of virtualbox package => Backport of virtualbox package

Manuel Hiebel 2011-09-02 21:31:00 CEST

Source RPM: (none) => virtualbox

Manuel Hiebel 2011-09-08 22:07:52 CEST

Summary: Backport of virtualbox package => Backport Request: virtualbox package
Whiteboard: (none) => Backport

Samuel Verschelde 2011-09-13 13:04:10 CEST

Keywords: (none) => Backport
Whiteboard: Backport => (none)

Comment 2 Marja Van Waes 2011-11-25 21:16:22 CET
Since a month ago Mga 1 has virtualbox-4.0.14-1.3.mga1
(in updates, we don't have backports, yet)

@ Stefano

Is that good enough for you, in other words: do you agree on closing this request?

CC: (none) => marja11

Marja Van Waes 2012-01-22 18:04:54 CET

Severity: normal => enhancement

Comment 3 Marja Van Waes 2012-02-27 21:41:07 CET
(In reply to comment #2)
> Since a month ago Mga 1 has virtualbox-4.0.14-1.3.mga1
> (in updates, we don't have backports, yet)
> 
> @ Stefano
> 
> Is that good enough for you, in other words: do you agree on closing this
> request?

You didn't reply, so I think you agree this is good enough.

Feel free to reopen if I misunderstood

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


Note You need to log in before you can comment on or make changes to this bug.