That was the one I was referring to; I linked the wrong stuff previously, I wanted the original breakage thread for r322 in august 2022:
I think I finally understood something:
1° you’re talking about a hook that runs only mkconfig, while my own ran both grub-install and mkconfig.
2° The existence and role of that hook in the Great Grubbening of 22 was not mentioned as a cause of the problem in the thread, and so I developed a warped understanding of how grub works: I thought part of the grub package files passively played a role in the later phase of the boot, somehow:
So what was implied was “When you call grub-mkconfig, whether manually or because the hook we set up on kernel update does that for you, that updates only the userspace components.”
Pinging @dalto for sanity check.
One last thing I want to check: are we agreed that there is no reason to run grub-mkconfig on kernel updates, only on install/removal of entirely new kernels (eg zen or something like that)? (Or of course upon modification of /etc/default/grub, or after a grub-install)
If that is the case, since I’ve all the kernels I need (vanilla, lts, zen) already, and I’m happy with my grub config and unlikely to tinker with it anymore, now that I’ve removed my -install + -mkconfig hook, I can basically ignore updates to the grub package entirely (until I want to tinker again, of course).