!pinned flag should not be used in opam package for releases #208
Labels
Comments
|
Thanks for the report @palmskog , note the comment of @kit-ty-kate here too:
It is a bit unclear to me how to best solve this, ideally we would not have to add some extra release step to the current standard |
|
The error seems to have evolved in the latest release, we now just get Coq not installed in OPAM's CI due to the package being pinned? ocaml/opam-repository#17070 (comment) |
ejgallego
added a commit
that referenced
this issue
May 2, 2024
We also remove the old !pinned method, as the setup-ocaml action does pin Coq in all cases. Fixes #208
ejgallego
added a commit
that referenced
this issue
May 2, 2024
We also remove the old !pinned method, as the setup-ocaml action does pin Coq in all cases. Fixes #208
ejgallego
added a commit
that referenced
this issue
May 2, 2024
We also remove the old !pinned method, as the setup-ocaml action does pin Coq in all cases. Fixes #208
ejgallego
added a commit
that referenced
this issue
May 2, 2024
We also remove the old !pinned method, as the setup-ocaml action does pin Coq in all cases. Fixes #208
ejgallego
added a commit
that referenced
this issue
May 2, 2024
We also remove the old !pinned method, as the setup-ocaml action does pin Coq in all cases. Fixes #208
ejgallego
added a commit
that referenced
this issue
May 2, 2024
We also remove the old !pinned method, as the setup-ocaml action does pin Coq in all cases. Fixes #208
ejgallego
added a commit
that referenced
this issue
May 2, 2024
We also remove the old !pinned method, as the setup-ocaml action does pin Coq in all cases. Fixes #208
ejgallego
added a commit
that referenced
this issue
May 2, 2024
We also remove the old !pinned method, as the setup-ocaml action does pin Coq in all cases. Fixes #208
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
!pinnedflag is currently used in the version-tracked opam package definition (coq-serapi.opam).However, this flag seemingly causes CI failures in the upstream opam repository, so it should never be part of opam package definitions for released versions of SerAPI (that are submitted to this opam repo). This should be accomplished with release automation, to avoid having to manual edit the opam file.
Some more background: ocaml/opam-repository#16564
The text was updated successfully, but these errors were encountered: