Change order in which DNF update runs #8
Merged
+1
−1
Conversation
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
Signed-off-by: Stephen Simpson <ssimpson89@users.noreply.github.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
There was a problem hiding this comment.
Pull request overview
This PR fixes an issue where dnf update was overwriting the alternatives-managed python3 symlink, causing it to point to python3.9 instead of the intended python3.11.
Changes:
- Moved
dnf update -y && dnf clean allcommand to run before thealternativescommands in the build steps
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cigamit
approved these changes
Jan 30, 2026
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Problem
dnf updatewas overwriting the alternatives-managed python3 symlink, causing it to point to python3.9 instead of python3.11.Solution
Move alternatives commands to run after
dnf updateso package updates can't overwrite the configuration.