ppx_type_conv 0.9.0 conflicts with ppx_deriving 4.02.0 #11086
Merged
Conversation
This file contains hidden or 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
This is the solution to build problems affecting cohttp proposed in mirage/ocaml-cohttp#591
✅ All lint checks passed 53a126c
✅ Installability check (8011 → 8011) |
Merged
gasche
added a commit
to gasche/opam-repository
that referenced
this pull request
Dec 22, 2017
see ocaml#11086 for previous version -- too restrictive -- of the conflict clause.
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.
This is the solution to build problems affecting cohttp proposed in
mirage/ocaml-cohttp#591
My first attempt at fixing the cohttp issue was #11085, but it seems to be the wrong approach.
I had to look at other files in the repository to remember whether
&or|should be used for multi-version conflicts, but this seems to be it. (It's not intuitive at all.)