From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id 60DD47EDD9 for ; Sun, 7 Oct 2012 09:48:17 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of edwin+ml-ocaml@etorok.net) identity=pra; client-ip=176.9.138.55; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="edwin+ml-ocaml@etorok.net"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of edwin+ml-ocaml@etorok.net designates 176.9.138.55 as permitted sender) identity=mailfrom; client-ip=176.9.138.55; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="edwin+ml-ocaml@etorok.net"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of postmaster@mail.etorok.net designates 176.9.138.55 as permitted sender) identity=helo; client-ip=176.9.138.55; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="postmaster@mail.etorok.net"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EANsycVCwCYo3/2dsb2JhbABFgm68NIEIgiABAQVAAQE2Ag8LGAkWDwkDAgECAUUTCAKIAgOmL4QyAQWOHwaLTyeCSIMhiFWNGYEVjxmCcIFZ X-IronPort-AV: E=Sophos;i="4.80,547,1344204000"; d="scan'208";a="176131905" Received: from mail.etorok.net ([176.9.138.55]) by mail1-smtp-roc.national.inria.fr with ESMTP; 07 Oct 2012 09:48:16 +0200 Received: from [IPv6:2a02:2f02:1022:a264:1e6f:65ff:fe23:db0d] (unknown [IPv6:2a02:2f02:1022:a264:1e6f:65ff:fe23:db0d]) by mail.etorok.net (Postfix) with ESMTPSA id B08B146AE for ; Sun, 7 Oct 2012 09:48:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=etorok.net; s=MAILOUT; t=1349596095; bh=QhlIliGrFx3KSFMhNiTQ7DzkphvDGIZq6Btxut7qLwo=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=XO8VrNjrlBKrIaWVPtTZgofhjhTB3APR1rdY1wTmtS5kBmBMLlfIaGWsqPhXkOM0l 60Dd0UKoqJi5XhPYxYuCQyclY20NlMSyAGtN1Jzg17EXQ+jv23gCBEg9ka/en0l5/N gloTa06Xjk6GRqO5lRFmTHyODTsnb0wRk86NwG5g= Message-ID: <507133BC.6040802@etorok.net> Date: Sun, 07 Oct 2012 10:48:12 +0300 From: =?ISO-8859-1?Q?T=F6r=F6k_Edwin?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.7) Gecko/20120922 Icedove/10.0.7 MIME-Version: 1.0 To: caml-list@inria.fr References: <20121007011648.GF15159@dark.recoil.org> In-Reply-To: <20121007011648.GF15159@dark.recoil.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.5 at mail X-Virus-Status: Clean Subject: Re: [Caml-list] opam update failing On 10/07/2012 04:16 AM, Anil Madhavapeddy wrote: > 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 see that 'opam' can be installed using opam (latest is 0.7.4 though), does this mean it supports upgrading itself? If so would it be possible to automatically install 'opam' as a package when you install opam? Then opam update would show when a new version is available, and upgrade could be used to upgrade it. Thanks, --Edwin