You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: