Attaching a graph to illustrate the dependencies. This is with version
13 of the package, which does not use virtual packages anymore, but meta
packages instead (to provide better upgrade experiences and allow side-
by-side installation)

** Summary changed:

- virtualbox installs for the wrong kernel
+ Installing virtualbox-ose-modules pulls in 386 kernel (on -generic)

** Description changed:

  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.
+ 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?

** Changed in: virtualbox-ose-modules (Ubuntu)
     Assignee: Daniel Hahler (blueyed) => (unassigned)
       Status: In Progress => Triaged

** Attachment added: "A graph of the dependencies (from virtualbox-ose-modules 
13)"
   http://launchpadlibrarian.net/12281963/vbos-ose-mods-deps.png

-- 
Installing virtualbox-ose-modules pulls in 386 kernel (on -generic)
https://bugs.launchpad.net/bugs/188579
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to