Hi everyone, OCaml 4.07.0 is not far from being released, and, as usual, some opam packages need some adjustments or a new compatible release. To be able to track which packages need fixes I’m please to offer the following webpage which tries to summaries this: http://check.ocamllabs.io/ This bl…

@Chris00 @perry @rixed Filter over maintainers is now available. For example: http://51.145.134.72/?compilers=4.05.0%3A4.06.1%3A4.07.0%2Bbeta2&show-available=4.05.0%3A4.06.1%3A4.07.0%2Bbeta2&maintainers=kate

Nice job, @kit-ty-kate ! This tool is so awesome! Would it be even remotely possible to implement a sort by rev-dep count? That would indicate the highest priority items for the community to update.

Thanks @kit-ty-kate , after all these systems eventually one that has exactly the right set of filters a maintainer needs. One last thing however, the notion of failure is wrong not precise enough e.g. on this page , vg is not to blame, it’s its js-of-ocaml dependency, this should be distinguished so…

[image] dbuenzli: One last thing however, the notion of failure is wrong not precise enough e.g. on this page , vg is not to blame, it’s its js-of-ocaml dependency, this should be distinguished somehow. Fixed and deployed. I’ve introduced a partial failure state and they are displayed as oran…

Thanks very much ! [image] kit-ty-kate: I’ll maybe add some other filters to filter out partial failures at some point but I’m not sure that’s needed. As far as I’m concerned I don’t think it’s needed. I’m interested in knowing one of my package is still failing, but I just wanted to know it…

Btw. I’m not sure also whether you can distinguish this. But for example this error http://51.145.134.72/4.05.0/bad/ocaml-manual.4.05.0 seems to be an infrastructure problem not a problem with the package itself.

[image] dbuenzli: Btw. I’m not sure also whether you can distinguish this. But for example this error http://51.145.134.72/4.05.0/bad/ocaml-manual.4.05.0 seems to be an infrastructure problem not a problem with the package itself. In this case it’s not an infrastructure problem, it’s the chec…

Are you sure ? I just tried locally and it installed without problem (and git log -- packages/ocaml-manual tells me it has not been altered since published).

mmh weird, I can install it locally but the archive checksums are all over the place: Checksum required: 1649c91a84fd35444192d6a55f932939 Checksum from the upstream-archive: 724ac6f96f019999cb83d95adafdda8e Checksum from the opam-archive-mirror: f872fc1411f8190ebc59343c84d464b4

Thanks for your work @kit-ty-kate ! I’m trying to figure out why benchmark 1.3.1 (for example) is red on OCaml 4.06.1 despite the constraint available: [ ocaml-version < "4.06.0" ] . Any help will be appreciated.

[ANN] opam-check-all: Are your packages broken for the upcoming OCaml releases?

Ecosystem

kit-ty-kate June 12, 2018, 8:43am 28

The service now has a proper domain name: http://check.ocamllabs.io/

Topic		Replies	Views
Check opam's health for the upcoming OCaml release (4.08) Ecosystem opam	3	1582	May 5, 2019
[ANN] opam-ci: first release of a tool to check the health of your packages Ecosystem opam , announce	3	2069	June 23, 2018
Check.ocamllabs.io: New features and call to rename Ecosystem opam	11	1944	October 20, 2020
Serious OPAM package quality issues Community opam , user-feedback	58	7617	September 25, 2017
[help wanted] crowd-sourcing package build fixes in opam-repository Community	15	1743	March 4, 2019

[ANN] opam-check-all: Are your packages broken for the upcoming OCaml releases?

Related topics