Joey Hess wrote: > Andres Salomon wrote: >> Yep, well aware of that. I've been waiting for the kernel team to do >> something about binary kernel modules in order to allow ndiswrapper to >> transition to testing (I have no interest in manually dealing w/ binary >> modules other than for a release). Unfortunately, I have no idea what >> the status of that is. >> >> Ditto for hostap stuff, but binary modules aren't holding the -source >> package back. > > Well, the existing binary modules in testing are for an old kernel and > are useless. It would be more useful to let a usable version of > ndiswrapper propigate to testing without those modules. > > Currently there is a very nasty trap for anyone upgrading a system that > relies on ndiswrapper for its networking from stable to testing. >
What nasty trap is that? The fact that the version in testing is so old? The point behind that "trap" (the dependency on ndiswrapper-modules-$MAJOR.$MINOR) is to keep people from breaking their ndiswrapper installation during an upgrade.. that is, dist-upgrade grabbing ndiswrapper-utils without caring what ndiswrapper-modules package is installed. ndiswrapper-utils specifically checks that the module in the kernel is the same version, and breaks otherwise. People upgrading from stable to testing shouldn't automatically get their kernel upgraded unless they're using some of the kernel-latest metapackages, and even then will have the older kernel installed. So, I'm making a trade-off: - reboot into an older kernel or grab ndiswrapper-source from unstable and rebuild vs. - upgrade ndiswrapper-utils and not be able to use ndiswrapper w/ the old *or* new kernel without rebuilding (and there's no guarantee the rebuild will work). The whole situation is rather messy and painful; if you have ideas for a better solution, I'm all ears. I have considered doing something similar to what did for lvm (lvm-common picking between lvm9, lvm10, lvm2, etc), but I haven't gotten around to implement such a beast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
