Skip to content
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.

Sign up for GitHub

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

Jump to bottom

optional SOLVER_FORCEBEST behavior for SOLVER_DISTUPGRADE #232

Open
j-mracek opened this issue Oct 13, 2017 · 2 comments
Open

optional SOLVER_FORCEBEST behavior for SOLVER_DISTUPGRADE #232

j-mracek opened this issue Oct 13, 2017 · 2 comments
Labels
RFE 🎁

Comments

@j-mracek
Copy link
Contributor

I am not sure if this is behavior, bug, or my problem in my to complicate case, but I tried job with

queue_push2(&goal->staging, SOLVER_DISTUPGRADE|SOLVER_SOLVABLE_ALL|SOLVER_WEAK, 0)

and I still was unable to get transaction with same set errors like without SOLVER_WEAK. Please is SOLVER_WEAK supported with SOLVER_DISTUPGRADE|SOLVER_SOLVABLE_ALL ?
Thanks a lot for any information that anyone can provide.
@ignatenkobrain
Copy link
Collaborator

AFAIK distupgrade supports all-or-nothing only

@j-mracek
Copy link
Contributor Author

@mlschroe Please is there any plan to add support of SOLVER_WEAK for SOLVER_DISTUPGRADE operation?

@ignatenkobrain ignatenkobrain changed the title SOLVER_DISTUPGRADE do not react to SOLVER_WEAK optional SOLVER_FORCEBEST behavior for SOLVER_DISTUPGRADE Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
RFE 🎁
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ignatenkobrain @j-mracek