Hi,

On 16/06/2024 06:36, Stéphane Glondu wrote:
Source: ocaml
Severity: normal
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-5.2.0-transition

Hi all,

As you may have seen from my recent commits and uploads, I've started
to prepare the transition of OCaml from the version currently in
unstable, 4.14.1, to 5.2.0.

The 5.x series feature a rewrite of significant parts of the runtime
to support multicore and effects.

I've uploaded 5.2.0-1~exp1 to experimental:

   
https://buildd.debian.org/status/package.php?p=ocaml&suite=experimental&compact=compact

It FTBFS on armel, m68k and ppc64 (and has not yet been built on alpha
and hurd-amd64):
- for armel, I've submitted a bug report upstream:
   https://github.com/ocaml/ocaml/issues/13234
- for ppc64, the failure is due to ppc64 not being a native arch any
   more
- I have not yet investigated the other failures

I've rebuilt all (relevant) packages with this new version; the
results are available at the following address:

   http://ocaml.debian.net/transitions/ocaml-5.2.0/

In particular, there are currently 117 (out of 390) missing packages,
mostly because of FTBFS (or exhaustion of allocated resources). A
graphical visualisation of the situation can be seen at:

   http://ocaml.debian.net/transitions/ocaml-5.2.0/missing.pdf

I'm now asking for help from other maintainers to improve the
situation... I've identified 3 big clusters:
- camlp4/ocamlnet: I will have a look in the next weeks
- elpi/ssreflect: Julien, can you have a look?
- liquidsoap: Kyle, can you have a look?


Liquidsoap is currently broken due #1064128. I am waiting for a fix from upstream, which should hopefully be in the next month or so. Looking over upstream's bug tracker, there doesn't seem to be much blocking OCaml 5. I see only 1 report of something failing [1], and it is unclear if that is directly related to the OCaml version.

[1] https://github.com/savonet/liquidsoap/issues/3936

Cheers
Kyle

--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze
⢿⡄⠘⠷⠚⠋⠀ Debian Developer
⠈⠳⣄⠀⠀⠀⠀ https://wiki.debian.org/KyleRobbertze

Reply via email to