optional SOLVER_FORCEBEST behavior for SOLVER_DISTUPGRADE
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 609
- Forks
- 177
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the queue_push2 call shown in the report and trace how SOLVER_DISTUPGRADE, SOLVER_SOLVABLE_ALL, and SOLVER_WEAK are handled. Check whether SOLVER_WEAK is supported in that combination and define completion as documented or corrected behavior for the reported transaction errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100