From: Martin DeMello <martindemello@gmail.com>
To: "Vincent B." <vb@luminar.eu.org>
Cc: "Anil Madhavapeddy" <anil@recoil.org>,
"Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"OCaml List" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] is this an opam bug or something i'm doing wrong?
Date: Thu, 28 Aug 2014 00:04:30 -0700 [thread overview]
Message-ID: <CAFrFfuFa+FjQEOr8PNSq9TzCNp+RYM0UZn0sAT5qjFGV_PmwCw@mail.gmail.com> (raw)
In-Reply-To: <53FED248.1070505@luminar.eu.org>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Wed, Aug 27, 2014 at 11:55 PM, Vincent B. <vb@luminar.eu.org> wrote:
> On 28/08/2014 01:02, Martin DeMello wrote:
> > 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
> >
>
> Hi Martin,
>
> On Archlinux git packages are not upgraded on a package upgrade, there is
> no way
> AFAIK for the package manager to guess if a git package has been upgraded
> or not.
>
> So this is normal.
>
> I recommand using only the "opam-git" package on Archlinux until a new OPAM
> version is released.
True; I'm not sure what exactly went wrong in my case but opam-git never
updated anything, that is, it never recompiled the latest version even when
there were pushes to the git repo.
martin
[-- Attachment #2: Type: text/html, Size: 1257 bytes --]
next prev parent reply other threads:[~2014-08-28 7:04 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
2014-08-28 6:55 ` Vincent B.
2014-08-28 7:04 ` Martin DeMello [this message]
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=CAFrFfuFa+FjQEOr8PNSq9TzCNp+RYM0UZn0sAT5qjFGV_PmwCw@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