‣ Attaching /home/runner/work/lkrg/lkrg/.mkosi-j5lzdb18 as loopback…įile '/usr/lib/python3.8/runpy.py', line 194, in _run_module_as_main ‣ Created image with partition table as /home/runner/work/lkrg/lkrg/.mkosi-j5lzdb18 ‣ Temporary workspace set up in /var/tmp/mkosi-h726qpf8 ‣ Setting up package cache /home/runner/work/lkrg/lkrg/mkosi.cache complete We started getting this: I: Retrieving InRelease We can indeed be dropping support for EOL'ed distros, but I'd rather do this for specific good reasons (if keeping such support becomes difficult or conflicts with our other goals), not just because of their EOL. For Ubuntu, we claimed support for 16.04+, and I think we should keep it that way for now. The oldest we currently support is RHEL7, so I think we should also keep support for any distro that we currently support and that is newer than RHEL7, even if it gets EOL'ed. Our testing on older versions isn't only to support those specific distros/versions, but also to have LKRG tested with those kernel versions, where similar versions might also be used on other distros from the time, including non-EOL'ed ones.

When we explicitly add a new version of Ubuntu, we expect possible failure due to that and we can handle it on a pull request intended for just that. Not updating the Ubuntu versions list automatically yet wanting to promptly add new versions is in fact contradictory, however my thinking is we don't want (more) sudden CI failures on unrelated changes to LKRG.

John the ripper github