Noble security fix#224
Merged
ekristen merged 5 commits intoteamdfir:masterfrom Apr 14, 2026
Merged
Conversation
This was referenced Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses the issue #223 by removing the currently pinned
noblecodename and replacing it with the extracted codename from the OS. This will provide fixes for Jammy, and allow for future-proofing with Resolute. As Jammy is the oldest OS supported, it will also remove thesources.listfile from Jammy in favor of the .sources file as long as the appropriate repo is enabled. Thefile.absentoption is in both universe and multiverse to ensure that the states can function independently if only one of them is executed in the future.Tested on Jammy and Noble on both amd64 and arm64 versions through several iterations with no issues.