From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id C8BBF7FCCB for ; Fri, 27 Mar 2015 19:54:24 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of agarwal1975@gmail.com) identity=pra; client-ip=74.125.82.51; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of agarwal1975@gmail.com designates 74.125.82.51 as permitted sender) identity=mailfrom; client-ip=74.125.82.51; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wg0-f51.google.com) identity=helo; client-ip=74.125.82.51; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="postmaster@mail-wg0-f51.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DDAABQphVVlDNSfUpcg1haBIMPsiOGLYdmgX+FdQKBMgdMAQEBAQEBEQEBAQEHCwsJEjCEFAEBAQMBEhEdARsSCwEDDAYDAgsNDR0CAiIBEQEFAQoSBhMSEId4AQMJCA2VPJBWPjGLMYFrgnePJAoZJwMJAVSEbQEBAQEBAQQBAQEBAQEBARQBBQ6LGoQ2PgQHgmiBRQWFDQqBA44shgGBGzqLZYMvgX4SI4EMCYF9JxyBbCIxAYEDgT8BAQE X-IPAS-Result: A0DDAABQphVVlDNSfUpcg1haBIMPsiOGLYdmgX+FdQKBMgdMAQEBAQEBEQEBAQEHCwsJEjCEFAEBAQMBEhEdARsSCwEDDAYDAgsNDR0CAiIBEQEFAQoSBhMSEId4AQMJCA2VPJBWPjGLMYFrgnePJAoZJwMJAVSEbQEBAQEBAQQBAQEBAQEBARQBBQ6LGoQ2PgQHgmiBRQWFDQqBA44shgGBGzqLZYMvgX4SI4EMCYF9JxyBbCIxAYEDgT8BAQE X-IronPort-AV: E=Sophos;i="5.11,480,1422918000"; d="scan'208";a="107426182" Received: from mail-wg0-f51.google.com ([74.125.82.51]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 27 Mar 2015 19:54:24 +0100 Received: by wgra20 with SMTP id a20so108614156wgr.3 for ; Fri, 27 Mar 2015 11:54:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=m+tk9wIu6vHXwzoCqv41756+l1g6y2/Wpq+7cFKLNys=; b=STEL35+lKIxhSr4/WKYeZ1u8bTiFVykYgH/pUqSkAecRqjxfrR3cRWwd0GobqJCYYT Pl09K1HAmb6RqhgI7iuCI3cIQlyW8GJTaIEiV1HC78Jyzn5XIhykGWWjkHAPh2kH57Fg lh+xrmOrslGOG/F/ohHIKxZHwcLA3VhglC0zH/1aQr8DIwQ5bKvdSZZpq2V/1nnRymrZ 31bEQgxtSrH+U/9tq8+85e1H8KO0SPGtpJfFrCB3ldWs6C5ZJHZHZ3XxjFINJ2mmCPmO csNmx7KA6QXcNapVOYeuMAK16UgsdFr38hK3lLw7DwwXf4yZXNBdXlB728uPi17UK1gO KZSQ== X-Received: by 10.181.27.201 with SMTP id ji9mr473388wid.20.1427482463807; Fri, 27 Mar 2015 11:54:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.27.45.17 with HTTP; Fri, 27 Mar 2015 11:54:03 -0700 (PDT) In-Reply-To: <5515A183.3020709@freenet.de> References: <2162350.aHZvdojE6Q@agaric> <55159AD3.7050507@freenet.de> <5515A183.3020709@freenet.de> From: Ashish Agarwal Date: Fri, 27 Mar 2015 14:54:03 -0400 Message-ID: To: "Mr. Herr" Cc: Caml List Content-Type: multipart/alternative; boundary=001a11c3476a2dafcf051249a938 Subject: Re: [Caml-list] OPAM 1.2.1 --001a11c3476a2dafcf051249a938 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable There is no error. The update seems to have succeeded. An "update" only updates the metadata information, and doesn't actually upgrade any of your packages. To upgrade your packages, you can now type "opam upgrade" as the message printed out states. What you're referring to as heiroglyphs, I see as rather nice usage of unicode characters to represent useful information. On Fri, Mar 27, 2015 at 2:29 PM, Mr. Herr wrote: > > > On 27.03.2015 19:09, Anil Madhavapeddy wrote: > >> On 27 Mar 2015, at 18:00, Mr. Herr wrote: >> >>> >>> the 1.2.1 binary from https://github.com/ocaml/opam/releases/tag/1.2.1, >>> as well as the compile result of >>> opam-full-1.2.1.tar.gz are behaving strange on my opensuse 1.3.1. >>> >>> All I did was to replace the 1.2.0 binaries with the 1.2.1 version. >>> >>> Here a console log where 'opam' is /usr/local/bin/opam-1.2.1-x86_ >>> 64-Linux >>> >>> ------------------------------------------------------------ >>> --------------------------------------- >>> strobel@s131-intel:/data/lvmvol/strobel-sources> opam update >>> >>> =3D-=3D- Updating package repositories =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D- >>> =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D >>> [default] synchronized from https://opam.ocaml.org >>> >>> Updates available for 4.02.1, apply them with 'opam upgrade': >>> =3D=3D=3D=3D=3D =E2=86=BB 1 =E2=86=97 1 =3D=3D=3D=3D=3D >>> strobel@s131-intel:/data/lvmvol> opam-1.2.0-x86_64-Linux update >>> [default] Downloading https://opam.ocaml.org/urls.txt >>> Updating /opt/opam/repo/compiler-index ... >>> Updating /opt/opam/compilers/ ... >>> Updating /opt/opam/repo/package-index ... >>> Updating /opt/opam/packages/ ... >>> >>> Updates available for 4.02.1, apply them with 'opam upgrade': >>> =3D=3D=3D 1 to reinstall | 1 to upgrade =3D=3D=3D >>> strobel@s131-intel:/data/lvmvol> >>> ------------------------------------------------------------ >>> --------------------------------------------- >>> >>> What can I do to debug this? >>> >>> I'm not sure if I've missed something obvious, since you haven't >> specified what you think has gone wrong. You appear to have typed in "op= am >> update" twice. >> >> Either do "opam update -u" (which updates the package sets and upgrades >> them), or "opam update && opam upgrade". >> >> >> the output from the 1.2.0 version is there for reference, this is what I > have come to expect. > > The 1.2.1 binary is not doing the same checks, and outputs hieroglyphs - > very dubious. > > /Str > > > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > --001a11c3476a2dafcf051249a938 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
There is no error. The update seems to have succeeded. An = "update" only updates the metadata information, and doesn't a= ctually upgrade any of your packages. To upgrade your packages, you can now= type "opam upgrade" as the message printed out states.

