caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Martin DeMello <martindemello@gmail.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
	"OCaml List" <caml-list@yquem.inria.fr>,
	"Vincent B." <vb@luminar.eu.org>
Subject: Re: [Caml-list] is this an opam bug or something i'm doing wrong?
Date: Wed, 27 Aug 2014 16:02:20 -0700	[thread overview]
Message-ID: <CAFrFfuFJhjc5urJ-CLniNHx14MdtWuuh2sr6+hQDtMP-OkKYTQ@mail.gmail.com> (raw)
In-Reply-To: <B6BAC2E3-B53B-4F30-9C2D-C097919861CE@recoil.org>

[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]

I managed to fix it by uninstalling opam-git and installing opam; the bug
seems to be that while the opam-git package did update to 1.1 it never
triggered an update to my installation.

martin


On Wed, Aug 27, 2014 at 3:48 PM, Anil Madhavapeddy <anil@recoil.org> wrote:

> According to the OPAM distributions list [1], Arch should be on OPAM
> 1.1.1, which points to the maintained default repo.
>
> I'm afraid I've never used Arch to know where you might turn to for help,
> but if it's really installing OPAM 1.0 then I'd like to know so that we can
> prevent any more new installations of that version.
>
> [1] https://github.com/ocaml/opam/wiki/Distributions
>
> -anil
>
> On 27 Aug 2014, at 21:28, Martin DeMello <martindemello@gmail.com> wrote:
>
> > Thanks! I've had to start from scratch anyway since for some reason the
> arch linux package had me stuck on the 1.0 version with a link to the wrong
> default repo (I only realised this when I tried to install oasis 0.4 and
> couldn't) and I messed something up trying to fix it in place, so I don't
> mind deleting .opam once more.
> >
> > martin
> >
> >
> > On Wed, Aug 27, 2014 at 2:27 AM, Daniel Bünzli <
> daniel.buenzli@erratique.ch> wrote:
> > Le mercredi, 27 août 2014 à 08:59, Martin DeMello a écrit :
> > > sorry for the noise, looks like a bug with the package itself :(
> should've checked for that first
> > >
> > > https://github.com/OCamlPro/ocp-indent/issues/142
> > This should be fixed but your opam may be in a state where it's not easy
> to apply the fix. Follow these instructions:
> >
> >
> https://github.com/ocaml/opam-repository/commit/55042c39fcef4f8b1c4e5db7b1120180bab05921#commitcomment-7540530
> >
> > Daniel
> >
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 2727 bytes --]

  reply	other threads:[~2014-08-27 23:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  7:18 Martin DeMello
2014-08-27  7:45 ` Martin DeMello
2014-08-27  7:59   ` Martin DeMello
2014-08-27  9:27     ` Daniel Bünzli
2014-08-27 20:28       ` Martin DeMello
2014-08-27 22:48         ` Anil Madhavapeddy
2014-08-27 23:02           ` Martin DeMello [this message]
2014-08-28  6:55             ` Vincent B.
2014-08-28  7:04               ` Martin DeMello
2014-08-27 12:53   ` Ashish Agarwal
2014-08-27 20:26     ` Martin DeMello
2014-08-27 22:55       ` Ashish Agarwal

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=CAFrFfuFJhjc5urJ-CLniNHx14MdtWuuh2sr6+hQDtMP-OkKYTQ@mail.gmail.com \
    --to=martindemello@gmail.com \
    --cc=anil@recoil.org \
    --cc=caml-list@yquem.inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --cc=vb@luminar.eu.org \
    /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).