The linux-modules-*-2.6 packages build kernel modules with version
numbers of the form kernelver-modulever (e.g. 2.6.18+1.3.0~pre9-2) while
module-assistant builds kernel modules with version numbers of the form
modulever-kernelver 1.3.0~pre9-3+2.6.18-6. This makes debian-generated
kernel module versions override locally installed versions.
It appears from the bug reports that linux-modules-extra-2.6 has the
correct behavior, in the presence of a ~ in module version numbers. (See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402811#41)
Furthermore, it seems to me that modules generated using
module-assistant should be one epoch above those generated from
linux-modules-extra-2.6 so that if I used module-assistant to generate a
patched version of a module, that patched version doesn't get
overwritten on the next upload of linux-modules-extra-2.6. I did such a
local patch just a couple days ago for gspca to add a device ID to the
module, so this is a useful concern.
That is to say:
linux-modules-*-2.6 should use version number 2.6.18+1.3.0~pre9-2
and module-assistant should use versinon number 1:2.6.18+1.3.0~pre9-2
--Ken
--
Ken (Chanoch) Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu/~kbloom1/
Bug#402811: module-assistant versioning inconsistent with linux-modules-*-2.6
