The Coq mailing list

[mukesh tiwari <mukeshtiwari.iiitm AT gmail.com>]

This is very interesting because I reckon I had a similar issue with coq-flocq [1], and the answer posted Guillaume (Laurent, in this thread)
worked for me. Today, I tried to install it again, and it went through without any problems.

➜  ~ opam install coq-flocq
The following actions will be performed:
  ∗ install conf-g++  1.0   [required by coq-flocq]
  ∗ install coq-flocq 3.3.1
===== ∗ 2 =====
Do you want to continue? [Y/n] Y

<><> Gathering sources ><><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
[coq-flocq.3.3.1] downloaded from https://gforge.inria.fr/frs/download.php/file/38329/flocq-3.3.1.tar.gz

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
∗ installed conf-g++.1.0
∗ installed coq-flocq.3.3.1
Done.
➜  ~ opam --version
2.0.7

Not sure if it's significant, but the only difference I see between my system and David's is that I use homebrew to install opam while David is using Macports.

[1] https://sympa.inria.fr/sympa/arc/coq-club/2019-05/msg00039.html

[2] https://gist.github.com/mukeshtiwari/305836a97118df55f44f0b7bc17c612c

On Sun, Aug 9, 2020 at 5:34 AM David Naumann <dnaumann AT stevens.edu> wrote:

Thanks for the info.  But I'm using opam 2.0.7.  I get opam updates via macports.

On 8/8/20, 5:06 AM, "Michael Soegtrop" <MSoegtrop AT yahoo.de> wrote:

    Hello David,

    I discussed this with Guillaume. He said that remake (which is used by
    Flocq) has indeed some kind of job server (but more fancy) and that opam
    sandboxing was to restrictive for this. This has been fixed in opam
    2.0.2 by:

    https://nam02.safelinks.protection.outlook.com/?url="https%3A%2F%2Fgithub.com%2Focaml%2Fopam%2Fpull%2F3663&amp;data=02%7C01%7Cdnaumann%40stevens.edu%7C415a783b6c6049a2849908d83b7a4e00%7C8d1a69ec03b54345ae21dad112f5fb4f%7C0%7C0%7C637324743774843050&amp;sdata=iF3zCqYqUGglk1OEYIU4AQEzK8QKYqB7yic9CQj6iS0%3D&amp;reserved=0
    Can you please check your opam version if you are indeed using 2.0.1
    (which is not that unlikely - 2.0.2 was released December 2018 and opam
    has afaik no self update mechanism)?

    I will add an opam version check to the coq-platform script to avoid
    such issues.

    Best regards,

    Michael