(Adding original submitter to the loop.) Ben Hutchings <ben@decadent.org.uk> (2013-11-16): > On Fri, 2013-11-15 at 21:50 +0400, Алексей Шилин wrote: > > I confirm this. > > > > Looks like the reason for having wrong kernel headers installed is the following dependencies chain: > > * virtualbox-ose-guest-x11 depends on virtualbox-guest-x11; > > * virtualbox-guest-x11 depends on virtualbox-guest-utils; > > * virtualbox-guest-utils recommends virtualbox-guest-dkms; > > * virtualbox-guest-dkms depends on dkms; > > * dkms recommends linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers. > > > > VirtualBox doesn't enable PAE/NX by default, > > That seems like a bug in VirtualBox. > > > so the installer chooses the 486 kernel for installation; however, > > when requesting virtualbox-ose-guest-x11 installation, no kernel > > headers package is explicitly requested by the installer, so APT > > chooses the default one, which is the first one in the dependencies > > list, namely linux-headers-686-pae. > > > > I guess, this can be fixed by explicitly requesting the kernel > > headers package, matching the kernel installed. > > Right. Recommendation of linux-headers packages is never going to > work for all cases. I'm not sure how to deal with this. Probably by reassigning this bug report to discover (and/or discover-data), so that it installs the relevant linux-headers package when it detects virtualbox-ose-guest-x11 is needed; to achieve this, maybe a specific package (something like linux-headers-@@whatever@@) could be specified together with that one, so that this mechanism can be reused for non-virtualbox, yet needing linux-headers-*, packages. Cc-ing discover maintainers for advice. Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature