-
Notifications
You must be signed in to change notification settings - Fork 4
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
bump opam to 2.1 #17
bump opam to 2.1 #17
Conversation
Hi @gares, thanks for your PR! sorry for replying a bit late, being swamped these days. But actually, it can't work as is, because of this issue: ocaml/opam.ocaml.org#24 Because of that, it is not possible to build new
I will ping the opam team anew then. As soon as the problem above is solved, the docker-base CI will become green again thanks to its nightly build pipeline: |
@gares so the |
Thanks, no pressure really. |
opam-3.ocaml.org was introduced as a temporary measure in 930e5b1 (coq-community#17), but that server will decommissioned quite soon (ocaml/infrastructure#19) so this will avoid build breakage for Coq.
opam-3.ocaml.org was introduced as a temporary measure in 930e5b1 (#17), but that server will decommissioned quite soon (ocaml/infrastructure#19) so this will avoid build breakage for Coq.
@erikmd opam 2.1 has the following advantages:
Fixes: coq-community/docker-coq#38