Bug#928352: nvidia-kernel-dkms: dkms did not automatically rebuild nvidia module for newly installed kernel

[Guillaume Raffy]

On Fri, 3 May 2019 01:22:37 +0200 Andreas Beckmann <anbe at debian.org> wrote:
 > On 2019-05-02 18:41, guillaume raffy wrote:
 > > Indeed, on our server, "linux-headers-4.9.0-8-all-amd64" was 
installed but not "linux-headers-amd64". I believe that if the package 
"linux-headers-amd64" was installed in the first place, then aptitude 
full-upgrade would have brought "linux-headers-4.9.0-9-all-amd64" along 
with the kernel, and the rebuild of the nvidia module would have then 
succeeded. But that's merely an hypothesis, as I'm not an expert.
 >
 > Exactly, if the linux-headers-amd64 metapackage had been installed,
 > everything would have worked as expected.
 > Since it it out of our realm to guess which kernel you want to run (and
 > therefore which kernel headers you need), I'm closing this bug.
 >
 > But feel free to point us to the places in the documentation where you
 > would have expected to find this information.
 >
 > The description of the nvidia-kernel-dkms package currently contains:
 > ...
 > Provided that you have the kernel header packages installed, the kernel
 > module will be built for your running kernel and automatically 
rebuilt for
 > any new kernel headers that are installed.
 > ...
 >
 > The dkms package itself has
 > Recommends: fakeroot, sudo, linux-headers-686-pae | linux-headers-amd64
 > | linux-headers-generic | linux-headers, lsb-release
 >
 >

 > Andreas

Hi Andreas,

Thank you very much for your clear answer. It helped me realize that the 
problem comes from the fact that we tweaked Debian's default settings 
(for some yet unknown reason, our configuration system had set 
Install-Recommends to false). This problem wouldn't happen for a basic 
user, which is good!

Thanks again and sorry for the trouble.

Guillaume