Your message dated Mon, 09 Sep 2024 00:15:09 +0200
with message-id <32b8bd198753dfa3ce664de37e79dd94ca4da66c.ca...@decadent.org.uk>
and subject line Re: linux-image-amd64: mess left when kernel installation
fails (grub treats the uninstalled kernel as existing)
has caused the Debian Bug report #1071468,
regarding linux-image-amd64: mess left when kernel installation fails (grub
treats the uninstalled kernel as existing)
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 ow...@bugs.debian.org
immediately.)
--
1071468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 6.6.13-1~bpo12+1
Severity: normal
X-Debbugs-Cc: debbug.linux-am...@sideload.33mail.com
A kernel installation failed due to a corrupt deb file that could not
be unpacked. That was reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071467
Apparently whatever generic installation mechanism is used, it fails
to properly treat a botched delivery. That is, even though the deb
file for kernel version 6.6.13-1~bpo12+1 is only 1480 bytes and so
corrupt it cannot even be unpacked, the package was erroneously
flagged as installed, at least in part:
===8<----------------------------------------
$ dpkg -l | grep 6.6.13-1~bpo12+1
iU linux-headers-6.6.13+bpo-amd64 6.6.13-1~bpo12+1 amd64 Header files for
Linux 6.6.13+bpo-amd64
ii linux-headers-6.6.13+bpo-common 6.6.13-1~bpo12+1 all Common header
files for Linux 6.6.13+bpo
iU linux-headers-amd64 6.6.13-1~bpo12+1 amd64 Header files for
Linux amd64 configuration (meta-package)
iF linux-image-6.6.13+bpo-amd64 6.6.13-1~bpo12+1 amd64 Linux 6.6 for
64-bit PCs (signed)
iU linux-image-amd64 6.6.13-1~bpo12+1 amd64 Linux for 64-bit
PCs (meta-package)
ii linux-kbuild-6.6.13+bpo 6.6.13-1~bpo12+1 amd64 Kbuild
infrastructure for Linux 6.6.13+bpo
ii linux-libc-dev 6.6.13-1~bpo12+1 all Linux support
headers for userspace development
===8<----------------------------------------
Perhaps “iU” and “iF” are correct flags in the first column (it’s
unclear because “man dpkg” does not document these). But grub
alterations were carried out despite the failure and the default
kernel became the version that could not even be unpacked from the deb
file (6.6.13-1~bpo12+1). So it’s not just a failure of that kernel but
also a failure in the installation logic, perhaps in apt. Though I
doubt apt would influence grub, so I’m filing this in the virtual pkg
linux-image-amd64 for lack of a better place.
-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990,
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-21-amd64 (SMP w/2 CPU threads; PREEMPT)
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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-amd64 depends on:
ih linux-image-6.6.13+bpo-amd64 6.6.13-1~bpo12+1
linux-image-amd64 recommends no packages.
linux-image-amd64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 19 May 2024 21:46:34 +0200 Manny
<debbug.linux-am...@sideload.33mail.com> wrote:
[...]
> ===8<----------------------------------------
> $ dpkg -l | grep 6.6.13-1~bpo12+1
> iU linux-headers-6.6.13+bpo-amd64 6.6.13-1~bpo12+1 amd64 Header
files for Linux 6.6.13+bpo-amd64
> ii linux-headers-6.6.13+bpo-common 6.6.13-1~bpo12+1 all Common
header files for Linux 6.6.13+bpo
> iU linux-headers-amd64 6.6.13-1~bpo12+1 amd64 Header
files for Linux amd64 configuration (meta-package)
> iF linux-image-6.6.13+bpo-amd64 6.6.13-1~bpo12+1 amd64 Linux
6.6 for 64-bit PCs (signed)
> iU linux-image-amd64 6.6.13-1~bpo12+1 amd64 Linux
for 64-bit PCs (meta-package)
> ii linux-kbuild-6.6.13+bpo 6.6.13-1~bpo12+1 amd64 Kbuild
infrastructure for Linux 6.6.13+bpo
> ii linux-libc-dev 6.6.13-1~bpo12+1 all Linux
support headers for userspace development
> ===8<----------------------------------------
>
> Perhaps “iU” and “iF” are correct flags in the first column (it’s
> unclear because “man dpkg” does not document these).
The first letter "i" indicates the requested status (installed) and the
second letter "F" or "U" indicates the actual status, respectively
half-configured or unpacked.
> But grub
> alterations were carried out despite the failure and the default
> kernel became the version that could not even be unpacked from the
deb
> file (6.6.13-1~bpo12+1). So it’s not just a failure of that kernel
but
> also a failure in the installation logic, perhaps in apt. Though I
> doubt apt would influence grub, so I’m filing this in the virtual pkg
> linux-image-amd64 for lack of a better place.
This is all based on a misunderstanding of what happened, which has
been discussed in #1071467. The new kernel version was successfully
unpacked and would have been bootable.
So I don't see any bug here.
Ben.
--
Ben Hutchings
A free society is one where it is safe to be unpopular.
- Adlai Stevenson
signature.asc
Description: This is a digitally signed message part
--- End Message ---
