Bug#988475: openrazer-driver-dkms: package removes essential files from linux-header package

[Thanatermesis]

Package: openrazer-driver-dkms
Version: 2.4.0+dfsg-1
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Installing this package causes files from the linux-header package to be
removed, this is imho a very important issue affecting the rest of the
OS

I noticed by installing the openrazer-driver-dkms package and then
noticing that other modules doesn't compile, after a long research I
found that the cause was this package the one that deletes essential
files, more exactly this one:

    /usr/src/linux-headers-5.10.0-0.bpo.5-amd64/include/generated/autoconf.h

Using another kernel (5.9) happens the same thing

There's a piece of the LOG generated by the emodule where we can see how
it removes the files:

$ cat /var/lib/dkms/openrazer-driver/2.4.0/build/make.log
DKMS make.log for openrazer-driver-2.4.0 for kernel 5.10.0-0.bpo.5-amd64 (x86_64)
Thu May 13 17:40:05 UTC 2021
- -e
:: Compiling OpenRazer kernel modules
========================================
make -C /lib/modules/5.10.0-0.bpo.5-amd64/build SUBDIRS=/var/lib/dkms/openrazer-driver/2.4.0/build/driver modules
make[1]: Entering directory '/usr/src/linux-headers-5.10.0-0.bpo.5-amd64'
  SYNC    include/config/auto.conf.cmd
sh: 0: Can't open /usr/src/linux-headers-5.10.0-0.bpo.5-common/scripts/mkmakefile
make[3]: *** [/usr/src/linux-headers-5.10.0-0.bpo.5-common/Makefile:548: outputmakefile] Error 127
/usr/src/linux-headers-5.10.0-0.bpo.5-common/Makefile:687: include/config/auto.conf.cmd: No such file or directory
make[2]: *** [/usr/src/linux-headers-5.10.0-0.bpo.5-common/Makefile:709: include/config/auto.conf.cmd] Error 2
make[2]: *** [include/config/auto.conf.cmd] Deleting file 'include/generated/autoconf.h'
make[1]: *** [/usr/src/linux-headers-5.10.0-0.bpo.5-common/Makefile:185: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-0.bpo.5-amd64'
make: *** [Makefile:25: driver] Error 2
$

The only way to make the system able to compile other modules is by
reinstalling the header files


Thank you,
Thanatermesis



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

Kernel: Linux 5.10.0-0.bpo.5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openrazer-driver-dkms depends on:
ii  dkms  2.8.4-3~bpo10+1
ii  udev  241-7~deb10u7

openrazer-driver-dkms recommends no packages.

openrazer-driver-dkms suggests no packages.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEfeKOpqCfdgmEOvbZoseZv9/418IFAmCdZ2gACgkQoseZv9/4
18KqgA/9FEtX1czWlG802hvzfzaE8P1svwWzIoVfLjDEaafOyygEMwM/3KWETP8p
/EU+d59XkOFjgFbZ/i21RHh6GwXidRdVX8oG9tk0qg0Vbify00PsKBHMWxLtHu5u
aLawx3bJryXV+E/kD/BpxBQsz6d1jdJZt0EWTht7ey/Ts0cH5v/AWXcexBa+lLgx
H/xl74UZutNtT3tWvVy4rd4pJonbdf1aQbB9zUWxmrbSYi9vEUSpXzGwK/dzLJoD
+OCysy4jiImDnP6vV9WgVNCxhAH49dHDfr6kP0aK0ZSXPIBQA+HYkp+SSIKpKhCO
MrDt0TUgebASQw5LLz9v+uA4pZUnpPTIDFgBEQ3SX6fjvGHkh8ryLbHOy640mf7u
5sVT/ArMwK7YrjoBbtMqFA6PAvOuE8QhYrocMEB3KjJEnDRoqmJqfwvkDFDVHzLv
x3G9nr6KXMCaffQhoYsnmyTwS0zEewzGp+wkdcUNfJ7VitckkTLSZqe4w2FB1Dja
+kO8pI7UtIrEL//Gh72aobzot0pS6tPGJ6A6XbMZtKOkdK6V/LdY/rg2wcAYmnTD
dfT+sgrOrY5qfZLHTFqEULJXlMp78kBXjA29yrl2cLWN4kFruMEOtW1Rqh1Z+CCV
NXwqGC4y9YBWDPzTnrn0MU9/VPdBIEJ3dOyK1B1gVFzINHvMy34=
=Kl+U
-----END PGP SIGNATURE-----

[Thanatermesis]

Note 1: Seems like this happens with the new kernels from backports but not the one provided by the default distro

Note 2: The issue happens also with the package  'ddcci-dkms', so im not sure how much is related to the dkms package(s) or with the new kernels from backports?

[Chris Hofstaedtler]

* Thanatermesis <thanat...@gmail.com> [210514 17:49]:

This is caused by a Linux kernel build system change, since Linux
5.something. *All* dkms packages in stable will show this issue when
used with a newer kernel (i.e. from backports).

There is very little to be done in old dkms packages - either use
everything from testing/backports, or everything from stable.

Given bullseye will be out soon, temporarily upgrading to testing
might also be an option if you need the newer kernel.

HTH,
Chris