Le 21/05/2026 à 11:59, Paul Gevers a écrit :
Le 15/05/2026 à 07:02, Stéphane Glondu a écrit :
Trying the resulting ben on respighi, I faced a regression with
projectb import, which I fixed in ben 1.20. The resulting binaries can
be found in:
https://ocaml.debian.net/backports/20260514/repo/pool/ben/
I've just uploaded ben 1.21 to unstable, and also compiled it in the
repo above.
Can you maybe upload it to oldstable-backports-sloppy (and in
preparation for future upgrades of respighi to stable-backports) once it
migrate to enable us to just ask DSA to install it from there?
As said in my initial report, the toolchain and/or library stack changed
too much for unstable's ben to be built in bookworm (or trixie). It is
just easier for me to rebuild unstable's OCaml world in $ANY_SUITE. Due
to the static nature of OCaml linking, executables usually don't need
OCaml runtime libraries on so-called "native" architectures (which amd64
is). (Ben is peculiar as it uses plugins as "templates".)
Nonetheless, the changes that scratch my present itch are
cherry-pickable into bookworm's version:
https://salsa.debian.org/debian/ben/-/tree/bookworm
and are already in testing (version 1.20), one can just build it with
sbuild in a bookworm chroot... but I'm afraid this doesn't qualify for
an official backport, as it's a version that never existed anywhere.
The following works on respighi:
- extract (with dpkg -x) ben and libben-ocaml into ~/ben
I prefer we don't need to this (although not sure what others think).
I understand your reluctance, but this is the simplest I could find to
have latest ben in production, which is in principle a good idea (IMHO).
From comments in Makefile, this has already be done in the past.
Moreover, maybe this could motivate people to work more on the
tracker/monitor part of ben if they could see the effect quickly on the
release.debian.org website.
Cheers,
--
Stéphane
