Hi,

when purging linux-image-5.15.0-2-amd64 I got these unexpected error
messages and I'm not sure if this is an issue of src:linux' prerm script
or in dkms itself — note the two blanks after "dkms: removing:":

[…]
Removing linux-image-5.15.0-2-amd64 (5.15.5-2) ...
/etc/kernel/prerm.d/dkms:
dkms: removing:   (5.15.0-2-amd64) (x86_64)
Error! Arguments <module> and <module-version> are not specified.
Usage: remove <module>/<module-version> or
       remove -m <module>/<module-version> or
       remove -m <module> -v <module-version>
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.15.0-2-amd64
/etc/kernel/postrm.d/zz-update-grub:
[…]
Reading database ... 1878017 files and directories currently installed.)
Purging configuration files for linux-image-5.15.0-2-amd64 (5.15.5-2) ...
rmdir: failed to remove '/lib/modules/5.15.0-2-amd64': Directory not empty
dpkg: warning: while removing linux-image-5.15.0-2-amd64, directory '/lib/modules/5.15.0-2-amd64' not empty so not removed
Processing triggers for initramfs-tools (0.140) ...
[…]

Not sure about the severity either. It probably means that it leaves
files after removal, so it could be RC, but then again it seems to have
no real impact and is "presumably trivial to fix", so it could be
"minor" as well. Leaving it at the default. Feel free to adjust as you
like. :-)

HI Axel,

Thanks for reporting!

I believe this should be on the dkms side, and would be the same
as #996104. There is a pull request upstream apprently which got
merged upstream.

Regards,
Salvatore

Still present for me.

error messages are

Removing linux-image-5.16.0-1-amd64 (5.16.7-2) ...
/etc/kernel/prerm.d/dkms:
dkms: removing:   (5.16.0-1-amd64) (x86_64)
Error! Arguments <module> and <module-version> are not specified.
Usage: remove <module>/<module-version> or
       remove -m <module>/<module-version> or
       remove -m <module> -v <module-version>

so error seems to be in /etc/kernel/prerm.d/dkms

fyi: I'm force merging duplicate reports to #996104. The bug was fixed
upstream in 2.8.8, but Debian upgraded to 3.0.3 in the meantime
(bullseye never had this bug, because it only has version 2.8.4).

I assume folks tracking testing are going to have to manually downgrade
to 2.8.4, or upgrade to 3.0.3, because I think it's unlikely that there
will be a 2.8.8 release just for testing.

Bug 1006431 may have been fixed at the same time as bug 996104,
but this was not the same bug: bug 996104 was typos in the
/etc/kernel/prerm.d/dkms script, so that the

  dkms remove -m $name -v $vers -k $inst_kern -a $arch

command failed due to incorrect arguments. So what I did was to
run the correct command manually. This had the effect to remove
the installed module, but was still leaving some files there.

Or perhaps this command is expected to be run while the kernel
is still installed (it is normally run as a prerm.d script,
while I ran it after the kernel was removed).