-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve goal according to strict setting first #1416
Conversation
It should help to force solver to prefer latest solution rather then minimalistic solution skipping something. Performance improvement for operation that does not generate any problem, because transaction is resolved only once with strict setting. Related: https://bugzilla.redhat.com/show_bug.cgi?id=2272257
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Hm, it looks like some tests are failing - e.g. if you try to install already installed package name and newer version is available, the result is upgrade instead of "nothing to do". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are several failing tests.
There is a significant problem with the patch. It will force to upgrade packages to latest - when installed version is a-1-1.noarch and available is a-2-1.noarch then even |
Closing the PR, because the new behavior will make no-best option useless and will trigger upgrades in situation when request should be satisfied by installed version. |
It should help to force solver to prefer latest solution rather then minimalistic solution skipping something.
Performance improvement for operation that does not generate any problem, because transaction is resolved only once with strict setting.
Related: https://bugzilla.redhat.com/show_bug.cgi?id=2272257