Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: ALT Sisyphus failing #360

Closed
solardiz opened this issue Dec 2, 2024 · 1 comment
Closed

CI: ALT Sisyphus failing #360

solardiz opened this issue Dec 2, 2024 · 1 comment
Labels
testing A testing task or issue (e.g., with CI)

Comments

@solardiz
Copy link
Contributor

solardiz commented Dec 2, 2024

https://github.com/solardiz/lkrg/actions/runs/12124977914/job/33803883053

E: Couldn't find package kernel-headers-modules-un-def

@vt-alt

@solardiz solardiz added the testing A testing task or issue (e.g., with CI) label Dec 2, 2024
@vt-alt
Copy link
Contributor

vt-alt commented Dec 2, 2024

Oh yeah, we deleted un-def kernel in favor of numerical kernels. I added latest pseudo-flavour but it turned out to wok not as I expected (bringing 6.6 instead of 6.12 due to ALT apt bugs). I thought I will invent something complicated to bring the latest kernel but I didn't get idea yet.

vt-alt added a commit to vt-alt/lkrg that referenced this issue Dec 3, 2024
ALT switched to numerical kernel flavours, thus no 'un-def' anymore.
Bring the new package 'kernel-headers-modules-mainline' that's supposed
to track the mainline kernels. If it fails bring 'stable' kernel
headers. Perhaps, it can fail during the merge window when `x.y.1`
stable is already released to the `x.y` flavour, so the pseudo-flavour
isn't longer 'mainline' but 'stable'.

Fixes: lkrg-org#360
Signed-off-by: Vitaly Chikunov <[email protected]>
vt-alt added a commit to vt-alt/lkrg that referenced this issue Dec 4, 2024
ALT switched to numerical kernel flavours, thus no 'un-def' anymore.
Bring the new package 'kernel-headers-modules-mainline' that's supposed
to track the mainline kernels. If it fails bring 'latest1' kernel
headers. Bringing 'mainline' could fail during the merge window when
`x.y.1` stable is already released to the `x.y` flavour, so the
pseudo-flavour isn't longer 'mainline' but 'latest1' (note it ends with
`1`). This should not be the 'latest' as it provided by multiple
packages and naïve apt-get install will refuse to install.

Fixes: lkrg-org#360
Signed-off-by: Vitaly Chikunov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing A testing task or issue (e.g., with CI)
Projects
None yet
Development

No branches or pull requests

2 participants