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

Impact of pinning after updating to Testing #114

Open
geckolinux opened this issue Aug 30, 2022 Discussed in #106 · 0 comments
Open

Impact of pinning after updating to Testing #114

geckolinux opened this issue Aug 30, 2022 Discussed in #106 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@geckolinux
Copy link
Contributor

Discussed in https://github.com/orgs/SpiralLinux/discussions/106

Originally posted by bin-linux August 22, 2022
Just a bit of forward planning here. I've updated one of my Spiral VMs to MATE testing - naturally all went well.
However I am wondering out the impact of the kernel pinning. For example, when Bookworm goes live it will then be possible to install newer kernels from future backports, but won't that be messed up by inherited pinning? Also with 5.18 going end of life there will surely have to be a shift somewhen?
EDIT: After upgrading I notice that the kernel pinning is gone. This begs the question of what will happen in future. If the aim of Spiral is to stay on backports and fast-track then when Bookworm goes live the repos will have to be updated - I assume manually. How will the kernel pinning be re-instated?

@geckolinux geckolinux added the documentation Improvements or additions to documentation label Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant