+4

docs/failures/OCADml.md docs/failures/OCADml.0.2.1.md

reviewed

··· 13 13 **Root cause:** The package depends on the `cairo2` OCaml library at build time, but this dependency is not installed. The `cairo2` library (ocaml-cairo bindings) requires the system library `libcairo2-dev` and the opam package `cairo2`. 14 14 15 15 **Suggested fix:** Add `"cairo2"` to the `depends` field in the opam file. If it is already listed, check that the solver is including it. The `cairo2` opam package itself requires the `libcairo2-dev` depext. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, OCADml.0.6.0 builds successfully.

+4

docs/failures/OSCADml.md docs/failures/OSCADml.0.2.1.md

reviewed

··· 13 13 **Root cause:** Same as OCADml -- the `cairo2` OCaml library is not installed. OSCADml depends on both OCADml and cairo2. 14 14 15 15 **Suggested fix:** Add `"cairo2"` to the `depends` field in the opam file. The `cairo2` opam package requires the `libcairo2-dev` depext. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, OSCADml.0.2.3 builds successfully.

+4

docs/failures/advi.md docs/failures/advi.2.0.0.md

reviewed

··· 13 13 **Root cause:** The `camlimages.graphics` sub-library is not available. The `camlimages` package builds the `graphics` sub-library only when the `graphics` OCaml library is installed. On modern OCaml (>= 4.09), `graphics` is a separate opam package. 14 14 15 15 **Suggested fix:** Add `"graphics"` and ensure `"camlimages"` is built with graphics support in the opam `depends` field. May also need an upper bound on OCaml version or a version constraint on `camlimages` that provides the graphics sub-library. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + No later version available.

+4

docs/failures/aws-s3-async.4.4.0.md

reviewed

··· 13 13 **Root cause:** The package uses `Term.info` from cmdliner, which was removed in cmdliner >= 1.1.0. In newer cmdliner, `Term.info` was replaced by `Cmd.info`. 14 14 15 15 **Suggested fix:** Add an upper bound on cmdliner in the opam file: `"cmdliner" {< "1.1.0"}`. Alternatively, update the source code to use the new cmdliner API. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, aws-s3-async.4.8.1 builds successfully.

+4

docs/failures/aws-s3-async.4.5.1.md

reviewed

··· 13 13 **Root cause:** Same issue as aws-s3-async.4.4.0. The package uses the old cmdliner `Term.info` API which was removed in cmdliner >= 1.1.0. 14 14 15 15 **Suggested fix:** Add an upper bound on cmdliner: `"cmdliner" {< "1.1.0"}`. Alternatively, update the source code to the new cmdliner `Cmd` API. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, aws-s3-async.4.8.1 builds successfully.

+4

docs/failures/bap-arm.md docs/failures/bap-arm.2.5.0.md

reviewed

··· 16 16 ## Suggested fix 17 17 18 18 Ensure `bap-primus` is listed as a build dependency in the opam file. If it already is, the root failure is in the `bap-primus` package itself -- fix that first and this package will follow. 19 19 + 20 20 + ## Later versions 21 21 + 22 22 + No later version available.

+4

docs/failures/bap-constant-tracker.md docs/failures/bap-constant-tracker.2.3.0.md

reviewed

··· 16 16 ## Suggested fix 17 17 18 18 Regenerate the opam repository overlay in the base layer, ensuring all package directories are present. This is not a package-level issue -- it is a build infrastructure problem with the repository snapshot. 19 19 + 20 20 + ## Later versions 21 21 + 22 22 + Yes, bap-constant-tracker.2.5.0 builds successfully.

+4

docs/failures/bap-primus-greedy-scheduler.md docs/failures/bap-primus-greedy-scheduler.2.5.0.md

reviewed

··· 17 17 ## Suggested fix 18 18 19 19 Fix the `bap-primus` package build first. This package will then succeed. 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + No later version available.

+4

docs/failures/bap-primus-loader.md docs/failures/bap-primus-loader.2.3.0.md

reviewed

··· 16 16 ## Suggested fix 17 17 18 18 Regenerate the opam repository overlay in the base layer. This is a build infrastructure problem, not a package-level issue. 19 19 + 20 20 + ## Later versions 21 21 + 22 22 + Yes, bap-primus-loader.2.5.0 builds successfully.

+4

docs/failures/bap-primus-mark-visited.md docs/failures/bap-primus-mark-visited.2.3.0.md

reviewed

··· 17 17 ## Suggested fix 18 18 19 19 Ensure `bap-primus-track-visited` is in the opam depends. Fix the upstream BAP dependency that provides this package first. 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + Yes, bap-primus-mark-visited.2.5.0 builds successfully.

+4

docs/failures/bap-primus-symbolic-executor.md docs/failures/bap-primus-symbolic-executor.2.3.0.md

reviewed

··· 17 17 ## Suggested fix 18 18 19 19 Fix the upstream BAP dependency that provides `bap-primus-track-visited` first. 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + Yes, bap-primus-symbolic-executor.2.5.0 builds successfully.

+4

docs/failures/bap-primus-x86.md docs/failures/bap-primus-x86.2.4.0.md

reviewed

··· 17 17 ## Suggested fix 18 18 19 19 Fix `bap-x86` first. This package depends on it transitively. 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + Yes, bap-primus-x86.2.5.0 builds successfully.

+4

docs/failures/bap-relocatable.md docs/failures/bap-relocatable.2.4.0.md

reviewed

··· 17 17 ## Suggested fix 18 18 19 19 Fix `bap-x86` first. 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + Yes, bap-relocatable.2.5.0 builds successfully.

+4

docs/failures/bap-thumb.md docs/failures/bap-thumb.2.5.0.md

reviewed

··· 17 17 ## Suggested fix 18 18 19 19 Fix `bap-primus` and `bap-arm` first. This package depends on `bap-arm`. 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + No later version available.

+4

docs/failures/bap-x86.md docs/failures/bap-x86.2.4.0.md

reviewed

··· 17 17 ## Suggested fix 18 18 19 19 Ensure `bap-llvm` is in the install plan and builds successfully. It may require LLVM system libraries via depexts (e.g., `libllvm-dev`). 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + Yes, bap-x86.2.5.0 builds successfully.

+4

docs/failures/cairo2-gtk.md docs/failures/cairo2-gtk.0.6.5.md

reviewed

··· 27 27 ["x11proto-dev" "shared-mime-info" "libgtk2.0-dev"] {os-family = "debian"} 28 28 ] 29 29 ``` 30 30 + 31 31 + ## Later versions 32 32 + 33 33 + No later version available.

+4

docs/failures/cairo2-pango.md docs/failures/cairo2-pango.0.6.1.md

reviewed

··· 27 27 ["x11proto-dev" "shared-mime-info" "libgtk2.0-dev"] {os-family = "debian"} 28 28 ] 29 29 ``` 30 30 + 31 31 + ## Later versions 32 32 + 33 33 + Yes, cairo2-pango.0.6.5 builds successfully.

+4

docs/failures/catala-format.md docs/failures/catala-format.0.1.0.md

reviewed

··· 15 15 ["gettext"] {os-distribution = "debian"} 16 16 ] 17 17 ``` 18 18 + 19 19 + ## Later versions 20 20 + 21 21 + Yes, catala-format.1.1.0 builds successfully.

+4

docs/failures/ccbg.md docs/failures/ccbg.0.1.md

reviewed

··· 12 12 **Root cause:** curl exit code 60 indicates an SSL certificate verification failure. The source archive host (`git.zapashcanon.fr`) has an untrusted or expired TLS certificate. 13 13 14 14 **Suggested fix:** The upstream source URL needs to be updated in the opam repository to point to a working mirror, or the host's certificate needs to be renewed. This is an upstream/opam-repository metadata issue. 15 15 + 16 16 + ## Later versions 17 17 + 18 18 + No later version available.

+4

docs/failures/checkseum.0.0.2.md

reviewed

··· 29 29 ``` 30 30 depends: [ "cmdliner" {< "1.1.0"} ] 31 31 ``` 32 32 + 33 33 + ## Later versions 34 34 + 35 35 + Yes, checkseum.0.5.2 builds successfully.

+4

docs/failures/checkseum.0.1.0.md

reviewed

··· 34 34 ``` 35 35 depends: [ "cmdliner" {< "1.1.0"} ] 36 36 ``` 37 37 + 38 38 + ## Later versions 39 39 + 40 40 + Yes, checkseum.0.5.2 builds successfully.

+4

docs/failures/clangml.3.5.0.md

reviewed

··· 29 29 available: os-distribution != "debian" | os-version < "12" 30 30 depends: [ "ocaml" {< "4.08"} ] 31 31 ``` 32 32 + 33 33 + ## Later versions 34 34 + 35 35 + Yes, clangml.4.8.0 builds successfully.

+4

docs/failures/clangml.3.6.0.6.md

reviewed

··· 24 24 ``` 25 25 available: os-distribution != "debian" | os-version < "12" 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, clangml.4.8.0 builds successfully.

+4

docs/failures/clangml.3.7.0.2.md

reviewed

··· 24 24 ``` 25 25 available: os-distribution != "debian" | os-version < "12" 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, clangml.4.8.0 builds successfully.

+4

docs/failures/coccinelle.md docs/failures/coccinelle.1.0.8.md

reviewed

··· 22 22 ## Suggested fix 23 23 24 24 Add an upper bound on the OCaml version in the opam file: `"ocaml" {>= "4.02" & < "4.12"}`, or update to a newer coccinelle release that bundles a compatible stdcompat. 25 25 + 26 26 + ## Later versions 27 27 + 28 28 + Yes, coccinelle.1.3.0 builds successfully.

+4

docs/failures/cohttp-lwt-jsoo.2.5.8.md

reviewed

··· 25 25 ## Suggested fix 26 26 27 27 Fix the js_of_ocaml-compiler build first, or add an appropriate OCaml version constraint. No opam metadata change needed for cohttp-lwt-jsoo itself. 28 28 + 29 29 + ## Later versions 30 30 + 31 31 + Yes, cohttp-lwt-jsoo.6.2.1 builds successfully.

+4

docs/failures/conf-bap-llvm.md docs/failures/conf-bap-llvm.1.1.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 This version is too old to work on modern distributions. Add a version constraint on `conf-bap-llvm` to depend on a newer LLVM, or add an `available` filter to restrict to distributions that ship LLVM 4.0 or earlier. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, conf-bap-llvm.1.8 builds successfully.

+4

docs/failures/conf-libclang.md docs/failures/conf-libclang.13.md

reviewed

··· 16 16 ## Suggested fix 17 17 18 18 Add a depext for `llvm-13-dev` and `libclang-13-dev`, or update the package to accept LLVM 14+ which is available in Bookworm. Alternatively, add `depexts: [["libclang-13-dev" "llvm-13-dev"] {os-distribution = "debian"}]` if those packages exist in the archive. 19 19 + 20 20 + ## Later versions 21 21 + 22 22 + Yes, conf-libclang.21 builds successfully.

+4

docs/failures/conf-python-2-7.md docs/failures/conf-python-2-7.1.2.md

reviewed

··· 23 23 ``` 24 24 25 25 Alternatively, mark the package as unavailable since Python 2 is EOL everywhere. 26 26 + 27 27 + ## Later versions 28 28 + 29 29 + No later version available.

+4

docs/failures/conf-rust-2024.md docs/failures/conf-rust-2024.1.md

reviewed

··· 23 23 ``` 24 24 25 25 Alternatively, install Rust via rustup rather than the system package. 26 26 + 27 27 + ## Later versions 28 28 + 29 29 + No later version available.

+4

docs/failures/conjury.md docs/failures/conjury.2.1.1.md

reviewed

··· 19 19 ] 20 20 ``` 21 21 Alternatively, this may indicate the omake-based build system has incorrect search paths for system headers. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, conjury.2.2 builds successfully.

+4

docs/failures/coqide-8.12.2.md docs/failures/coqide.8.12.2.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Ensure `lablgtk3` and `lablgtk3-sourceview3` are installed and detected at configure time. If they cannot be installed, add version constraints to prevent this coqide version from being selected. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, coqide.8.20.1 builds successfully.

+4

docs/failures/coqide-8.17.1.md docs/failures/coqide.8.17.1.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Fix the `lablgtk3-sourceview3` build first. This is a cascading failure. 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, coqide.8.20.1 builds successfully.

+4

docs/failures/coqide-8.20.0.md docs/failures/coqide.8.20.0.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Fix the `lablgtk3-sourceview3` build first. 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, coqide.8.20.1 builds successfully.

+4

docs/failures/coqide-8.7.2.md docs/failures/coqide.8.7.2.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Ensure `lablgtk3` and `lablgtk3-sourceview3` are installed. Add appropriate version constraints if they cannot be built with the current compiler. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, coqide.8.20.1 builds successfully.

+4

docs/failures/coqide-8.8.0.md docs/failures/coqide.8.8.0.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Ensure `lablgtk3` and `lablgtk3-sourceview3` are installed. Add appropriate version constraints if they cannot be built with the current compiler. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, coqide.8.20.1 builds successfully.

+4

docs/failures/crlibm.md docs/failures/crlibm.0.2.md

reviewed

··· 22 22 ``` 23 23 patches: ["fix-scs-types.patch"] 24 24 ``` 25 25 + 26 26 + ## Later versions 27 27 + 28 28 + Yes, crlibm.0.5.1 builds successfully.

+4

docs/failures/crypt.md docs/failures/crypt.1.2.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Add depext for `libcrypt-dev` and patch the Makefile/build to ensure `-lcrypt` is passed during test linking. The package needs `depexts: [["libcrypt-dev"] {os-family = "debian"}]` and a build patch to fix the implicit declaration warning. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, crypt.2.1 builds successfully.

+4

docs/failures/devkit.md docs/failures/devkit.1.20210120.md

reviewed

··· 15 15 **Root cause:** The `Lwt_engine.abstract` class gained a new virtual method `id` in newer versions of lwt, and `devkit` does not implement it. Additionally, multiple Warning 6 errors (`labels-omitted`) indicate incompatibility with OCaml 5.x where `String.starts_with`/`String.ends_with` require labelled arguments. 16 16 17 17 **Suggested fix:** Add an upper bound on the OCaml version: `"ocaml" {< "5.0"}`, or add an upper bound on `lwt` to a version that does not require the `id` method. The package needs upstream updates for OCaml 5.x compatibility. 18 18 + 19 19 + ## Later versions 20 20 + 21 21 + Yes, devkit.1.20240429 builds successfully.

+4

docs/failures/dune-release.md docs/failures/dune-release.1.2.0.md

reviewed

··· 13 13 **Root cause:** `Result.result` was removed from the standard library in OCaml 4.13+. The type is now simply `result` (unqualified) or `Result.t`. This old version of dune-release is incompatible with modern OCaml. 14 14 15 15 **Suggested fix:** Add an upper bound on OCaml version: `"ocaml" {< "4.13"}`. This is a very old version of dune-release; upgrading to a newer version is the better solution. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, dune-release.2.2.0 builds successfully.

+4

docs/failures/electrod.md docs/failures/electrod.0.5.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Ensure `stdcompat` is listed in the opam `depends` field. If it is, verify that `stdcompat` itself builds successfully with the current compiler version. 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, electrod.1.0.0 builds successfully.

+4

docs/failures/eliom.md docs/failures/eliom.8.4.8.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Add a version constraint on `tyxml` in the opam file, e.g., `"tyxml" {< "4.6"}`, or upgrade to a newer eliom release that is compatible with the current tyxml. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, eliom.12.0.1 builds successfully.

+4

docs/failures/ffmpeg-0.2.1.md docs/failures/ffmpeg.0.2.1.md

reviewed

··· 26 26 ``` 27 27 28 28 Users should migrate to a newer version of the `ffmpeg` opam package. 29 29 + 30 30 + ## Later versions 31 31 + 32 32 + Yes, ffmpeg.1.2.8 builds successfully.

+4

docs/failures/ffmpeg-0.4.1.md docs/failures/ffmpeg.0.4.1.md

reviewed

··· 23 23 ``` 24 24 available: false # Incompatible with FFmpeg >= 5.0 25 25 ``` 26 26 + 27 27 + ## Later versions 28 28 + 29 29 + Yes, ffmpeg.1.2.8 builds successfully.

+4

docs/failures/fmlib_js.0.5.0.md

reviewed

··· 25 25 ## Suggested fix 26 26 27 27 Fix the js_of_ocaml-compiler build first, or add an appropriate OCaml version constraint. No opam metadata change needed for fmlib_js itself. 28 28 + 29 29 + ## Later versions 30 30 + 31 31 + Yes, fmlib_js.0.6.2 builds successfully.

+4

docs/failures/frama-c.md docs/failures/frama-c.26.1.md

reviewed

··· 21 21 ## Suggested fix 22 22 23 23 Check whether the `ivette` component requires additional depexts (e.g., `nodejs`, `yarn`). If Ivette is not needed, a newer frama-c version may handle this more gracefully. Consider adding `conf-nodejs` and `conf-yarn` to depexts if the install script requires them. 24 24 + 25 25 + ## Later versions 26 26 + 27 27 + Yes, frama-c.32.0 builds successfully.

+4

docs/failures/fswatch-0.1.1.md docs/failures/fswatch.11-0.1.1.md

reviewed

··· 24 24 ``` 25 25 26 26 Alternatively, add a depext pointing to the correct package name if it exists in third-party repos. 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, fswatch.11-0.1.5 builds successfully.

+4

docs/failures/fswatch-0.1.4.md docs/failures/fswatch.11-0.1.4.md

reviewed

··· 20 20 ``` 21 21 available: os-distribution != "debian" 22 22 ``` 23 23 + 24 24 + ## Later versions 25 25 + 26 26 + Yes, fswatch.11-0.1.5 builds successfully.

+4

docs/failures/fswatch-0.1.6.md docs/failures/fswatch.11-0.1.6.md

reviewed

··· 20 20 ``` 21 21 available: os-distribution != "debian" 22 22 ``` 23 23 + 24 24 + ## Later versions 25 25 + 26 26 + No later version available.

+4

docs/failures/gdbprofiler.md docs/failures/gdbprofiler.0.3.md

reviewed

··· 17 17 **Root cause:** Two issues: (1) Menhir's code back-end now requires explicit `%type` declarations, which this old jbuilder-era package does not provide. (2) `Yojson.Safe.json` was renamed to `Yojson.Safe.t` in newer yojson versions. 18 18 19 19 **Suggested fix:** Add upper bounds: `"menhir" {< "20211215"}` and `"yojson" {< "2.0.0"}` in the opam file. The package uses jbuilder and is too old for modern toolchain versions. 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + Yes, gdbprofiler.0.4 builds successfully.

+4

docs/failures/gitlab-jsoo.0.1.1.md

reviewed

··· 20 20 ## Suggested fix 21 21 22 22 Fix the js_of_ocaml-compiler build first. No opam metadata change needed for gitlab-jsoo itself. 23 23 + 24 24 + ## Later versions 25 25 + 26 26 + Yes, gitlab-jsoo.0.1.8 builds successfully.

+4

docs/failures/glpk.md docs/failures/glpk.0.1.6.md

reviewed

··· 23 23 ``` 24 24 depends: [ "ocaml" {< "5.0"} ] 25 25 ``` 26 26 + 27 27 + ## Later versions 28 28 + 29 29 + Yes, glpk.0.1.8 builds successfully.

+4

docs/failures/graphql-lwt.0.6.0.md

reviewed

··· 25 25 ``` 26 26 27 27 If it is already listed, check the solver output for version conflicts preventing its installation. 28 28 + 29 29 + ## Later versions 30 30 + 31 31 + Yes, graphql-lwt.0.14.0 builds successfully.

+4

docs/failures/hlarp.md docs/failures/hlarp.0.0.1.md

reviewed

··· 13 13 **Root cause:** The package uses `Term.pure` from cmdliner, which was renamed to `Term.const` in cmdliner >= 1.0.0. 14 14 15 15 **Suggested fix:** Add an upper bound on cmdliner: `"cmdliner" {< "1.0.0"}` in the opam file. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, hlarp.0.0.3 builds successfully.

+4

docs/failures/hugin.md docs/failures/hugin.1.0.0~alpha2.md

reviewed

··· 13 13 **Root cause:** The `cairo2` OCaml library is not installed. The package depends on cairo2 but it was not resolved by the solver. 14 14 15 15 **Suggested fix:** Ensure `"cairo2"` is in the `depends` field of the opam file. The `cairo2` opam package requires the `libcairo2-dev` depext. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + No later version available.

+4

docs/failures/js_of_ocaml-compiler.5.9.1.md

reviewed

··· 27 27 ``` 28 28 29 29 Or upgrade to a newer js_of_ocaml-compiler release that supports the installed OCaml version. 30 30 + 31 31 + ## Later versions 32 32 + 33 33 + Yes, js_of_ocaml-compiler.6.3.2 builds successfully.

+4

docs/failures/jupyter.2.6.1.md

reviewed

··· 24 24 ``` 25 25 depends: [ "ocaml" {< "5.0"} ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, jupyter.3.0.1 builds successfully.

+4

docs/failures/jupyter.2.7.0.md

reviewed

··· 24 24 ``` 25 25 depends: [ "ocaml" {< "5.0"} ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, jupyter.3.0.1 builds successfully.

+4

docs/failures/jupyter.2.7.2.md

reviewed

··· 24 24 ``` 25 25 depends: [ "ocaml" {< "5.0"} ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, jupyter.3.0.1 builds successfully.

+4

docs/failures/jupyter.2.7.3.md

reviewed

··· 24 24 ``` 25 25 depends: [ "ocaml" {< "5.0"} ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, jupyter.3.0.1 builds successfully.

+4

docs/failures/jupyter.2.7.7.md

reviewed

··· 24 24 ``` 25 25 depends: [ "ocaml" {< "5.0"} ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, jupyter.3.0.1 builds successfully.

+4

docs/failures/kappa-agents.md docs/failures/kappa-agents.4.1.0.md

reviewed

··· 23 23 ## Suggested fix 24 24 25 25 Ensure `kappa-library` is listed in the opam `depends` field and builds successfully. This is likely a cascading failure from `kappa-library` failing to build. 26 26 + 27 27 + ## Later versions 28 28 + 29 29 + Yes, kappa-agents.4.1.3 builds successfully.

+4

docs/failures/karamel.md docs/failures/karamel.1.0.0.md

reviewed

··· 17 17 ## Suggested fix 18 18 19 19 Add `fstar` as a dependency in the opam file, or add a depext/conf package for it. If fstar is not packaged in opam, the opam file should document this requirement and add an appropriate `available` constraint or post-message. 20 20 + 21 21 + ## Later versions 22 22 + 23 23 + No later version available.

+4

docs/failures/lablgl.md docs/failures/lablgl.1.05.md

reviewed

··· 24 24 ["freeglut3-dev"] {os-family = "debian"} 25 25 ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, lablgl.1.07 builds successfully.

+4

docs/failures/lablgtk.md docs/failures/lablgtk.2.18.12.md

reviewed

··· 29 29 ``` 30 30 31 31 The `x11proto-dev` package in Bookworm provides the merged xproto/renderproto/kbproto/xextproto headers. 32 32 + 33 33 + ## Later versions 34 34 + 35 35 + Yes, lablgtk.2.18.14 builds successfully.

+4

docs/failures/lablgtk3-sourceview3-3.0.beta4.md docs/failures/lablgtk3-sourceview3.3.0.beta4.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Ensure `lablgtk3` is in the opam `depends` field and builds successfully. The `lablgtk3` package requires GTK3 system libraries via depexts (`libgtk-3-dev`). 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, lablgtk3-sourceview3.3.1.5 builds successfully.

+4

docs/failures/lablgtk3-sourceview3-3.1.3.md docs/failures/lablgtk3-sourceview3.3.1.3.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Fix the `lablgtk3` package build first. 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, lablgtk3-sourceview3.3.1.5 builds successfully.

+4

docs/failures/lablgtk3-sourceview3-3.1.4.md docs/failures/lablgtk3-sourceview3.3.1.4.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Fix the `lablgtk3` package build first. 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, lablgtk3-sourceview3.3.1.5 builds successfully.

+4

docs/failures/llvm-11.0.0.md docs/failures/llvm.11.0.0.md

reviewed

··· 25 25 ``` 26 26 available: false # LLVM 11 not available in Debian Bookworm 27 27 ``` 28 28 + 29 29 + ## Later versions 30 30 + 31 31 + Yes, llvm.19-static builds successfully.

+4

docs/failures/llvm-15.0.7.md docs/failures/llvm.15.0.7+nnp-2.md

reviewed

··· 24 24 ``` 25 25 26 26 Or patch the script to `cd` to its own directory instead of checking. 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, llvm.19-static builds successfully.

+4

docs/failures/mastodon-archive-viewer.md docs/failures/mastodon-archive-viewer.0.3.md

reviewed

··· 20 20 ## Suggested fix 21 21 22 22 Add a version constraint on `cmdliner` in the opam file: `"cmdliner" {< "1.1.0"}`, or update the source code to use `Cmdliner.Term.const` instead of `pure`. 23 23 + 24 24 + ## Later versions 25 25 + 26 26 + Yes, mastodon-archive-viewer.0.4.0 builds successfully.

+4

docs/failures/mesh-graphics.md docs/failures/mesh-graphics.0.9.4.md

reviewed

··· 12 12 **Root cause:** The `graphics` library was removed from the OCaml standard distribution in OCaml 4.09 and moved to a separate opam package. This jbuilder-era package does not declare the dependency. 13 13 14 14 **Suggested fix:** Add `"graphics"` to the `depends` field in the opam file, or add an upper bound: `"ocaml" {< "4.09"}`. 15 15 + 16 16 + ## Later versions 17 17 + 18 18 + Yes, mesh-graphics.0.9.5 builds successfully.

+4

docs/failures/metapp.0.4.2.md

reviewed

··· 25 25 ``` 26 26 27 27 If this is a container issue, mount tmpfs with exec. No opam metadata change needed if the environment is fixed. 28 28 + 29 29 + ## Later versions 30 30 + 31 31 + Yes, metapp.0.4.4 builds successfully.

+4

docs/failures/metaquot.0.5.1.md

reviewed

··· 20 20 ## Suggested fix 21 21 22 22 Fix the metapp build first (see metapp.0.4.2.md). No opam metadata change needed for metaquot itself. 23 23 + 24 24 + ## Later versions 25 25 + 26 26 + Yes, metaquot.0.6.0 builds successfully.

+4

docs/failures/mpi.md docs/failures/mpi.1.06.md

reviewed

··· 26 26 ``` 27 27 28 28 Or patch the C stubs to use the new 3-argument form when building against OCaml >= 5.0. 29 29 + 30 30 + ## Later versions 31 31 + 32 32 + No later version available.

+4

docs/failures/ocaml-freestanding.md docs/failures/ocaml-freestanding.0.6.7.md

reviewed

··· 14 14 **Root cause:** The package requires at least one Solo5 bindings package to be installed. None of the supported Solo5 backend packages are present. 15 15 16 16 **Suggested fix:** Add a dependency on at least one Solo5 bindings package in the opam file, e.g., `"solo5-bindings-hvt" | "solo5-bindings-spt"` as a disjunction in `depends`. This is a Mirage unikernel support package that needs a specific target platform binding. 17 17 + 18 18 + ## Later versions 19 19 + 20 20 + No later version available.

+4

docs/failures/ocaml-protoc-plugin.md docs/failures/ocaml-protoc-plugin.0.9.md

reviewed

··· 14 14 **Root cause:** The `Pbrt.Encoder.key` function signature changed in a newer version of the `ocaml-protoc`/`pbrt` library. It now expects an `int` instead of a `(int * payload_kind)` tuple. 15 15 16 16 **Suggested fix:** Add an upper bound on `pbrt` or `ocaml-protoc` in the opam file to pin to a compatible version, e.g., `"ocaml-protoc" {< "3.0"}`. 17 17 + 18 18 + ## Later versions 19 19 + 20 20 + Yes, ocaml-protoc-plugin.6.2.0 builds successfully.

+4

docs/failures/ocaml-r.0.1.0.md

reviewed

··· 18 18 ["r-base-dev"] {os-distribution = "debian"} 19 19 ] 20 20 ``` 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, ocaml-r.0.6.0 builds successfully.

+4

docs/failures/ocaml-r.0.5.0.md

reviewed

··· 18 18 ["r-base-dev"] {os-distribution = "debian"} 19 19 ] 20 20 ``` 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, ocaml-r.0.6.0 builds successfully.

+4

docs/failures/ocamlformat.0.9.1.md

reviewed

··· 24 24 ``` 25 25 depends: [ "cmdliner" {< "1.1.0"} ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, ocamlformat.0.28.1 builds successfully.

+4

docs/failures/ocsigen-start-2.15.1.md docs/failures/ocsigen-start.2.15.1.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Add a version constraint on `lwt` in the opam file: `"lwt" {< "5.0"}`, or update to a newer ocsigen-start release that is compatible with lwt 5.x. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, ocsigen-start.8.0.0 builds successfully.

+4

docs/failures/ocsigen-start-2.16.1.md docs/failures/ocsigen-start.2.16.1.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Add `"lwt" {< "5.0"}` to the opam depends, or upgrade to a newer ocsigen-start release. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, ocsigen-start.8.0.0 builds successfully.

+4

docs/failures/ocsigen-start-2.18.0.md docs/failures/ocsigen-start.2.18.0.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Fix the `eliom` package build first. This is a cascading failure. Ensure `eliom` is listed in the opam depends and builds successfully. 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, ocsigen-start.8.0.0 builds successfully.

+4

docs/failures/ocsigen-start-2.21.1.md docs/failures/ocsigen-start.2.21.1.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Fix the `eliom` package build first. This is a cascading failure. 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, ocsigen-start.8.0.0 builds successfully.

+4

docs/failures/odepack.md docs/failures/odepack.0.7.md

reviewed

··· 16 16 **Root cause:** The bundled Fortran source code has type mismatches between `REAL(8)` and `INTEGER(4)` arguments at call sites. Modern gfortran (>= 10) treats these argument type mismatches as errors by default (previously only warnings). 17 17 18 18 **Suggested fix:** Add `-fallow-argument-mismatch` to the Fortran compiler flags, or add a version constraint on the package. In the opam file, this could be done via a patch or by setting `FFLAGS` in the build environment. 19 19 + 20 20 + ## Later versions 21 21 + 22 22 + Yes, odepack.0.7.1 builds successfully.

+4

docs/failures/orrandomForest.md docs/failures/orrandomForest.3.0.0.md

reviewed

··· 13 13 **Root cause:** The install step runs `R CMD BATCH install_randomForest.r` to install the R `randomForest` package, but this fails. This is likely because the R package installation requires network access (to download from CRAN) which is not available in the sandboxed build environment, or R library write permissions are insufficient. 14 14 15 15 **Suggested fix:** The opam package should pre-install the required R packages via depexts if available as system packages, e.g., `"r-cran-randomforest"` on Debian. Alternatively, the package needs to handle the case where the R package is already installed. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + No later version available.

+4

docs/failures/otaglibc.md docs/failures/otaglibc.0.1.0.md

reviewed

··· 21 21 ] 22 22 ``` 23 23 Note: Debian Bookworm ships TagLib 1.x, so the `>= 2.0.0` version requirement may not be satisfiable on this distribution. The package may need a version constraint or a newer distro. 24 24 + 25 25 + ## Later versions 26 26 + 27 27 + No later version available.

+4

docs/failures/owi.md docs/failures/owi.0.2.md

reviewed

··· 13 13 **Root cause:** The `hc` OCaml library (hash-consing library) is not installed. It is required by owi but was not resolved by the solver. 14 14 15 15 **Suggested fix:** Ensure `"hc"` is listed in the `depends` field of the opam file. If it is already listed, the solver may have failed to install it. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + No later version available.

+4

docs/failures/ppx_cstubs.0.6.1.1.md

reviewed

··· 24 24 ``` 25 25 depends: [ "containers" {< "3.0"} ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, ppx_cstubs.0.7.0 builds successfully.

+4

docs/failures/ppx_show.0.2.1.md

reviewed

··· 26 26 ``` 27 27 28 28 If it is already listed, the solver may have failed to install it -- check the solver output for conflicts. 29 29 + 30 30 + ## Later versions 31 31 + 32 32 + No later version available.

+4

docs/failures/ppx_test.1.8.0.md

reviewed

··· 26 26 ``` 27 27 28 28 If it is already listed, the solver may have failed to install it -- check the solver output for conflicts. 29 29 + 30 30 + ## Later versions 31 31 + 32 32 + No later version available.

+4

docs/failures/protocol-9p-tool.md docs/failures/protocol-9p-tool.0.11.2.md

reviewed

··· 14 14 **Root cause:** The `protocol-9p-unix` library is not installed. This is a co-installable package from the same project that provides Unix-specific 9P protocol support. 15 15 16 16 **Suggested fix:** Add `"protocol-9p-unix"` to the `depends` field in the opam file. 17 17 + 18 18 + ## Later versions 19 19 + 20 20 + Yes, protocol-9p-tool.2.1.0 builds successfully.

+4

docs/failures/proverif.md docs/failures/proverif.2.00.md

reviewed

··· 13 13 **Root cause:** `String.uppercase` was removed in OCaml 4.03+. It was replaced by `String.uppercase_ascii`. The build appeared to succeed but the binary was not produced, causing the install step to fail with `cp: cannot stat 'proverif': No such file or directory`. 14 14 15 15 **Suggested fix:** Add an upper bound on OCaml: `"ocaml" {< "5.0"}` or more accurately `{< "4.03"}` depending on when `String.uppercase` was fully removed. The package needs upstream patching to use `String.uppercase_ascii`. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, proverif.2.05 builds successfully.

+4

docs/failures/quill.md docs/failures/quill.1.0.0~alpha0.md

reviewed

··· 14 14 **Root cause:** Multiple missing dependencies: the `hugin` library (which itself fails to build due to missing `cairo2`), `cairo2`, and the `wasm_of_ocaml` compiler tool. 15 15 16 16 **Suggested fix:** Ensure the opam file includes `"hugin"`, `"cairo2"`, and `"wasm_of_ocaml-compiler"` in the `depends` field. The `hugin` dependency has its own build failure (missing cairo2), so fixing that is a prerequisite. 17 17 + 18 18 + ## Later versions 19 19 + 20 20 + Yes, quill.1.0.0~alpha2 builds successfully.

+4

docs/failures/raygui-1.3.0.md docs/failures/raygui.1.3.0.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Ensure `raylib` is listed as a dependency in the opam file and that a compatible version of `raylib` is installable. Since raylib itself fails to build (missing X11 depexts), fixing raylib's depexts will cascade to fix this package. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, raygui.1.6.0 builds successfully.

+4

docs/failures/raygui-1.3.1.md docs/failures/raygui.1.3.1.md

reviewed

··· 19 19 ## Suggested fix 20 20 21 21 Fix the raylib package's depexts (add `libxrandr-dev` etc.), which will allow raygui to build successfully. 22 22 + 23 23 + ## Later versions 24 24 + 25 25 + Yes, raygui.1.6.0 builds successfully.

+4

docs/failures/raylib-1.0.0.md docs/failures/raylib.1.0.0.md

reviewed

··· 24 24 ["libxrandr-dev" "libxcursor-dev" "libxi-dev" "libxinerama-dev"] {os-family = "debian"} 25 25 ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, raylib.1.5.1 builds successfully.

+4

docs/failures/raylib-1.1.0.md docs/failures/raylib.1.1.0.md

reviewed

··· 24 24 ["libxrandr-dev" "libxcursor-dev" "libxi-dev" "libxinerama-dev"] {os-family = "debian"} 25 25 ] 26 26 ``` 27 27 + 28 28 + ## Later versions 29 29 + 30 30 + Yes, raylib.1.5.1 builds successfully.

+4

docs/failures/raylib-1.6.0.md docs/failures/raylib.1.6.0.md

reviewed

··· 25 25 ["libxrandr-dev" "libxcursor-dev" "libxi-dev" "libxinerama-dev"] {os-family = "debian"} 26 26 ] 27 27 ``` 28 28 + 29 29 + ## Later versions 30 30 + 31 31 + No later version available.

+4

docs/failures/refl.0.2.0.md

reviewed

··· 30 30 ## Suggested fix 31 31 32 32 Fix the metapp build first (see metapp.0.4.2.md). The rest of the chain (traverse, metaquot, refl) will resolve. 33 33 + 34 34 + ## Later versions 35 35 + 36 36 + Yes, refl.0.4.1 builds successfully.

+4

docs/failures/so.md docs/failures/so.0.0.1.md

reviewed

··· 12 12 **Root cause:** curl exit code 60 indicates an SSL certificate verification failure. The source archive host (`fs.zapashcanon.fr`) has an untrusted or expired TLS certificate. 13 13 14 14 **Suggested fix:** The upstream source URL needs to be updated in the opam repository to point to a working mirror, or the host's certificate needs to be renewed. This is an upstream/opam-repository metadata issue. 15 15 + 16 16 + ## Later versions 17 17 + 18 18 + No later version available.

+4

docs/failures/starpath.0.1.2.md

reviewed

··· 25 25 ``` 26 26 27 27 Alternatively, if the source exists at a different URL, update the `url` section in the opam file. 28 28 + 29 29 + ## Later versions 30 30 + 31 31 + No later version available.

+4

docs/failures/statocaml_community.md docs/failures/statocaml_community.0.1.0.md

reviewed

··· 13 13 **Root cause:** The `statocaml_plots` library is not installed. It is likely a co-installable package from the same project. 14 14 15 15 **Suggested fix:** Add `"statocaml_plots"` to the `depends` field in the opam file. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + No later version available.

+4

docs/failures/stk.md docs/failures/stk.0.1.0.md

reviewed

··· 20 20 **Root cause:** Two issues: (1) `Yojson.Safe.t` no longer includes `Tuple` and `Variant` constructors in yojson >= 2.0. (2) The `tsdl` library added new event types (e.g., `Locale_changed`) that are not handled in the pattern match. 21 21 22 22 **Suggested fix:** Add upper bounds: `"yojson" {< "2.0.0"}` and `"tsdl" {< "1.0.0"}` (or whichever version added the new events) in the opam file. 23 23 + 24 24 + ## Later versions 25 25 + 26 26 + Yes, stk.0.5.0 builds successfully.

+4

docs/failures/stk_rdf.md docs/failures/stk_rdf.0.2.0.md

reviewed

··· 13 13 **Root cause:** The `stk` library is not installed. This is because `stk.0.1.0` itself fails to build (see stk.md). `stk_rdf` depends on `stk` which is broken. 14 14 15 15 **Suggested fix:** Fix the `stk` package first (yojson/tsdl compatibility issues). Once `stk` builds, `stk_rdf` should also build. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, stk_rdf.0.5.0 builds successfully.

+4

docs/failures/topiary.md docs/failures/topiary.0.2.1.md

reviewed

··· 11 11 **Root cause:** The Rust toolchain on the system (rustc 1.63.0, from Debian Bookworm) is too old. The `clap_builder` Rust crate dependency requires rustc >= 1.64.0. 12 12 13 13 **Suggested fix:** Add a depext or version constraint that ensures a sufficiently new Rust compiler. On Debian, this may require using `rustup` rather than the system rustc. In the opam file, add a constraint like `"conf-rust-2021"` or document the minimum Rust version requirement. 14 14 + 15 15 + ## Later versions 16 16 + 17 17 + Yes, topiary.0.6.0 builds successfully.

+4

docs/failures/traverse.0.2.0.md

reviewed

··· 25 25 ## Suggested fix 26 26 27 27 Fix the metapp build first (see metapp.0.4.2.md). No opam metadata change needed for traverse itself. 28 28 + 29 29 + ## Later versions 30 30 + 31 31 + Yes, traverse.0.3.0 builds successfully.

+4

docs/failures/unison.md docs/failures/unison.2.51.5.md

reviewed

··· 13 13 **Root cause:** The `lablgtk2` library (OCaml bindings for GTK2) is not installed. Unison tries to build a GTK2 GUI frontend but the dependency is missing. 14 14 15 15 **Suggested fix:** Add `"lablgtk"` to the `depends` field in the opam file, along with the depext `"libgtk2.0-dev"`. Alternatively, if the GTK frontend is optional, the build system should be modified to skip it when lablgtk2 is not available. 16 16 + 17 17 + ## Later versions 18 18 + 19 19 + Yes, unison.2.53.8 builds successfully.

+4

docs/failures/uri.1.9.7.md

reviewed

··· 27 27 ``` 28 28 29 29 Or upgrade to a newer version of uri that does not depend on the `bytes` package. 30 30 + 31 31 + ## Later versions 32 32 + 33 33 + Yes, uri.4.4.0 builds successfully.

+4

docs/failures/vhd-format.md docs/failures/vhd-format.0.12.0.md

reviewed

··· 20 20 **Root cause:** `Cstruct.len` was removed in cstruct >= 6.2.0. It was replaced by `Cstruct.length`. 21 21 22 22 **Suggested fix:** Add an upper bound on cstruct: `"cstruct" {< "6.2.0"}` in the opam file. Alternatively, patch the source to use `Cstruct.length`. 23 23 + 24 24 + ## Later versions 25 25 + 26 26 + Yes, vhd-format.0.13.0 builds successfully.

+4

docs/failures/why3-ide.md docs/failures/why3-ide.1.6.0.md

reviewed

··· 18 18 ## Suggested fix 19 19 20 20 Ensure `lablgtk3` is in the opam `depends` field and builds successfully. Fix the `lablgtk3` build first -- this is a cascading failure from `lablgtk3` not being available. 21 21 + 22 22 + ## Later versions 23 23 + 24 24 + Yes, why3-ide.1.8.2 builds successfully.

+4

docs/failures/z3-4.7.1.md docs/failures/z3.4.7.1.md

reviewed

··· 22 22 ``` 23 23 24 24 Users should use a newer z3 version that supports Python 3. 25 25 + 26 26 + ## Later versions 27 27 + 28 28 + Yes, z3.4.15.2 builds successfully.

+4

docs/failures/z3-4.8.14.md docs/failures/z3.4.8.14.md

reviewed

··· 22 22 ``` 23 23 depends: [ "ocaml" {< "5.0"} ] 24 24 ``` 25 25 + 26 26 + ## Later versions 27 27 + 28 28 + Yes, z3.4.15.2 builds successfully.

+4

docs/failures/z3-4.8.9.md docs/failures/z3.4.8.9-1.md

reviewed

··· 20 20 ``` 21 21 22 22 Users should use z3 >= 4.8.14 which uses Python 3. 23 23 + 24 24 + ## Later versions 25 25 + 26 26 + Yes, z3.4.15.2 builds successfully.