Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #94205 > unrolled thread

Bug#1148823: linux-binary-7.2.6+deb14-amd64: The vmlinuz-7.2.6+deb14-amd64 file is not owned by any package

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1148823: linux-binary-7.2.6+deb14-amd64: The vmlinuz-7.2.6+deb14-amd64 file is not owned by any package Salvatore Bonaccorso <carnil@debian.org> - 2026-09-24 10:40 +0200
    Bug#1148823: linux-binary-7.2.6+deb14-amd64: The vmlinuz-7.2.6+deb14-amd64 file is not owned by any package Thomas Nemeth <tnemeth@free.fr> - 2026-09-24 10:50 +0200
      Bug#1148823: linux-binary-7.2.6+deb14-amd64: The vmlinuz-7.2.6+deb14-amd64 file is not owned by any package Salvatore Bonaccorso <carnil@debian.org> - 2026-09-24 11:50 +0200
        Bug#1148823: linux-binary-7.2.6+deb14-amd64: The vmlinuz-7.2.6+deb14-amd64 file is not owned by any package Thomas Nemeth <tnemeth@free.fr> - 2026-09-24 12:10 +0200

#94205 — Bug#1148823: linux-binary-7.2.6+deb14-amd64: The vmlinuz-7.2.6+deb14-amd64 file is not owned by any package

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: debian-amd64@lists.debian.org
> User: debian-amd64@lists.debian.org
> 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

[toc] | [next] | [standalone]

#94206

[Multipart message — attachments visible in raw view] — view raw

Le jeudi 24 septembre 2026, 10:36 Salvatore Bonaccorso a écrit :
> HI Thomas,

    Hi Salvatore !


> 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).

    Ok. I wasn't aware...
    So instead of checking for the kernel file in /boot I just have to
    check /usr/lib/modules/$(uname -r)/vmlinuz. Will an apt-get purge
    of the matching package(s) also remove the /boot kernel ?

Regards,

Thomas.

[toc] | [prev] | [next] | [standalone]

#94207

Hi Thomas,

On Thu, Sep 24, 2026 at 10:46:21AM +0200, Thomas Nemeth wrote:
> Le jeudi 24 septembre 2026, 10:36 Salvatore Bonaccorso a écrit :
> > HI Thomas,
> 
>     Hi Salvatore !
> 
> 
> > 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).
> 
>     Ok. I wasn't aware...
>     So instead of checking for the kernel file in /boot I just have to
>     check /usr/lib/modules/$(uname -r)/vmlinuz. Will an apt-get purge
>     of the matching package(s) also remove the /boot kernel ?


Yes on removal of the linux-image pacakge, in the prerm script the
linux-run-hooks are called with the prerm argument, and they do remove
then the installed image in /boot/vmlinuz-${version} (check the
/usr/share/kernel/prerm.d/zz-legacy-boot hook script.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#94208

[Multipart message — attachments visible in raw view] — view raw

Le jeudi 24 septembre 2026, 11:38 Salvatore Bonaccorso a écrit :
> Yes on removal of the linux-image pacakge, in the prerm script the
> linux-run-hooks are called with the prerm argument, and they do remove
> then the installed image in /boot/vmlinuz-${version} (check the
> /usr/share/kernel/prerm.d/zz-legacy-boot hook script.

    Thanks a lot !

    I think we can close the issue.


Regards,

Thomas.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web