[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#979426: marked as done (missing linux-headers-amd64 prevents running dkms when kernel is updated in debian/contrib-testing64)

Your message dated Thu, 11 Feb 2021 18:34:20 +0100
with message-id <f4dfe9d4-7c0c-9d95-403e-e58fea98cea0@libera.cc>
and subject line 
has caused the Debian Bug report #979426,
regarding missing linux-headers-amd64 prevents running dkms when kernel is updated in debian/contrib-testing64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
979426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979426
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cloud.debian.org
Severity: normal

While upgrading the current debian/current-testing64 (half of 2020) under virtualbox provider:

[...]
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.9.0-5-amd64:Error! Your kernel headers for kernel 5.9.0-5-amd64 cannot be found.
Please install the linux-headers-5.9.0-5-amd64 package,
or use the --kernelsourcedir option to tell DKMS where it's located
[...]

That's due to 5.6 -> 5.9 migration and missing of linux-headers-amd64 package apparently.

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
the latest testing64 released box should fix this issue

--- End Message ---
Reply to: