Your message dated Sun, 1 Nov 2026 00:13:04 +0100
with message-id <[email protected]>
and subject line Re: Bug#1152742: unsigned kernel images built with the new
pkg.linux.unsigned are not copied to /boot
has caused the Debian Bug report #1152742,
regarding unsigned kernel images built with the new pkg.linux.unsigned are not
copied to /boot
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 [email protected]
immediately.)
--
1152742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1152742
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: linux
Version: 7.3
Severity: normal
X-Debbugs-Cc: Bastian Blank <[email protected]>, [email protected]
I've just used the new `pkg.linux.unsigned` profile to build myself a 7.3.1 and
it worked almost fine: the only problem was that after installing the built
packages, the image was not copied from `/usr/lib/modules/${kernelRelease}/` to
`/boot/` and as a consequence `update-grub` did not add it to my Grub menu.
I'm guessing that the reason is that post-install scripts expect image files in
`/usr/lib/modules/${kernelRelease}/` to be named `vmlinuz`, while when using
this profile, it is named `vmlinuz.unsigned`.
My simple workaround is to manually copy the image to
`/boot/vmlinuz-${kernelRelease}` and rerun `update-grub`.
I use `linux-base` version 4.17~bpo13+1.
Best regards!
-- System Information:
Debian Release: 13.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 7.3.1+morgwai2.1-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
I've just noticed the fix in `linux-base`
(https://salsa.debian.org/kernel-team/linux-base/-/commit/4a78cb93b7f60a72b5b9616997d713d7de4afe9e
).
Apologies for the unnecessary noise.
On 31/10/2026 23:35, Piotr Morgwai Kotarbinski wrote:
> Source: linux
> Version: 7.3
> Severity: normal
> X-Debbugs-Cc: Bastian Blank <[email protected]>, [email protected]
>
> I've just used the new `pkg.linux.unsigned` profile to build myself a 7.3.1
> and
> it worked almost fine: the only problem was that after installing the built
> packages, the image was not copied from `/usr/lib/modules/${kernelRelease}/`
> to
> `/boot/` and as a consequence `update-grub` did not add it to my Grub menu.
>
> I'm guessing that the reason is that post-install scripts expect image files
> in
> `/usr/lib/modules/${kernelRelease}/` to be named `vmlinuz`, while when using
> this profile, it is named `vmlinuz.unsigned`.
>
> My simple workaround is to manually copy the image to
> `/boot/vmlinuz-${kernelRelease}` and rerun `update-grub`.
>
> I use `linux-base` version 4.17~bpo13+1.
>
> Best regards!
>
>
> -- System Information:
> Debian Release: 13.7
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
> 'stable'), (100, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 7.3.1+morgwai2.1-amd64 (SMP w/24 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_IE:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
--- End Message ---
