Unhelpful conflict messages #4373
Comments
|
Similar here for I would have expected an extra step: |
|
Ok, I see what's happening, we just need to refine how information is filtered out. Here is the message with more info and less filtering: Obviously in this case we should have been able to merge all the chains rather than just use one... |
|
I have another really surprising and different one here: |
|
Could this be added to the next |
|
Here is another example of a package that fails without any messages like |
|
Actually, the empty conflict message problem looks like the bug in dose 6.0 I fixed here: #4515 (comment) |
|
More testing with dose 5.0.1: Switching to master with dose 7.0.0, there seems to be no differences with opam 2.1: I also tested on a macOS/arm64 with dose 7.0.0 and it seems that the constraint solver does not like having "available constraints" in the compiler packages: So overall the issue won't be resolved by upgrading dose. It is an endemic issue since opam 2.1 (as seen above by the clear difference between the conflict message in 2.0 and 2.1) |
|
Hi, currently I try to use $ git clone https://github.com/dinosaure/unipi
$ cd unipi
$ git checkout with-paf-opam
$ mirage configure
$ make depends
opam pin add -k path --no-action --yes mirage-unikernel-unipi-unix . && opam depext --yes --update mirage-unikernel-unipi-unix ; opam pin remove --no-action mirage-unikernel-unipi-unix
Package mirage-unikernel-unipi-unix does not exist, create as a NEW package? [Y/n] y
[mirage-unikernel-unipi-unix.~dev] synchronised (file:///home/dinosaure/dev/unipi)
mirage-unikernel-unipi-unix is now pinned to file:///home/dinosaure/dev/unipi (version ~dev)
opam: unknown command `depext'.
Usage: opam COMMAND ...
Try `opam --help' for more information.
Ok, mirage-unikernel-unipi-unix is no longer pinned to file:///home/dinosaure/dev/unipi (version ~dev)
opam install -y --deps-only .
[ERROR] Package conflict!
Sorry, no solution found: there seems to be a problem with your request.
No solution found, exiting
make: *** [Makefile:15 : depends] Erreur 20So I believe that something is wrong about dependencies but I don't have any clues 😕 . Do you know an option to explain where is the error? |
|
Same issue with opam-repository at |
kit-ty-kate
added a commit
to kit-ty-kate/opam
that referenced
this issue
Jan 4, 2022
This was referenced Jan 4, 2022
|
Please refer to discussion for examples of conflict message. |
This was referenced Aug 17, 2022
Closed
kit-ty-kate
added a commit
to kit-ty-kate/opam
that referenced
this issue
Sep 1, 2022
rjbou
pushed a commit
to kit-ty-kate/opam
that referenced
this issue
Sep 2, 2022
kit-ty-kate
added a commit
that referenced
this issue
Sep 2, 2022
Add some tests showing the unhelpful conflict messages mentionned in #4373
|
I am seeing this message, it may be related here. But I am looking for a workaround. Switch invariant: ["ocaml-base-compiler" {= "4.09.1"} | "ocaml-system" {= "4.09.1"}]
[ERROR] Could not determine which packages to install for this switch:
* Missing dependency:
- ocaml-base-compiler = 4.09.1 | ocaml-system = 4.09.1
unmet availability conditions: '!(os = "macos" & arch = "arm64")'
unmet availability conditions: 'sys-ocaml-version = "4.09.1"' |
|
In this case, the conflict message is rather explicit:
Only OCaml 4.10.2 or >= 4.12.0 support the new architecture. This part could be explicited but I don't see an easy way to do that so I don't think it's doable. |
|
I agree. Thanks for the answer. I am not an OCaml user/dev so I am not really into OCaml. But I do use a software that was written in OCaml. This one uses 4.09.1. I am not sure if I can upgrade to let's say 4.10.2. I thought I tried once to use a different version than what was specified but I think I ran into problems and something did not work. Do you know if upgrading the version like this is something that should work? |
|
It should, but the OCaml forum is the preferred place to ask this kind of question: https://discuss.ocaml.org/ |
|
Ok, thanks anyway @kit-ty-kate |
|
I came across a confusing message in https://github.com/RyanGibb/ocaml-dns-eio/ With: I got: Changing |
Leonidas-from-XIV
pushed a commit
to Leonidas-from-XIV/opam
that referenced
this issue
Mar 10, 2023
Leonidas-from-XIV
pushed a commit
to Leonidas-from-XIV/opam
that referenced
this issue
Mar 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
*** Please add your unhelpful conflict message to this discussion ***
While trying to install
expect.0.0.6on OCaml 4.12:I would have expected:
as the latest version of
batteriesindicates.The text was updated successfully, but these errors were encountered: