Avoid certain symlinks when checking for inconsistencies #513
Conversation
This file contains 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
andreas-el
force-pushed
the
resolve_reported_symlink_inconsistencies
branch
from
5ff07fe to
90cd496
Compare
andreas-el
changed the title
berland
approved these changes
Oct 3, 2024
andreas-el
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #512
We have altered how symlinks are being interpreted when introducing multiple rhel-versions, and when introducing bleeding-timestamped builds.
The concept of root-link does not fully match here, where we source symlinks based on OS versions in enable scripts, and therefore have no clean linkage as we used to have.