Skip to content

Work around opam bug in make setup for opam < 2.2#2044

Merged
sim642 merged 1 commit into
masterfrom
dev-setup-opam-2.1
May 25, 2026
Merged

Work around opam bug in make setup for opam < 2.2#2044
sim642 merged 1 commit into
masterfrom
dev-setup-opam-2.1

Conversation

@sim642

@sim642 sim642 commented May 24, 2026

Copy link
Copy Markdown
Member

The nightly build immediately failed after merging #2036.
My guess is that this happens during make setup with opam version < 2.2.

Although with-dev-setup was supposed to be ignored by old opams, it's not with --locked: ocaml/opam#6946.
So this is a workaround that should still allow using opam < 2.2.

@sim642 sim642 added this to the v2.8.0 Clumsy Clurichaun milestone May 24, 2026
Copilot AI review requested due to automatic review settings May 24, 2026 07:42
@sim642 sim642 added bug setup Dependencies, CI, releasing labels May 24, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adjusts the make setup opam bootstrap flow to avoid an opam < 2.2 bug triggered by --locked when with-dev-setup is present, while keeping the intended locked dependency installation behavior.

Changes:

  • Replace opam switch create . --deps-only ... --locked with a two-step workaround: create the local switch with --no-install, then install dependencies from *.opam.locked.
  • Add inline documentation in make.sh explaining the opam bug and linking the upstream issue.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@sim642 sim642 merged commit c5d094f into master May 25, 2026
20 checks passed
@sim642 sim642 deleted the dev-setup-opam-2.1 branch May 25, 2026 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug setup Dependencies, CI, releasing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants