[new release] opam-monorepo (0.3.5)

[Leonidas-from-XIV]

Assemble and manage fully vendored Dune repositories

• Project page: https://github.com/tarides/opam-monorepo
• Documentation: https://tarides.github.io/opam-monorepo

CHANGES:

Changed

• Treat packages with no build commands as if they can be built with dune (Allow packages with no build commands tarides/opam-monorepo#355,
  @gridbugs)

Fixed

• Fix resolving refs of locally pinned repositories (failure with a pinned opam package tarides/opam-monorepo#326, Allow resolving unprefixed refs tarides/opam-monorepo#332, @hannesm,
  @Leonidas-from-XIV)
• Read the compiler flag from OPAM metadata thus classifying more packages
  correctly as base packages (Read package flags from OPAM metadata tarides/opam-monorepo#328, @Leonidas-from-XIV)
• Fix bug where dev repo urls ending with a "/" would result in
  opam monorepo pull placing package source code directly inside the duniverse
  directory instead of in a subdirectory of the duniverse directory (Fix bug where dev repo urls ending with a "/" would result in opam monorepo pull placing package source code directly inside the duniverse directory instead of in a subdirectory of the duniverse directory tarides/opam-monorepo#359,
  @gridbugs)

[raphael-proust]

CI errors:

• Some revdeps: mirage on 4.14 and 5.0. I don't know if it's related to this PR.
• Archlinux system package installation errors: should be fixed when updating the base image which should include some new maintainer keys. Not blocking IMO.
• opensuse system package installation error: I don't know opensuse well enough to tell, but that seems to be a transient network issue or maybe a docker image issue.

[kit-ty-kate]

The revdeps failures are related. This is because mirage uses opam-monorepo in its (recent) tests

[Leonidas-from-XIV]

Looks like the Arch Linux and OpenSUSE tests are unrelated issues.

The mirage failures are indeed unexpected and hint at the fact that the test-suite of opam-monorepo is not exercising the case that mirage is running into because I don't see how the changes between 0.3.4 and 0.3.5 would break it. It's possible something went wrong in this release.

[Leonidas-from-XIV]

Ok, after investigating the issue I think @kit-ty-kate's solution of restricting the version is correct.

It's not really a bug, rather a conscious change in opam-monorepo.0.3.5 that packages without build instructions are considered "virtual" and thus skipped. Mirage ran into this issue because the dummy packages it tests opam-monorepo against do not contain build stanzas.

I've made a PR to mirage to fix it in the future: mirage/mirage#1383

[Leonidas-from-XIV]

The conan failures are due to OCaml 5 rejecting the formatters in the conan test, so I've added a constraint: #22790

[kit-ty-kate]

Thanks! Sorry for the wait