[Sorry if you received this message multiple times...] 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)? Cheers, -- Stéphane
diff -Nru opam-2.0.3/debian/changelog opam-2.0.3/debian/changelog --- opam-2.0.3/debian/changelog 2019-02-01 12:05:09.000000000 +0100 +++ opam-2.0.3/debian/changelog 2020-02-18 07:42:31.000000000 +0100 @@ -1,3 +1,10 @@ +opam (2.0.3-1+deb10u1) buster; urgency=medium + + * Team upload + * Prefer mccs over aspcud (Closes: #908203) + + -- Stéphane Glondu <glo...@debian.org> Tue, 18 Feb 2020 07:42:31 +0100 + opam (2.0.3-1) unstable; urgency=medium * New (bugfix) upstream release diff -Nru opam-2.0.3/debian/control opam-2.0.3/debian/control --- opam-2.0.3/debian/control 2019-02-01 10:13:14.000000000 +0100 +++ opam-2.0.3/debian/control 2020-02-18 07:37:20.000000000 +0100 @@ -22,7 +22,7 @@ libopam-file-format-ocaml-dev, libjsonm-ocaml-dev, libopam-file-format-ocaml-dev, - aspcud, + mccs, rsync, unzip, openssl, @@ -50,7 +50,7 @@ ${misc:Depends}, opam-doc (= ${source:Version}), build-essential, - aspcud | mccs | packup, + mccs, opam-installer, bubblewrap [linux-any], unzip, diff -Nru opam-2.0.3/debian/gbp.conf opam-2.0.3/debian/gbp.conf --- opam-2.0.3/debian/gbp.conf 2018-12-02 12:53:29.000000000 +0100 +++ opam-2.0.3/debian/gbp.conf 2020-02-18 07:33:43.000000000 +0100 @@ -8,3 +8,5 @@ "src_ext", "ocp-build" ] +debian-branch = buster/master +upstream-branch = buster/upstream diff -Nru opam-2.0.3/debian/patches/0003-Prefer-mccs-over-aspcud.patch opam-2.0.3/debian/patches/0003-Prefer-mccs-over-aspcud.patch --- opam-2.0.3/debian/patches/0003-Prefer-mccs-over-aspcud.patch 1970-01-01 01:00:00.000000000 +0100 +++ opam-2.0.3/debian/patches/0003-Prefer-mccs-over-aspcud.patch 2020-02-18 07:40:53.000000000 +0100 @@ -0,0 +1,25 @@ +From: Martin Lucina <m...@users.noreply.github.com> +Date: Tue, 18 Feb 2020 07:37:04 +0100 +Subject: Prefer mccs over aspcud + +Bug-Debian: https://bugs.debian.org/908203 +Bug: https://github.com/ocaml/opam/issues/3827 +Origin: https://github.com/ocaml/opam/issues/3827#issuecomment-586945810 +--- + src/solver/opamCudfSolver.ml | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/src/solver/opamCudfSolver.ml b/src/solver/opamCudfSolver.ml +index 03486f1..b3b8aa6 100644 +--- a/src/solver/opamCudfSolver.ml ++++ b/src/solver/opamCudfSolver.ml +@@ -215,8 +215,8 @@ let make_custom_solver name args criteria = + + let default_solver_selection = + OpamBuiltinMccs.all_backends @ [ +- (module Aspcud: S); + (module Mccs: S); ++ (module Aspcud: S); + (module Aspcud_old: S); + (module Packup: S); + ] diff -Nru opam-2.0.3/debian/patches/series opam-2.0.3/debian/patches/series --- opam-2.0.3/debian/patches/series 2019-02-01 12:04:22.000000000 +0100 +++ opam-2.0.3/debian/patches/series 2020-02-18 07:40:53.000000000 +0100 @@ -1,2 +1,3 @@ 0002-Add-a-test-target.patch 0002-Fix-spelling-error-in-manpage.patch +0003-Prefer-mccs-over-aspcud.patch