You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm using opam 2.2.0~beta3 on windows. I've noticed that a package name is percent-encoded in an error message:
C:\Users\etien\src\dune>opam install -y lwt cinaps core_bench "csexp>=1.3.0" js_of_ocaml js_of_ocaml-compiler "mdx>=2.3.0" menhir ocamlfind ocamlformat.0.26.1 "odoc>=2.4.0" "ppx_expect>=v0.16.0" ppx_inline_test
ppxlib ctypes "utop>=2.6.0" "melange>=4.0.0-414"
[ERROR] Package conflict!
* No agreement on the version of ppx%5fexpect:
- ppx_expect >= v0.16.0
- core_bench → ppx_jane < v0.15 → ppx_expect < v0.15
* No agreement on the version of ocaml-base-compiler:
- (invariant) → ocaml-base-compiler = 4.14.1
- core_bench → core = 109.24.00 → ocaml < 4.01.0 → ocaml-base-compiler = 3.09.1
The first occurrence is displayed as ppx%5fexpect, while the rest is displayed correctly as ppx_expect.
Maybe that's a styling issue, since the invalid one is printed in bold while the other ones are using normal text (this on windows Terminal).
The text was updated successfully, but these errors were encountered:
opam@eb69dfc8d71b:~$ opam-dev install core_bench.v0.15.0 "ppx_expect>=v0.16.0"
[ERROR] Package conflict!
* No agreement on the version of ppx%5fexpect:
- ppx_expect >= v0.16.0
- core_bench = v0.15.0 -> ppx_jane < v0.16 -> ppx_expect < v0.15
* Incompatible packages:
IIRC the _ is not valid in CUDF, so it looks as though we're not translating a package name back in the "No agreement on the version" part of the message.
Hi,
I'm using opam 2.2.0~beta3 on windows. I've noticed that a package name is percent-encoded in an error message:
The first occurrence is displayed as
ppx%5fexpect
, while the rest is displayed correctly asppx_expect
.Maybe that's a styling issue, since the invalid one is printed in bold while the other ones are using normal text (this on windows Terminal).
The text was updated successfully, but these errors were encountered: