-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
new package packages/fasmifra/fasmifra.1.0.0 #19149
Conversation
…match the SPDX format
Thanks for the fixes. |
The CI test logs are a little hard to read.
It sends me there: In the same log file, I can read:
I understand the package was installed, then removed, then the next trial at installing failed. |
The error that needs to be fixed is
This is sue to some package (maybe parany) being downgraded to an incompatible version in
You just need to add the appropriate lower bound in the opam file. In this case I am not sure which one it is. |
To give you more context: the lower bounds test first installs the package with the usual bounds –which is expected to succeed–, then tries to downgrade all the dependencies to their lower bounds in a way compatible with their opam bounds. Then it proceed to reinstall your packages with all the dependencies downgraded. If it fails when building your package it means that some lower bounds are missing or incorrect |
Ok, I added a lower bound contraint on parany. |
Thanks. I agree with you, but I would not know where to start to make such a tool. On the one hand, error can be of very different nature, and on the other we would need to try and install or grep the interfaces of all possible versions of the packages that are getting downgraded, try to install with the versions that seem to be correct and repeat until there is a configuration that works. There is a lot of "understanding" that the tool needs to make |
And, the process would be very compute heavy.
…On Thu, Jul 29, 2021 at 5:51 PM Marcello Seri ***@***.***> wrote:
Thanks. I agree with you, but I would not know where to start to make such
a tool. On the one hand, error can be of very different nature, and on the
other we would need to try and install or grep the interfaces of all
possible versions of the packages that are getting downgraded, try to
install with the versions that seem to be correct and repeat until there is
a configuration that works. There is a lot of "understanding" that the tool
needs to make
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFUFAA6PVAFXBKNLIZ3OWTT2EI75ANCNFSM5BDW7TGQ>
.
|
Should I change something more? |
There is still a wrong/missing lower bound:
|
I'll check, maybe for parany. For the future, is there a script to do those tests locally? |
Note that the approach I took is: constrain almost all dependencies to the latest version currently available in opam. |
I don’t have a problem with it, if you want you can go and try relaxing some bounds. I don’t see a way to have such tool and for it to be usable. However, we are slowly fixing the lower bounds in the various PRs, so this will improve with time. It has already improved a lot in the last few weeks, but once we stumble upon previously unchecked packages it takes a while to find and fix all the issues. I don’t know if there is a way to replicate the lower bounds locally, maybe @kit-ty-kate knows |
The best we know how to do properly at the moment without taking too much time is to do it step by step (same as our CI does currently). You can use
|
Ok, thanks for the info. |
No description provided.