Bug#908203: opam in buster

[Anil Madhavapeddy <anil@recoil.org>]

On 17 Feb 2020, at 23:25, Stéphane Glondu <glondu@debian.org> wrote:
> 
> Hello,
> 
> It has been brought to my attention that opam doesn't work in stable
> (buster) out of the box. This has been tracked in [1] (fixed in testing
> (bullseye)) and [2]. See in particular comments starting at [3].
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908203
> [2] https://github.com/ocaml/opam/issues/3827
> [3] https://github.com/ocaml/opam/issues/3827#issuecomment-586265289
> 
> Martin Lucina (@mato on GitHub) proposed some changes to improve the
> situation.
> 
> I've tested the following: "opam init" does not work properly without
> the changes (I've killed it because it consumes too much memory). With
> the changes, it fails (in a chroot) because bwrap fails, but "opam init
> --disable-sandboxing" works.
> 
> I've attached the proposed changes. I am considering submitting them to
> buster. Can someone review them and confirm that they work as expected
> (or, at least, that they improve the situation)?
> 

I have reviewed it (but not yet tested it with a binary package build) and
can confirm that it would certainly improve the situation. For all useful
purposes, aspcud no longer scales to the live opam repository, and mccs
does.  This will significantly improve opam in buster if applied.

regards,
Anil