> There should be a way to tell dkms not to build a module for kernels > newer than $FOO, or (maybe preferably) at least make the failure > non-fatal so that the package still installs fine but issues a warning > that the build failed for some kernel(s).
A dkms variable that contains the last kernel version that the module in known to work with would be great. If a build fails with a kernel version that is > that variable, dkms could display a warning that the kernel is not supported and not run the apport hook. > I don't see why you would ever want the package to install though > if it's not going to work with your kernel. I agree that the user should know that module X failed to build with kernel Y, but doing that by failing the package installation is a bad idea. You have false-positives because a user might have a kernel installed that he doesn't use (anymore). You don't catch a lot of cases: - module build fails with a kernel that has been isntalled after the *-dkms package - the header files aren't installed Using OBSOLETE_BY is just a hack to prevent package installation failures. You still end up having a kernel without the module. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735505 Title: RFC: add a mechanism to disable building a module for known bad kernels -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
