-
Notifications
You must be signed in to change notification settings - Fork 358
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
Better error output for debugging #4258
Comments
The message "there seems to be a problem with your request" is a placeholder and generally symptom of a bug, normally there is more information. Also note that there are |
That's weird... here is what I get (both with opam 2.0.3 and 2.0.7 (latest stable)):
Dockerfile used (for reference):
|
Ah, I am noticing you seem to be using an external |
This is my full dockerfile right now (I copied some parameters how you used them to see if it makes a difference, but doesn't work. I do notice that you didn't do the
|
So I've been trying things just to see at what point it stops giving that error. Ran it again, no change, same error. Then I removed I attached the dockerfile what it looks like now as a file, to prevent these lengthy comments. EDIT: I removed Hopefully this helps in diagnosing this bug. |
Ah, probably has to do with how Debian provides
As a workaround, I would suggest you try to get your opam binary directly from https://github.com/ocaml/opam/releases/download/2.0.7/opam-2.0.7-x86_64-linux instead of |
@AltGr I did end up fixing the issue for myself once I got some error output, so that's solved :) |
I think this will have been resolved as part of the myriad changes in 2.1.0 for integrated depext along with various solver improvements. Please re-open if necessary! |
When I use opam to install multiple packages & dependencies, it's not uncommon for one to fail because of whatever reason (most of the time because the package needs to be pinned to the repository).
But rather then just telling me which packages are the culprit, I get the most useless response that effectively just tells me the command failed, without providing any useful information at all.
It'd be really useful if this could be improved and could tell the user which packages (or dependencies) failed so we have more to go on.
The text was updated successfully, but these errors were encountered: