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
At some point I created an opam switch with ocaml-variants.4.14.2+trunk as the invariant (probably by accident, but it wasn't an issue so far). I now needed to install a newly released package from opam repository so I did opam update. This also included the update that ocaml-variants.4.14.2+trunk is now unavailable.
The result of this was that opam seemed to refuse to do anything because the unavailable package was still installed in my switch.
For example, when I just tried installing the unrelated new package with opam install, then it just complained about ocaml-variants.4.14.2+trunk as "missing dependency" or something. opam upgrade had the same problem.
Even opam remove ocaml-variants.4.14.2+trunk errored like that, which was particularly confusing (the unavailable package is a problem, but I also cannot get rid of it).
I think eventually opam install --update-invariant ocaml-variants.4.14.2+options or something actually worked to make the switch usable again. However, I don't remember seeing --update-invariant being suggested by any of the earlier errors (I don't have the output logs).
It seems that an installed but now-unavailable package is somehow problematic for opam. Although I think it shouldn't have been in my case, especially because the package version still exists on opam-repository (albeit with different contents). Nevertheless, if a package is already installed and there's no need to change it, then being unavailable shouldn't be a problem for existing installations.
At some point I created an opam switch with
ocaml-variants.4.14.2+trunk
as the invariant (probably by accident, but it wasn't an issue so far). I now needed to install a newly released package from opam repository so I didopam update
. This also included the update thatocaml-variants.4.14.2+trunk
is now unavailable.The result of this was that opam seemed to refuse to do anything because the unavailable package was still installed in my switch.
For example, when I just tried installing the unrelated new package with
opam install
, then it just complained aboutocaml-variants.4.14.2+trunk
as "missing dependency" or something.opam upgrade
had the same problem.Even
opam remove ocaml-variants.4.14.2+trunk
errored like that, which was particularly confusing (the unavailable package is a problem, but I also cannot get rid of it).I think eventually
opam install --update-invariant ocaml-variants.4.14.2+options
or something actually worked to make the switch usable again. However, I don't remember seeing--update-invariant
being suggested by any of the earlier errors (I don't have the output logs).It seems that an installed but now-unavailable package is somehow problematic for opam. Although I think it shouldn't have been in my case, especially because the package version still exists on opam-repository (albeit with different contents). Nevertheless, if a package is already installed and there's no need to change it, then being unavailable shouldn't be a problem for existing installations.
opam config (after fixing the switch)
The text was updated successfully, but these errors were encountered: