From: "Jocelyn Sérot" <jocelyn.serot@uca.fr>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] the nocrypto package prevents building opam2 publish plugin
Date: Thu, 14 Feb 2019 18:39:33 +0100 [thread overview]
Message-ID: <201D6443-0DDB-424B-9D99-75121CA39985@uca.fr> (raw)
In-Reply-To: <CALdWJ+z9mOhkPBfj6F=o5GxxRDxxwBzSmA=SAxB=RVpvO+mqPg@mail.gmail.com>
Hi,
I’ve cross-posted the issue on the opam2 [1] and nocrypto [2] tracking systems but got no feedback.
Has anybody already encountered this problem ?
Using the opam2 publish plugin was my main motivation for switching to opam2 :/
Jocelyn
[1] https://github.com/ocaml/opam-repository/issues/13363
[2] https://github.com/mirleft/ocaml-nocrypto/issues/154
next prev parent reply other threads:[~2019-02-14 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 5:39 [Caml-list] FrontC package Kenneth Adam Miller
2019-01-22 14:15 ` Ivan Gotovchits
2019-01-22 14:28 ` Kenneth Adam Miller
2019-01-22 15:40 ` Ivan Gotovchits
2019-01-22 15:57 ` Kenneth Adam Miller
2019-01-22 16:13 ` Ivan Gotovchits
2019-02-14 17:39 ` Jocelyn Sérot [this message]
2019-02-14 21:05 ` [Caml-list] the nocrypto package prevents building opam2 publish plugin Daniel Bünzli
[not found] ` <0CA4CC4F-23C9-42F6-BDE3-0728F9F57E33@uca.fr>
2019-02-15 9:30 ` Jocelyn Sérot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201D6443-0DDB-424B-9D99-75121CA39985@uca.fr \
--to=jocelyn.serot@uca.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).