Bugfix: zypper ZYPPER_EXIT_NO_REPOS exit code #49805
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
ghost
self-requested a review
meaksh
approved these changes
Sep 27, 2018
rallytime
approved these changes
Sep 27, 2018
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.
What does this PR do?
pkg.installedreports failed if the following conditions are met:What issues does this PR fix or reference?
pkg.installeddoes not report failed if the following conditions above are met.Caveats
Zypper (all versions) still contains a bug (which is already fixed as of today) — https://bugzilla.suse.com/show_bug.cgi?id=1109893 — where new package installation fails with the same exit code. That said,
pkg.installedwill work, butpkg.installfrom execution command will not fail, if you did not upgrade zypper.Tests written?
No
Should just pass existing.