Weblog entry #12 for e5z8652
See all weblog entries made by e5z8652.
#12
Virtualbox modules are somebody else's problem
Posted by e5z8652 on Mon 8 Dec 2008 at 18:05
Somebody Else's Problem.
I love to hear that.
<cut>
I use the Virtualbox-ose packages in Lenny.
The packages are for version 1.6.6. I download the module source package, also version 1.6.6, and build the modules with module-assistant.
Everything works. I'm happy.
And then I do a dist-upgrade, as I did this morning, and apt insists on downloading and installing the pre-built modules for version 1.6.2:
Preparing to replace virtualbox-ose-modules-2.6.26-1-amd64 1.6.6-dfsg-3+2.6.26-11 (using .../virtualbox-ose-modules-2.6.26-1-amd64_2.6.26+1.6.2-dfsg-4_amd64.deb) ...
Unpacking replacement virtualbox-ose-modules-2.6.26-1-amd64 ...
1.6.2 modules do not play nice with 1.6.6 binaries. And it does this even after I purge the pre-built 1.6.2 packages. It does this on multiple machines in different environments.
I've run across this before, and have filed bug 505592.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505592
Now I admit that I'm not completely familiar with Debian's breakdown of who is responsible for what. So I just filed a bug against a package that broke machines I use. The owner of said package apparently doesn't feel that it is a problem.
The end result?
The bug is closed with an SEP entry. Not even a comment about why the kernel module wouldn't be the same revision as the software.
Thanks! I'll be happy about that as I'm once again purging the silly pre-built package and rebuilding the working modules from source.
I love to hear that.
<cut>
I use the Virtualbox-ose packages in Lenny.
The packages are for version 1.6.6. I download the module source package, also version 1.6.6, and build the modules with module-assistant.
Everything works. I'm happy.
And then I do a dist-upgrade, as I did this morning, and apt insists on downloading and installing the pre-built modules for version 1.6.2:
Preparing to replace virtualbox-ose-modules-2.6.26-1-amd64 1.6.6-dfsg-3+2.6.26-11 (using .../virtualbox-ose-modules-2.6.26-1-amd64_2.6.26+1.6.2-dfsg-4_amd64.deb) ...
Unpacking replacement virtualbox-ose-modules-2.6.26-1-amd64 ...
1.6.2 modules do not play nice with 1.6.6 binaries. And it does this even after I purge the pre-built 1.6.2 packages. It does this on multiple machines in different environments.
I've run across this before, and have filed bug 505592.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505592
Now I admit that I'm not completely familiar with Debian's breakdown of who is responsible for what. So I just filed a bug against a package that broke machines I use. The owner of said package apparently doesn't feel that it is a problem.
The end result?
The bug is closed with an SEP entry. Not even a comment about why the kernel module wouldn't be the same revision as the software.
Thanks! I'll be happy about that as I'm once again purging the silly pre-built package and rebuilding the working modules from source.
Comments on this Entry
The bug here is actually #402811 - module-assistant versioning inconsistent with linux-modules-*-2.6
Nothing further done about it since May '08. :(
Nothing further done about it since May '08. :(
[ Parent | Reply to this comment ]
Posted by Anonymous (60.248.xx.xx) on Fri 12 Dec 2008 at 05:32
I agree - that sucks.
You can work around that by putting the virtualbox-modules packages on hold.
You can work around that by putting the virtualbox-modules packages on hold.
[ Parent | Reply to this comment ]
Which is what I did, until I hit a different bug...
--
"It's Not Magic, It's Work"
Adam
[ Parent | Reply to this comment ]