HI Thomas, On Thu, Sep 24, 2026 at 08:10:36AM +0200, Thomas wrote: > Package: src:linux > Version: 7.2.6-1 > Severity: normal > X-Debbugs-Cc: [email protected] > User: [email protected] > Usertags: amd64 > > > Hi ! > > For (tenth of) years, I had the habit of cleaning up my older kernels > after a few days of use with the new one every time a new kernel > package appear in testing. In order to ensure removing the right > package I check which package installed the current kernel to avoid > removing it. > > Something along the line of : > > dpkg -S /boot/vmlinux-$(uname -r) > > I worked perfectly until today. I still have the previous kernel > installed so : > > ```bash > $ cd /boot > $ ls -1 vm* > vmlinuz-7.1.13+deb14-amd64 > vmlinuz-7.2.6+deb14-amd64 > $ dpkg -S vmlinuz-7.1.13+deb14-amd64 > linux-binary-7.1.13+deb14-amd64: /boot/vmlinuz-7.1.13+deb14-amd64 > ``` > > As you can see, `dpkg -S` gives the package name for the kernel. > However : > > ``` > $ dpkg -S vmlinuz-7.2.6+deb14-amd64 > dpkg-query: no path found matching pattern *vmlinuz-7.2.6+deb14-amd64* > $ uname -r > 7.2.6+deb14-amd64 > $ dpkg -S vmlinuz-$(uname -r) > dpkg-query: no path found matching pattern *vmlinuz-7.2.6+deb14-amd64* > ``` > > Is there a packaging problem ?
This is in fact was an intentional made change as per https://salsa.debian.org/kernel-team/linux/-/merge_requests/1892 and https://salsa.debian.org/kernel-team/linux-base/-/merge_requests/21 (together with some more additional followup fixes, e.g. to correctly copy as well the config to /boot). Regards, Salvatore
