[Pkg-virtualbox-devel] Bug#454348: This won't fix makes a hold necessary and use of older virtualbox-ose-source

[Dennis Eckhaus]

I don't understand the statement that a user isn't supposed to be 
rebuilding the source.  I only understand that the way to install the 
virtualbox kernel module is to do so with module assistant

Module Assistant will only build with the prior Lenny module (I use 
Lenny), and not the current Lenny module that aptitude will upgrade to 
if allowed, this because of the renaming of the source package.  Module 
Assistant will not find the package if it is the new one.  But it will 
download and install the older one if the m-a a-i process is used.  
That'll work, but if one accepts the offered upgrade by aptitude there 
is no way to use Virtualbox as then there is no kernel module installed.

The same situation has just occurred with the latest NVidia 169.07 Sid 
driver.  Since the nvidia-kernel-source package contains a different 
naming scheme that module assistant doesn't recognize, it is impossible 
to install the latest NVidia driver (well, unless using the downloaded 
script from upstream, which is what I did).

It is nice that the new upgraded source packages are being named based 
upon the future naming scheme that module assistant will use with the 
2.6.23 kernels, but what do we do until we get 2.6.23 in Lenny?  At 
least module assistant can get the older source for virtualbox, which it 
cannot get for NVidia.  I just put a hold on the virtualbox-ose-source 
package so it won't upgrade.  But that means of course, that I do not 
get whatever benefits that the newer kernel module would contain.

Are you sure this should be a won't fix?

Dennis Eckhaus
eckhaus1 at comcast.net