[MIR] virtualbox
Bug #1605337 reported by
Steve Langasek
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Debian) |
New
|
Unknown
|
|||
virtualbox (Ubuntu) |
Invalid
|
Undecided
|
Matthias Klose |
Bug Description
[Availability]
Currently in multiverse. The host component has external build dependencies not in Ubuntu; the source package would need to be split to allow the guest pieces to go into main.
[Rationale]
The guest package should be pulled in for cloud images targeting the virtualbox environment (i.e. vagrant). As this is an official cloud image that's being produced, the packages should all be in main and supported.
[Security]
[Quality Assurance]
[Dependencies]
[Standards Compliance]
[Maintenance]
Package ownership TBD. It is likely this should be owned by either the Cloud team or the Server team.
Changed in virtualbox (Ubuntu): | |
status: | New → Incomplete |
Changed in virtualbox (Ubuntu): | |
assignee: | nobody → Matthias Klose (doko) |
Changed in virtualbox (Debian): | |
status: | Unknown → New |
To post a comment you must log in.
Just to make you aware, I already did the split and it is even currently waiting on trusty new queue
(the split was done because the guest packages needs to be rebuilt on top of the lts stack, but this is OT).
The question is: if you take over the maintenance, just please take it over on Debian too!
I really would like to avoid maintain a delta for such a huge and problematic package.
thanks