<= /div>
What you're referring to as heiroglyphs, I see as rather nice= usage of unicode characters to represent useful information.

On F= ri, Mar 27, 2015 at 2:29 PM, Mr. Herr <misterherr@freenet.de> wrote:


On 27.03.2015 19:09, Anil Madhavapeddy wrote:
On 27 Mar 2015, at 18:00, Mr. Herr <misterherr@freenet.de> wrote:

the 1.2.1 binary from https://github.com/ocaml/opam/releases/tag= /1.2.1, as well as the compile result of
opam-full-1.2.1.tar.gz are behaving strange on my opensuse 1.3.1.

All I did was to replace the 1.2.0 binaries with the 1.2.1 version.

Here a console log where 'opam' is /usr/local/bin/opam-1.2.1-x86_64-Linux

-------------------------------------------------------------= --------------------------------------
strobel@s131-intel:/data/lvmvol/strobel-sources> opam update

=3D-=3D- Updating package repositories =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D
[default] synchronized from https://opam.ocaml.org

Updates available for 4.02.1, apply them with 'opam upgrade':
=3D=3D=3D=3D=3D =E2=86=BB=C2=A0 1=C2=A0 =C2=A0=E2=86=97=C2=A0 1 =3D=3D=3D= =3D=3D
strobel@s131-intel:/data/lvmvol> opam-1.2.0-x86_64-Linux update [default] Downloading https://opam.ocaml.org/urls.txt
Updating /opt/opam/repo/compiler-index ...
Updating /opt/opam/compilers/ ...
Updating /opt/opam/repo/package-index ...
Updating /opt/opam/packages/ ...

Updates available for 4.02.1, apply them with 'opam upgrade':
=3D=3D=3D 1 to reinstall | 1 to upgrade =3D=3D=3D
strobel@s131-intel:/data/lvmvol>
-------------------------------------------------------------= --------------------------------------------

What can I do to debug this?

I'm not sure if I've missed something obvious, since you haven'= t specified what you think has gone wrong. You appear to have typed in &quo= t;opam update" twice.

Either do "opam update -u" (which updates the package sets and up= grades them), or "opam update && opam upgrade".


the output from the 1.2.0 version is there for reference, this is what I ha= ve come to expect.

The 1.2.1 binary is not doing the same checks, and outputs hieroglyphs - ve= ry dubious.

/Str

--001a11c3476a2dafcf051249a938--