fix packagehub activation #424
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
…ror 106 from zypper because of untrusted repo signing key. this patch works around this by allowing the initial refresh to fail for this product.
digitaltom
changed the title
|
Well Done! Your tests are still passing. |
lagartoflojo
deleted the
workaround_initial_packagehub_repo_refresh_failure
branch
|
|
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.
on initial refresh of packagehub repositories, SUSEConnect gets an error 106 from zypper because of untrusted repo signing key. this patch works around this by allowing the initial refresh to fail for this product.