Closed emillon closed 2 days ago
This isn't Windows-specific:
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.
This is also present in 2.1 (but not 2.0) - looks like it would have come in with #4349 (although it's not necessarily an issue directly with the PR)
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).