From: Anil Madhavapeddy <anil@recoil.org>
To: Malcolm Matalka <mmatalka@gmail.com>
Cc: Mike McClurg <mike.mcclurg@gmail.com>,
T?r?k Edwin <edwin+ml-ocaml@etorok.net>,
caml-list@inria.fr
Subject: Re: [Caml-list] opam update failing
Date: Sun, 7 Oct 2012 02:28:53 +0100 [thread overview]
Message-ID: <20121007012853.GG15159@dark.recoil.org> (raw)
In-Reply-To: <CAKziXDWd=MAEYQb+72-n64sqr2tm5LeGMOYqycQx2W5jM+psog@mail.gmail.com>
On Sun, Oct 07, 2012 at 02:51:03AM +0200, Malcolm Matalka wrote:
> On a side note, I was very surprised when an 'opam upgrade' didn't
> actually bring me to the latest versions of everything. Specifically
> all of the jane st stuff was an older version than the latest. I
> ended up wiping my entire opam, "opam remove" was not working for me
> either, and starting from scratch, which worked. I'm sure that makes
> sense for someone that knows opam but I found it counter intuitive.
This is actually correct behaviour, although OPAM could explain its
reasoning to the user better.
The latest JSC packages (108.07.00+) introduced a backwards-incompatible
API change in type_conv. Type_conv is very commonly used by third-party
packages such as OASIS (via ODN) and would break if compiled against the
newest version.
Luckily, OPAM supports constraints on the package versions that let it
figure out a workable strategy, which in this case will use the older
version of type_conv. Since the Core suite has an exact dependency on
type_conv, this will also pin the rest of Core and Async to that older
version.
I've been patching a few of the type_conv packages to support the newer
API, and once these are merged [1], an 'opam upgrade' should recompile
your packages up to the latest version.
[1] https://github.com/OCamlPro/opam-repository/pull/107
--
Anil Madhavapeddy http://anil.recoil.org
next prev parent reply other threads:[~2012-10-07 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 19:57 Malcolm Matalka
2012-10-06 20:49 ` Török Edwin
2012-10-06 23:56 ` Mike McClurg
2012-10-07 0:22 ` Malcolm Matalka
2012-10-07 0:51 ` Malcolm Matalka
2012-10-07 1:28 ` Anil Madhavapeddy [this message]
2012-10-07 1:16 ` Anil Madhavapeddy
2012-10-07 7:48 ` Török Edwin
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=20121007012853.GG15159@dark.recoil.org \
--to=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=edwin+ml-ocaml@etorok.net \
--cc=mike.mcclurg@gmail.com \
--cc=mmatalka@gmail.com \
/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