This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
EPEL: Import GPG keys #464
Merged
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
An issue in ansible[1] has been fixed ensuring that the dnf/yum module actually does verify GPG signature. Meaning we need to import them before using epel. [1] ansible/ansible#71537 fixes: #7709
Spredzy
requested review from
mikedep333,
mdellweg,
dkliban,
fao89 and
bmbouter
|
Attached issue: https://pulp.plan.io/issues/7709 |
dkliban
approved these changes
Oct 14, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
An issue in ansible[1] has been fixed ensuring that the dnf/yum module
actually does verify GPG signature. Meaning we need to import them
before using epel.
[1] ansible/ansible#71537
fixes: #7709