On 3 Jun 2024 09:51 -0500, from
[email protected] (Tom Browder):
But another remote host seems to have the same problem. Each host comes
from a different provider and had slightly different default pinnings in '/etc/apt/sources.list'.
I'll double-check my pinnings.
Try: apt-cache policy linux-image-amd64
Here's the output of that from my system, only slightly anonymized,
for comparison:
linux-image-amd64:
Installed: 6.1.90-1
Candidate: 6.1.90-1
Version table:
*** 6.1.90-1 500
500 http://security.debian.org bookworm-security/main amd64 Packages
100 /var/lib/dpkg/status
6.1.76-1 500
500 https://mirror.debian.example/debian bookworm/main amd64 Packages
6.1.67-1 500
500 https://mirror.debian.example/debian bookworm-updates/main amd64 Packages
I also double-checked, and 6.1.0-13 is indeed the ABI version
immediately preceding the kernel bugs incident. The kernels affected
by that in mainline Debian were 6.1.0-14/6.1.64* and 6.1.0-15/6.1.66*;
the latter by unrelated bug #1057967 which may or may not affect you.
This further reinforces my belief that the problem is likely to be an
errant apt pin meant to exclude those kernels from being installed accidentally, and which ended up matching too much. (The other obvious possibility would be that the mirror you're using stopped updating
around that time, but frankly that seems less likely, especially if
you are seeing the same behavior across two different hosting
providers.)
--
Michael Kjörling 🔗
https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)