GoalPrivate: Fix protecting the running kernel #385
Merged
+1
−1
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
The detected running kernel was not used in GoalPrivate::limit_installonly_packages() call.
|
LGTM, but do we have a test case for the issue? |
|
Please feel free to merge it when tests will pass. The same for the new CI tests. |
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.
The detected running kernel was not used in GoalPrivate::limit_installonly_packages() call.
Test: rpm-software-management/ci-dnf-stack#1241
Bug 2178329 - dnf5 doesn't replace the oldest installed non-running kernel with a newer one during upgrade