Joey Hess wrote: > Andres Salomon wrote: >>> 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? > > I upgraded everything, which included switching to udev, removing > hotplug etc and pretty well broke running the system with the 2.6.8 > kernel. Then I booted to the new 2.6.15 kernel, and ran module-assistant > to build ndiswrapper modules for it, and found that it FTBFS, at which > point I was left without a wireless network to upgrade the ndiswrapper > versions to unstable.
When I added the dependency (pre-sarge), I wasn't expecting users to be forced to upgrade kernels. Unfortunately, udev and other packages have made that a requirement. :( > Well, it seems that I seem to have managed to hit every one of the > possible failure modes here. Maybe unlike real debian users I don't know > what I'm doing. > Yes, the failure mode you've hit will most likely become the common case unless the hotplug/udev stuff is fixed to work w/ older kernels (it's looking like 3.1 -> 3.2 upgrades/migrations are not going to be pretty). That raises the urgency to allow ndiswrapper-utils packages to be installed in parallel, and DTRT depending upon which ndiswrapper driver is actually in the running kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
