From: "Hezekiah M. Carty" <hez@0ok.org>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: "Ömer Sinan Ağacan" <omeragacan@gmail.com>, OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] opam package problem - can't install easy-format
Date: Fri, 22 Feb 2013 07:25:37 -0500 [thread overview]
Message-ID: <CAMfPyLCoc_vyF=aiNW0UKRaKmUVS2kbwmJJbtqiUe3v40yUR7w@mail.gmail.com> (raw)
In-Reply-To: <9887FE99-F0FA-4F3A-B415-D54A610E93B7@recoil.org>
On Fri, Feb 22, 2013 at 7:12 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> On 22 Feb 2013, at 12:08, Ömer Sinan Ağacan <omeragacan@gmail.com> wrote:
>>
>>> It's likely that you don't have the latest version of OPAM (0.9.3), since
>>> patch handling was changed to make it more robust. Do also let us know
>>> the compiler version you are running with in the bug report.
>>
>> You're right. I was still using a beta version of it even though I run
>> `opam upgrade`. Now I installed 0.9.3 and installation worked fine.
>
> OPAM doesn't upgrade itself, although we did flirt with the idea in the
> early versions. This will all cease to be a problem when the binary
> packages start flowing (already the case in Arch Linux, and soon a PPA
> on Ubuntu).
>
Given this lack of support - what is the proper way to upgrade opam?
Does it require using a different opam root? Is there an easy way to
dump the currently installed compilers + packages and easily ingest
this list into an upgraded opam?
Hez
next prev parent reply other threads:[~2013-02-22 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 11:41 Ömer Sinan Ağacan
2013-02-22 11:46 ` Anil Madhavapeddy
2013-02-22 12:08 ` Ömer Sinan Ağacan
2013-02-22 12:12 ` Anil Madhavapeddy
2013-02-22 12:25 ` Hezekiah M. Carty [this message]
2013-02-22 13:17 ` Anil Madhavapeddy
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='CAMfPyLCoc_vyF=aiNW0UKRaKmUVS2kbwmJJbtqiUe3v40yUR7w@mail.gmail.com' \
--to=hez@0ok.org \
--cc=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=omeragacan@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;
as well as URLs for NNTP newsgroup(s).