-
Notifications
You must be signed in to change notification settings - Fork 15
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
Internal error in solver #90
Comments
Hello. I managed to extract the minimal package set triggering the issue and I added it as a test. With the latest commit
should be enough. |
Is it possible to make a test case in resolvo? |
Do you mean translating the set into the BundleBox terms? Well I could try, it seems technically possible, I just need to figure out how to map the debian versions into ranges. Any suggestions are welcome. |
The BundleBox versioning system represents a discrete set of versions, whereas Debian versions resemble an infinite, continuous set. Additionally, Debian's constraint semantics include concepts such as "no version of the package" and "any version of the package except for the specified one." I'm uncertain how to translate these concepts into the BundleBox range syntax, especially the latter. |
Thanks to your reproducer I found the bug and fixed in it #93 . With that fix both your reproducers produce a valid solution. Happy new year! 😄 |
Wow, that was quick. Thank you! |
Hello.
I am developing a tool to work with Debian repositories, which involves finding solutions for package recipes. I decided to give a shot to Resolvo, and it has been significantly faster than the APT solver over EDSP. However, I encountered an internal error during execution:
I couldn't create a minimal example, so I extracted the relevant code into a separate library. You can reproduce the issue with the following steps
For some reason, the issue occurs only with exim4 and sendmail.
Please let me know if I can provide more information or help debug this issue further.
Oh, and thank you for resolve and have a Happy New Year!
The text was updated successfully, but these errors were encountered: