Bug 4396 - stop removing sdk & add virtualbox-devel and python-virtualbox subpackage
Summary: stop removing sdk & add virtualbox-devel and python-virtualbox subpackage
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: Junior_job, PATCH
Depends on:
Blocks:
 
Reported: 2012-02-03 12:54 CET by Kamil Rytarowski
Modified: 2012-03-14 21:43 CET (History)
2 users (show)

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

Attachments
patch that enables sdk build (3.31 KB, patch)
2012-02-03 12:55 CET, Kamil Rytarowski 		Details | Diff
new version of the patch (2.05 KB, patch)
2012-02-03 13:38 CET, Kamil Rytarowski 		Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Description Kamil Rytarowski 2012-02-03 12:54:10 CET 
Description of problem:
Please include virtualbox-devel and python-virtualbox into the virtualbox package
This is a missing requirement for GNS3.

Version-Release number of selected component (if applicable):
Cauldron
Comment 1 Kamil Rytarowski 2012-02-03 12:55:02 CET 
Created attachment 1487 [details]
patch that enables sdk build
Kamil Rytarowski 2012-02-03 12:55:23 CET

Assignee: bugsquad => tmb

Comment 2 Thierry Vignaud 2012-02-03 13:28:33 CET 
You should not mix different things in a patch.
Here you enable SDK but you also:
- cleaned spec (cleaning %buildroot, ...)
- altered the menu entries
- replaced mageia by %{_real_vendor}
- ...

Keywords: (none) => PATCH
CC: (none) => thierry.vignaud
Summary: please include virtualbox-devel and python-virtualbox into the virtualbox package => stop removing sdk & add virtualbox-devel and python-virtualbox subpackage

Comment 3 Kamil Rytarowski 2012-02-03 13:38:31 CET 
Created attachment 1488 [details]
new version of the patch

Attachment 1487 is obsolete: 0 => 1

Comment 4 Manuel Hiebel 2012-02-03 18:08:36 CET 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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

Comment 5 Manuel Hiebel 2012-02-03 18:09:11 CET 
oups sorry; bad script :/

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Comment 6 Kamil Rytarowski 2012-02-03 18:58:52 CET 
Don't frighten us! :)
Kamil Rytarowski 2012-02-15 03:41:10 CET

Priority: Normal => release_blocker

Thierry Vignaud 2012-02-15 07:24:52 CET

Keywords: (none) => Junior_job

Comment 7 Anne Nicolas 2012-03-14 10:19:51 CET 
Ping ?

CC: (none) => ennael1

Comment 8 Thomas Backlund 2012-03-14 21:00:03 CET 
Added in upcoming 4.1.10-1.mga2

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

Comment 9 Kamil Rytarowski 2012-03-14 21:43:08 CET 
Thank you! Hopefully everything is fine.
Note You need to log in before you can comment on or make changes to this bug.