From: Anil Madhavapeddy <anil@recoil.org>
To: Malcolm Matalka <mmatalka@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] opam update failing
Date: Sun, 7 Oct 2012 02:16:48 +0100 [thread overview]
Message-ID: <20121007011648.GF15159@dark.recoil.org> (raw)
In-Reply-To: <CAKziXDWqNeCjgUBCz=29arq0bOcWRrxWns85hR5iMGA262oZTg@mail.gmail.com>
On Sat, Oct 06, 2012 at 09:57:34PM +0200, Malcolm Matalka wrote:
> Hello! I did an opam update and after printing a list of packages
> that need upgrading I get:
>
> ...
> - ulex.1.1
> - variantslib.108.00.02
> - zed.1.2
> File /home/mmatalka/.opam/opam/ANSITerminal.0.6.opam: Bad format!
> Expecting list or list-list, got list({optio
> n(list({string("rm") string("setup.ml")}),{string("%{ocaml-version}%")
> symbol(=) string("4.00.0")}) option(lis
> t({string("oasis") string("setup")}),{string("%{ocaml-version}%")
> symbol(=) string("4.00.0")}) list({string("o
> caml") string("setup.ml") string("-configure") string("--prefix")
> string("%{prefix}%")}) list({string("ocaml")
> string("setup.ml") string("-build")}) list({string("ocaml")
> string("setup.ml") string("-install")})})
> 'opam update' failed
>
> and opam upgrade fails. Did a badly formated package sneak in somehow?
OPAM is still being hacked on pretty rapidly (although its getting very
stable in recent days!). The format of the repository changed between 0.6
and 0.7 to improve the constraint system, and so older clients wont
interoperate. Very recent OPAMs have a version check on the repository
also, so that they can detect future changes.
For immediate use, do not use the OPAM master branch as it is in the
middle of a refactoring, and stick to the tagged released versions instead
(0.7.5 works for me). I've just setup a Jenkins autobuilder which is
continuously building all the OPAM and packages under various operating
systems. I'll publish the build logs such as soon as I figure out how to
convince the Jenkins plugin API to give me a report in the right form...
--
Anil Madhavapeddy http://anil.recoil.org
next prev parent reply other threads:[~2012-10-07 1:16 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
2012-10-07 1:16 ` Anil Madhavapeddy [this message]
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=20121007011648.GF15159@dark.recoil.org \
--to=anil@recoil.org \
--cc=caml-list@inria.fr \
--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;
as well as URLs for NNTP newsgroup(s).