• Kernel mismatch in daily d-i image

    From Roland Clobus@21:1/5 to Debian Install System Team on Mon Jan 13 16:50:03 2025
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------8wyAi2aXTqm4uBvvqZJk0hVd
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGVsbG8gZGViaWFuLWJvb3QsIEN5cmlsLA0KDQpJdCBoYXBwZW5lZCBhZ2FpbjogdGhlIGtl cm5lbCBnb3QgdXBkYXRlZCBhbmQgdGhlIGRhaWx5IGQtaSBpbWFnZXMgDQooYmVpbmcgYmFz ZWQgb24gc2lkKSByZXN1bHQgaW4gYSBrZXJuZWwgbWlzbWF0Y2guDQpodHRwczovL3RyYWNr ZXIuZGViaWFuLm9yZy9wa2cvbGludXgtc2lnbmVkLWFtZDY0DQoNCllvdSBjYW4gc2VlIHRo ZSByZWQgYmFycyBpbiBvcGVuUUE6DQpodHRwczovL29wZW5xYS5kZWJpYW4ubmV0Lw0KDQpJ biBvcGVuUUEgdGhlIGtlcm5lbCBtaXNtYXRjaCBpcyBkaWFnbm9zZWQgcmF0aGVyIHF1aWNr bHkgYWZ0ZXIgYSBrZXJuZWwgDQp1cGRhdGUuDQoNCiogRG8geW91IHdhbnQgZnV0dXJlIG1h aWxzIG9mIHRoaXMgdHlwZSwgb3IgYXJlIHlvdSBtb25pdG9yaW5nIA0Kb3BlblFBL3NvbWV0 aGluZyBlbHNlIHlvdXJzZWx2ZXM/DQoqIFdvdWxkIGEgc2V0dGluZyBsaWtlICdMSU5VWF9L RVJORUxfQUJJID89IGF1dG8nIGJlIHdlbGNvbWVkIGFzIGEgDQpwYXRjaD8gV2l0aCB0aGF0 IHZhbHVlLCB0aGUga2VybmVsIHdpbGwgYmUgYXV0b21hZ2ljYWxseSBiZSBtYXRjaGVkIHRv IA0KdGhlIGN1cnJlbnQga2VybmVsIHZlcnNpb24sIHdoZXJlYXMgaXQgd291bGQgc3RpbGwg YmUgcG9zc2libGUgdG8gDQpzcGVjaWZ5ICdMSU5VWF9LRVJORUxfQUJJID89IDYuMTIuOCcg Zm9yIGV4cGxpY2l0IGtlcm5lbCB2ZXJzaW9ucy4NCg0KTGl2ZS1idWlsZCBhbHJlYWR5IGhh cyB0aGlzIGF1dG9tYWdpYyBpbiBwbGFjZSwgd2hpY2ggZXhwbGFpbnMgd2h5IHRoZSANCmRh aWx5IHNpZC1iYXNlZCBpbWFnZXMgc3RpbGwgaGF2ZSBhIHdvcmtpbmcgZC1pIGluc3RhbGxl ci4NCg0KV2l0aCBraW5kIHJlZ2FyZHMsDQpSb2xhbmQgQ2xvYnVzDQo=

    --------------8wyAi2aXTqm4uBvvqZJk0hVd--

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEUFVLM5Bdj7GSJEb+YsV8aqYUlb0FAmeFNAEACgkQYsV8aqYU lb2hrw//UoyXulf70ig9+bTuQDBSmjz07t5Toz2koqj8FOBAFkwJbJKDt4Z5O5MT MfHBa0YKknv9ifZylY4Z2A6QCgMi8bzvdc78/954CrvnyPoA16FQ5X35/Brgj+E1 64LkwHzZp2QMvc5xqUTrp+IWxqtVYw5uQo/i3+XMIlyToVnxVoGjlXd50RsCLumy 1fGjpWM2EggY4qPjXvWCel0jn+ZP16dMAKGQFSHfFm5uePKNXZ7heNVzPrMSaDht fuOl356xjQ4pkvbMFZWyEJ00lWUmQcYKuS4LDMVuVzdN7WF05OGmYGOsNDisQmwb Vut9AEaEj97XR98MVjVKPKotKWO3uamOZpHaOYCns5rl6PQoyulkcObPhkQL/VFy WL0O5sD7mm4SjeYLl9/vPokCwcmQp60IHaZH1kHLB5KJcIb+TkxkEG80R1fJ5oxl nfL3F/HIRhD6uYjuDaiF3n7IDYnz77yZGPohyTY6mihbxFFQQeTF3px/Vl7qusID jo9hPhNJTn59D8+vW8r7CiYYOKbitVivLFnsiXU7PAdAnL/kssTXDZR1h0adBfn5 rwz+j8F6D6+tJOSfBkZu0GLNJ3yKjnuTSKQg1qwLF9gsJRhfzNWRcH/Np1+ew8uD Sm1FvDFD63A9ZliPQHjETxTzgKZ7WVTkrW7d0erOgA/QFPvz6BU=
    =9N/B
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Philip Hands@21:1/5 to Roland Clobus on Mon Jan 13 21:30:01 2025
    Hi Roland,

    Roland Clobus <rclobus@rclobus.nl> writes:

    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 may be mistaken, but I think that the problem is due to debian-cd
    (AFAIK) using the version of d-i that's in the archive to build the CDs,
    rather than building a new d-i version on the fly.

    This is different from what I do for the mini-ISOs that get built for
    testing on salsa, and I guess it's different from what's occurring with
    your Live builds.

    That being the case, the thing in the archive is always going to lag a
    bit, because one cannot build it until the signed kernel lands, and that
    takes a time after the unsigned one is built.

    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

    Cheers, Phil.
    --
    Philip Hands -- https://hands.com/~phil

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEE3/FBWs4yJ/zyBwfW0EujoAEl1cAFAmeFd58ACgkQ0EujoAEl 1cBD8BAAxSG6u+xQkJrOzkctqtZSF3isccr8D1tmMbmk1tYHLemSZ//KUOC7QPKy OWvVqHFYsnXs2K7Jn0Aeizdltdu1FIkgDqiFLc0MUp5jnPn2sH5WSk1kAgkbEteH lAAoWmXFdbOviklcPLwEFLtfh1zG+caty2qJU1osdIbSvek6XY8Keqq8S5TLrGw/ IzMrJN9+h9Ylhd+BBFNXiYMrqobKJL1QIQbktOK1VlwonSaHX2k7x7FgTQD1+DMe 6yeQBuSYcqk89CxWUZ4l92zuvHyZFEjXpMeypwX7KD8R3+iEvfxdvVqpeGIfJIST RWr+iEFFXBBCH12r2BvEAiqtZFg8Iu3nIQVbzf8t3bCVA7UAsMqjGyHvf/dsxCGA WRfsTp/YJyzEplWbvChP3spx8n9DDW0b/f7mX4NOs6TOPOdFP2sFfqB2AwHxavjx Uafnb4uqe4jZaxgBpf5qJuu4Khj3NlmIu4W472s+I24qlPASodjXnCIgh7EbC6CM GuEyVnZyEENAjBlHU3zxcZglZ2cAKuZBVknA1NUT0C/EgN7mCRMcLD4FKSema3wO z9p+dG7yKatrHtKt7VW/eCmPfRqPZ8IEPRnbIsp0u/MPSdkK3mmdzOUfWqyTaul5 Tq71xFrun5LGF32fElPGAfM0JhHfE2cslex3f1cOnP5liocFwg8=WxF/
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gatewa
  • From Cyril Brulebois@21:1/5 to All on Tue Jan 14 02:50:01 2025
    Philip Hands <phil@hands.com> (2025-01-13):
    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.

    I think I mentioned MANIFEST.udebs…

    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

    … but if I did, that wasn't in that specific mail. This file is found
    at the top-level of the generated build artifacts, and mentions
    kernel-image (beware of multiple flavors).


    Cheers,
    --
    Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
    D-I release manager -- Release team member -- Freelance Consultant

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmeFwa8ACgkQ/5FK8MKz VSAFHxAAunM1enYwp+r4t+xAjjku7Iexa2Q3Ok8dVAL8fax4ftDusErzYrXzP9Ur ZsMPGjkUhJKXMfIX1At0LWQMIQr0OtG9lzdIdW5pJ9tXIPysXzY0jhz2qZFSX6yb bObaRq43j9o92wBB9SE2iaDoHpzKwYbzuoGPkmS6Z76mSxKdUtxwtPGL3C4V/ynN ymJkYS41xCsRYVRP1h3kNDRlf5U2MI1vBAw2UdrZRuWF7o/nTAR6Cjq7B+xOZ6d+ cpPMmzwHAat/qOuwN7kTnymAlSXhjJ8U7diZnL/s5EhPl3yrxfyfXCq/gxGJvmBm 6UVWSVXWPoowm//iT4nWsSWpusuDH63yBZOgsyggj7v2g7eLZuhw4bd5dwxBBFVm P/+SU0sA6ElOBvmwBBIPlAmVC5KGHAhsQdfLLs0hptUPwjn5OJidc51jYs0QTFr1 MD6ymVhyUzKdtoL5tc2dEkzoinQWXH9u2wXQCOLs/4GvTW+70wMpS6zdG+Awta3U 03i5FJx77838Xx00CKJA2pgZ1Xrn5f7reBNNRejUdnV+NhvwbHIrFGW2OplDXz8b UemowooL8K8PfnkORZ55PTJVCgxjMTFxtegpkgOEXasOK26ymMlTczwWrq/Y0z6w +UosqG6PmDjGZR7uPNpVfpN+gz6jxs3NBK4VGImzHiN98IZJmYI=
    =TCMP
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *