Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opam doesn't allow with-test in conflicts #269

Merged
merged 1 commit into from
Feb 24, 2023
Merged

Conversation

talex5
Copy link
Contributor

@talex5 talex5 commented Feb 24, 2023

So, we have to conflict with jbuilder in all cases (which isn't very good, but there aren't many such packages left).

Suggested by @kit-ty-kate.

So, we have to conflict with jbuilder in all cases (which isn't very
good, but there aren't many such packages left).

Suggested by Kate <[email protected]>.
@talex5 talex5 merged commit 82a3a93 into mirage:master Feb 24, 2023
@talex5 talex5 deleted the fix-opam branch February 24, 2023 15:23
talex5 added a commit to talex5/opam-repository that referenced this pull request Nov 28, 2024
CHANGES:

- Update dependencies and remove capnp-rpc-mirage (@talex5 mirage/capnp-rpc#276).
  - Update for breaking changes in tls, mirage-crypto and mirage-flow.
  - capnp-rpc-mirage isn't used much, and won't be needed after switching to Eio.

- Update tests to Cap'n Proto 1.0.1 (@MisterDA mirage/capnp-rpc#274).

- Update links to ocaml-ci and capnp-ocaml (@tmcgilchrist mirage/capnp-rpc#271).

- Opam doesn't allow with-test in conflicts (@talex5 mirage/capnp-rpc#269).

- Disable opam tests on macos (@talex5 mirage/capnp-rpc#268).

- Update CI (@MisterDA mirage/capnp-rpc#272, @talex5 mirage/capnp-rpc#277).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants