Hello debian-boot, Cyril,
It happened again: the kernel got updated and the daily d-i images
(being based on sid) result in a kernel mismatch. https://tracker.debian.org/pkg/linux-signed-amd64
You can see the red bars in openQA:
https://openqa.debian.net/
In openQA the kernel mismatch is diagnosed rather quickly after a kernel update.
* Do you want future mails of this type, or are you monitoring openQA/something else yourselves?
* Would a setting like 'LINUX_KERNEL_ABI ?= auto' be welcomed as a
patch? With that value, the kernel will be automagically be matched to
the current kernel version, whereas it would still be possible to
specify 'LINUX_KERNEL_ABI ?= 6.12.8' for explicit kernel versions.
I was looking at this (briefly) this morning to see how we might notice
that we're in this state during the debian-cd run, and abort, as that
would at least prevent people being offered the known-broken image to
test, although I guess there'd still be the chance of producing an image
that was OK when you started, but was broken by the time you'd finished,
if you get the timing perfectly wrong.
The thing I failed to work out this morning was how to discover the
version of the kernel that's in the version of d-i that debian-cd is
going to use. Given that it should be pretty trivial to check that the
needed kernel version is still available.
If anyone happens to know the answer to that, that would be helpful :-)
BTW There was a thread about this on debian-cd last month in which
Cyril's mail provides helpful pointers:
https://lists.debian.org/debian-cd/2024/12/msg00044.html
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 485 |
Nodes: | 16 (2 / 14) |
Uptime: | 95:29:32 |
Calls: | 9,642 |
Files: | 13,701 |
Messages: | 6,163,498 |