On 2026-05-24 at 09:35, Greg Wooledge wrote: > On Sun, May 24, 2026 at 09:08:58 -0400, The Wanderer wrote: > >> On 2026-05-24 at 08:23, Antonio Russo wrote: >> >>> The linux-headers-amd64 package exists for this exact purpose. >>> (presumably other architectures have an equivalent). >> >> That will handle the "corresponding" part, but not AFAIK the >> "automatically" part - which I parse as meaning "when I install a >> new (version of) linux-image-*, linux-headers-* should get >> installed along with it, without me needing to do anything extra at >> install time to make that happen". >> >> I have yet to manage to think of a way to *ensure* that automation >> in all circumstances, for all methods of initiating upgrade. > > If you need DKMS modules, you have two paths from which to choose. > The first path, which most people choose, involves adding a > trixie-security source to apt, and installing both > "linux-image-amd64" and "linux-headers-amd64". Whenever there's a > kernel security update, you will automatically get both the image and > headers for that update.
Okay, you're right. I was referring to the idea that upgrading one wouldn't necessarily cause the other to also get upgraded, so you could wind up with the two out of sync, and I was doing that because I couldn't see any path from either package which would lead to the other. Testing it out, however, shows that in fact it does happen - and the reason turns out to be that both packages have a versioned dependency on linux-base-amd64, so upgrading either will pull in the new version of that, which will in turn cause apt to want to upgrade the other to prevent its dependency from becoming broken. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
