Remove opam pin <compiler> to avoid issues with opam 2.1 #150
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Mmh, the pin was added in #61. I’m not sure how to fix both issues :/ |
|
I think that the target here would be to have a precise switch invariant - that'll do exactly what the pin did before without triggering #61 (at least I don't think it should trigger that - if the package in the switch invariant is no longer available, I don't think that causes the solver to ignore the invariant). I've no idea what that means in terms of having an opam 2.0 root initially, though 😭 |
benmandrew
force-pushed
the
master
branch
2 times, most recently
from
64dfa12 to
5b6d232
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See ocaml/opam#4501
Some more details on the issue can be seen in ocurrent/opam-repo-ci@a4cbe3f