Lower the priority of testing-farm-tag-repo as first prepare task #703
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
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.
This is a followup for #697 and fixes a corner-case we didn't noticed in that PR:
If the test system is a testing-farm system, has a testing-farm-tag-repository with high priority, and the distro has pre-installed an rpm which depends on
llvm-libs(such asbcc,mesa-dri-drivers, etc), thendnf install --bestwill still consider as "best" the rpms coming from the highest priority repo -- which is testing-farm-tag-repository. Hence we must first lower the tag repo priority, then add the copr repo and ask dnf to install/update llvm-libs.