| 2008-02-03 10:52:52 |
sibidiba |
bug |
|
|
added bug |
| 2008-02-04 02:20:01 |
Daniel Hahler |
virtualbox-ose: importance |
Undecided |
High |
|
| 2008-02-04 02:20:14 |
Daniel Hahler |
bug |
|
|
assigned to aptitude (Ubuntu) |
| 2008-02-28 19:39:49 |
Daniel Hahler |
virtualbox-ose: status |
New |
Triaged |
|
| 2008-02-28 19:52:33 |
Daniel Hahler |
virtualbox-ose-modules: status |
Triaged |
In Progress |
|
| 2008-02-28 19:52:33 |
Daniel Hahler |
virtualbox-ose-modules: assignee |
|
blueyed |
|
| 2008-02-29 00:54:16 |
Daniel Hahler |
aptitude: importance |
Undecided |
Medium |
|
| 2008-02-29 00:54:16 |
Daniel Hahler |
aptitude: status |
New |
Confirmed |
|
| 2008-02-29 00:59:48 |
Daniel Hahler |
description |
Binary package hint: virtualbox-ose
On Ubuntu Hardy alpha 4:
When installing virtualbox with aptitude, it installs the -386 kernel image unnecessarily and virtualbox-ose-modules-2.6.24-5-386 instead of the -generic one. |
Binary package hint: virtualbox-ose
On Ubuntu Hardy alpha 4:
When installing virtualbox-ose with aptitude, it installs the -386 kernel image unnecessarily and virtualbox-ose-modules-2.6.24-5-386 instead of the -generic one.
virtualbox-ose-modules has been a virtual package, provided by all the different flavours of the module (-386, -generic, ..). But apt fails to find the "best path" when selecting a package: it seems to always chose the -386 one, although using the -generic one would have to pull less dependencies in (in particular the linux-image-386).
Also when using real meta packages (instead of virtual packages), the problem persist.
Is this a packaging problem with virtualbox-ose-modules or is apt missing the expected feature? Is there a way to provide better hinting? |
|
| 2008-02-29 00:59:48 |
Daniel Hahler |
title |
virtualbox installs for the wrong kernel |
Installing virtualbox-ose-modules pulls in 386 kernel (on -generic) |
|
| 2008-02-29 01:00:03 |
Daniel Hahler |
virtualbox-ose-modules: status |
In Progress |
Triaged |
|
| 2008-02-29 01:00:03 |
Daniel Hahler |
virtualbox-ose-modules: assignee |
blueyed |
|
|
| 2008-02-29 01:02:52 |
Daniel Hahler |
bug |
|
|
added attachment 'vbos-ose-mods-deps.png' (A graph of the dependencies (from virtualbox-ose-modules 13)) |
| 2008-02-29 01:10:04 |
Daniel Hahler |
description |
Binary package hint: virtualbox-ose
On Ubuntu Hardy alpha 4:
When installing virtualbox-ose with aptitude, it installs the -386 kernel image unnecessarily and virtualbox-ose-modules-2.6.24-5-386 instead of the -generic one.
virtualbox-ose-modules has been a virtual package, provided by all the different flavours of the module (-386, -generic, ..). But apt fails to find the "best path" when selecting a package: it seems to always chose the -386 one, although using the -generic one would have to pull less dependencies in (in particular the linux-image-386).
Also when using real meta packages (instead of virtual packages), the problem persist.
Is this a packaging problem with virtualbox-ose-modules or is apt missing the expected feature? Is there a way to provide better hinting? |
Binary package hint: virtualbox-ose
On Ubuntu Hardy alpha 4:
When installing virtualbox-ose with aptitude, it installs the -386 kernel image unnecessarily and virtualbox-ose-modules-2.6.24-5-386 instead of the -generic one.
virtualbox-ose-modules has been a virtual package, provided by all the different flavours of the module (-386, -generic, ..). But apt fails to find the "best path" when selecting a package: it seems to always chose the -386 one, although using the -generic one would have to pull less dependencies in (in particular the linux-image-386).
Also when using real meta packages (instead of virtual packages), the problem persist.
Is this a packaging problem with virtualbox-ose-modules or is apt missing the expected feature? Is there a way to provide better hinting?
WORKAROUND: Install the virtualbox-ose-modules-$flavor package manually, e.g.:
$ sudo apt-get install virtualbox-ose-modules-generic virtualbox-ose
(AppArmor seems to be affected by a similar/the same issue, see bug 148586) |
|
| 2008-03-14 09:25:48 |
Launchpad Janitor |
virtualbox-ose-modules: status |
Triaged |
Fix Released |
|
| 2008-03-17 22:36:58 |
Daniel Hahler |
virtualbox-ose-modules: status |
Fix Released |
Triaged |
|
| 2008-03-17 23:27:34 |
Daniel Hahler |
apt: status |
Confirmed |
Triaged |
|
| 2008-03-20 01:25:17 |
Daniel Hahler |
bug |
|
|
assigned to apt (Debian) |
| 2008-03-20 01:32:25 |
Daniel Hahler |
virtualbox-ose-modules: status |
Triaged |
In Progress |
|
| 2008-03-20 01:32:25 |
Daniel Hahler |
virtualbox-ose-modules: assignee |
|
blueyed |
|
| 2008-03-20 12:21:06 |
Bug Watch Updater |
apt: status |
Unknown |
New |
|
| 2008-03-21 17:33:54 |
Daniel Hahler |
virtualbox-ose-modules: status |
In Progress |
Fix Released |
|
| 2009-07-22 01:10:30 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/virtualbox-ose |
|
| 2009-07-22 07:23:38 |
Igor Zubarev |
removed subscriber Igor Zubarev |
|
|
|
| 2009-08-08 04:50:23 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/hardy-updates/virtualbox-ose-modules |
|
