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

8 packages from ocaml/opam at 2.1.6 #25891

Merged
merged 1 commit into from
May 22, 2024

Conversation

kit-ty-kate
Copy link
Member

@kit-ty-kate kit-ty-kate commented May 16, 2024

This pull-request concerns:

  • opam-client.2.1.6: Client library for opam 2.1
  • opam-core.2.1.6: Core library for opam 2.1
  • opam-devel.2.1.6: Bootstrapped development binary for opam 2.1
  • opam-format.2.1.6: Format library for opam 2.1
  • opam-installer.2.1.6: Installation of files to a prefix, following opam conventions
  • opam-repository.2.1.6: Repository library for opam 2.1
  • opam-solver.2.1.6: Solver library for opam 2.1
  • opam-state.2.1.6: State library for opam 2.1


🐫 Pull-request generated by opam-publish v2.3.0

@kit-ty-kate kit-ty-kate changed the title 10 packages from ocaml/opam at 2.1.6 8 packages from ocaml/opam at 2.1.6 May 16, 2024
@mseri
Copy link
Member

mseri commented May 22, 2024

Do we need to do something about the opam-dune-lint failures? Are they related to this PR?

@kit-ty-kate
Copy link
Member Author

No, those are separate. It happens because this package is using the current opam state (which is 2.2 in CI) but it's trying to use an opam 2.1 library, so it fails during the test. If you want to fix them you can make the version constraint in opam-dune-lint match the version number of the current opam binary by doing:

  "opam-state" {>= "2.0" & < "2.1" & opam-version >= "2.0" & opam-version < "2.1"}
  "opam-state" {>= "2.1" & < "2.2" & opam-version >= "2.1" & opam-version < "2.2"}

@mseri mseri merged commit 8907d75 into ocaml:master May 22, 2024
1 of 2 checks passed
@mseri
Copy link
Member

mseri commented May 22, 2024

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants