DKMS build fails, but package upgrade still successful
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkms (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Unassigned | ||
nvidia-graphics-drivers-180 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Karmic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
The nvidia-
I believe the package should not be marked as configured in this case, especially as otherwise the user will notice the problem only on the next boot.
Example failure case (due to DKMS bug #438393):
-----------------
Configuring: nvidia-
Removing all DKMS Modules
Done.
Adding Module to DKMS build system
driver version= 185.18.36
Doing initial module build
Error! Bad return status for module build on kernel: 2.6.31-11-generic (i686)
Consult the make.log in the build directory
/var/lib/
Installing initial module
Error! Could not locate nvidia.ko for module nvidia in the DKMS tree.
You must run a dkms build for kernel 2.6.31-11-generic (i686) first.
Done.
-----------------
Extract from make.log
-----------------
DKMS make.log for nvidia-185.18.36 for kernel 2.6.31-11-generic (i686)
ti 29.9.2009 00.03.29 +0300
The C compiler '/home/
create executables. Please make sure you have
your Linux distribution's libc development package
installed and that '/home/
name.
*** Failed CC sanity check. Bailing out! ***
make: *** [select_makefile] Virhe 1
-----------------
Changed in nvidia-graphics-drivers-180 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Interesting, you're right that in such a case the package upgrade should not be marked as succeeding. This may be exacerbating the situation when the package fails to build for other reasons.