Open kit-ty-kate opened 3 weeks ago
The source of the issue is located in OpamSolution.check_availability
https://github.com/ocaml/opam/blob/9c7a256f60e78d1a1cc5ea90f8069a351aeb86a5/src/client/opamSolution.ml#L192 which seems to mix both concept of "unavailability because the package does not (longer) exist" and "unavailability because the package is not available on this platform"
Based on how OpamSwitchState.unavailable_reason
is used everywhere else with the correct exit_reason
, i strongly believe this is a bug.
Similar to https://github.com/ocaml/opam/issues/4493 Using opam 2.2.0~beta3 and https://github.com/ocaml/opam-repository/pull/26072:
According to the documentation, exit code 5 means:
Instead, one would expect exit code 20: