That's probably because of the resolution of the virtual package "virtualbox-ose-modules" done by aptitude.
If I remember correctly, there has been a similar bug already been reported before. I'm adding a bug task for aptitude.
Have you tested it using apt alone?
FYI:
$ aptitude search '~Pvirtualbox-ose-modules'
p virtualbox-ose-modules-2.6.24-5-386 - virtualbox-ose modules for linux-image-2.6.24-5-386
i virtualbox-ose-modules-2.6.24-5-generic - virtualbox-ose modules for linux-image-2.6.24-5-generic
p virtualbox-ose-modules-2.6.24-5-rt - virtualbox-ose modules for linux-image-2.6.24-5-rt
p virtualbox-ose-modules-2.6.24-5-server - virtualbox-ose modules for linux-image-2.6.24-5-server
p virtualbox-ose-modules-2.6.24-5-virtual - virtualbox-ose modules for linux-image-2.6.24-5-virtual
That's probably because of the resolution of the virtual package "virtualbox- ose-modules" done by aptitude.
If I remember correctly, there has been a similar bug already been reported before. I'm adding a bug task for aptitude.
Have you tested it using apt alone?
FYI: ose-modules' ose-modules- 2.6.24- 5-386 - virtualbox-ose modules for linux-image- 2.6.24- 5-386 ose-modules- 2.6.24- 5-generic - virtualbox-ose modules for linux-image- 2.6.24- 5-generic ose-modules- 2.6.24- 5-rt - virtualbox-ose modules for linux-image- 2.6.24- 5-rt ose-modules- 2.6.24- 5-server - virtualbox-ose modules for linux-image- 2.6.24- 5-server ose-modules- 2.6.24- 5-virtual - virtualbox-ose modules for linux-image- 2.6.24- 5-virtual
$ aptitude search '~Pvirtualbox-
p virtualbox-
i virtualbox-
p virtualbox-
p virtualbox-
p virtualbox-