-
Notifications
You must be signed in to change notification settings - Fork 372
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
"resolution of the request timed out" even with OPAMSOLVERTIMEOUT=1200 #5504
Comments
Thanks for this useful feedback. Side question: |
Hi, opam 2.1.4 Same trouble today : impossible to install packages (after installing ocamlformat ; that fails at some step) Using OPAMSOLVERTOLERANCE=0.0003 didn't fix the situation. To work around, I created a new packages configuration (so-called "switch"). finally, I tried to pin the package to a specific version but opam still refused to install it. My service is broken with not understandable reason. Q1: how can I fix that? Q2: How can you make opam's behaviour more predictable? Thanks |
Did you compile the branch in #5510 ? If you're still using 2.1.4 it looks like you haven't tried this fix as linked above and thus setting |
I didn't, believing it was an included var I just had to use. See
Now, when I have some trouble with opam, i don't try to fix it anymore. It's nearly always a lost of time ending with crash or pain. PS: for unknow reason, with opam 2.1.5 I could finally build the targeted packages that failed as described. Q2: How can you make opam's behaviour more predictable? I mean we often don't exactly know what is going on. |
I have an old ocsigen.2.19.3 configuration that I don't want&need to upgrade.
After the problem described at #5485, it was destroyed but with some tweak, I could save it with a
opam switch export
and built it withopam switch import
.I've the following error message with the package
ocsigen-ppx-rpc
requires byocsigen-start
:Using
OPAMSOLVERTIMEOUT=1200
orOPAMSOLVERTIMEOUT=1200.0
gives nothing more.Using flag
--verbose
gives NO MORE details.For unknown reason, the existing and working
ocsigen-start.2.19.3
webapp was expectingocsigen-ppx-rpc.1.0
for compilation while this package is not a dependency (it is an ocsigen-start dependecy from 4.6.0). See https://opam.ocaml.org/packages/ocsigen-ppx-rpc/ .I suspect that it may have been caused by opam tool and opam repository that are not enough strict/demanding regarding declared opam files. ITO, one can declare a wrong opam file.
See [TODO : find previous discussion about that.]
btw, what is the recommended command/way to produce the real dependencies of a package?
ocamldep gives only references to external compilation units.
Possibly related issues:
#3447
#4203
#3447
#685
The text was updated successfully, but these errors were encountered: