Acknowledge that jacquev6's packages support OCaml 4.06.0

[jacquev6]

This reflects the following commits:

• jacquev6/General@df2a4f9#diff-ce1095cc45339eed28fa39a706eac56a
• jacquev6/JsOfOCairo@3912f73#diff-91a565848e6c3dd4496c366fd0be1393
• jacquev6/hashids-ocaml@78c1cc0#diff-537f3ffa3dd84ab6601fdf4a033a7b1f
• jacquev6/DrawGrammar@e8dc473#diff-16e2f48684fed3e20eecb51788c587d1

No code had to be modified to support of OCaml 4.06.0, so the
existing archives are usable as-is, and modifying the *.opam files
is enough.

My package sphinxcontrib-ocaml will require more work.

[camelus]

✅ All lint checks passed d7b1577

• These packages passed lint tests: DrawGrammar.0.2.1, General.0.4.0, JsOfOCairo.1.0.1, hashids.1.0.0

---

✅ Installability check (8296 → 8296)

[kit-ty-kate]

Does your packages depends on OCaml's internals to have those upper-bound constraints ?

[jacquev6]

@jpdeplaix I agree they should not, but 4.06.0 introduced a backward incompatibility : the num library now needs to be installed via opam. So as they were, my packages would have been broken for 4.06.0.

I remember having similar issues when porting my code from 4.02.3 to 4.05.0. That's why I said "< 4.06.0" in the first place, and why I consider safer to put "< 4.07.0" now. I'm open to suggestions though.

[kit-ty-kate]

I think it definitely better to just allow every upcoming versions and wait the checks before each releases. If there is a problem with any upcoming versions your opam file will be patched by the maintainers or by any contributors and you will be notified if something needs to be changed on your side.

But putting such constraints in advance because it might brake later (like any other packages btw) is probably too restrictive I think.

[jacquev6]

If there are automated checks for new OCaml versions, this sounds fine.

I just don't want to ever be in a situation where my packages end up broken, I don't know it and people don't know if it's my responsibility or if it comes from some other changes somewhere else.

I'll update this PR soon.

[jacquev6]

I've rebased my initial change and removed the upper version constraints.

[jacquev6]

For the "ci/datakit/5 V1.2 All Distros" check, the error is:

The following command needs to be run through "sudo":
    apt-get install -qq -yy libcairo2-dev libexpat1-dev libgtk2.0-dev
E: Unable to correct problems, you have held broken packages.
OS package installation failed

For the "1 arm64 V2.0 Build" check, the error is:

docker: Error response from daemon: connection error: desc = "transport: dial unix:///var/run/docker/containerd/docker-containerd.sock: timeout".

I have no idea how to help fixing these errors.

[samoht]

Do not worry about these errors, some bits of the CI is still experimental... The changes look good to me, merging.

[jacquev6]

Thanks @samoht!