[Caml-list] [ANN] OPAM 1.2.1

[Caml-list] [ANN] OPAM 1.2.1

[Louis Gesbert]

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

Hi,

We're glad to announce the release of the version 1.2.1 of the OPAM package manager.
This point release features a number of stability improvements, better processing of package operations, better messages, and fixes.

See the announcement and get the update at http://opam.ocaml.org/blog/opam-1-2-1-release/

Thanks to all the contributors, testers and issue reporters!

Best,
Louis Gesbert, OCamlPro

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [Caml-list] OPAM 1.2.1

[Mr. Herr]

On 24.03.2015 04:08, Louis Gesbert wrote:
> We're glad to announce the release of the version 1.2.1 of the OPAM package manager.
> This point release features a number of stability improvements, better processing of package operations, better messages, and fixes.
>
> See the announcement and get the update at http://opam.ocaml.org/blog/opam-1-2-1-release/
>
Hi,

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

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

Updates available for 4.02.1, apply them with 'opam upgrade':
===== ↻  1   ↗  1 =====
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':
=== 1 to reinstall | 1 to upgrade ===
strobel@s131-intel:/data/lvmvol>
---------------------------------------------------------------------------------------------------------

What can I do to debug this?

/Str.

Re: [Caml-list] OPAM 1.2.1

[Anil Madhavapeddy]

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
> 
> =-=- Updating package repositories =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [default] synchronized from https://opam.ocaml.org
> 
> Updates available for 4.02.1, apply them with 'opam upgrade':
> ===== ↻  1   ↗  1 =====
> 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':
> === 1 to reinstall | 1 to upgrade ===
> 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 "opam update" twice.

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

-anil

Re: [Caml-list] OPAM 1.2.1

[Mr. Herr]

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
>>
>> =-=- Updating package repositories =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> [default] synchronized from https://opam.ocaml.org
>>
>> Updates available for 4.02.1, apply them with 'opam upgrade':
>> ===== ↻  1   ↗  1 =====
>> 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':
>> === 1 to reinstall | 1 to upgrade ===
>> 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 "opam 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

Re: [Caml-list] OPAM 1.2.1

[Stefan Schmiedl]

Mr. Herr (27.03. 19:29):

> 
> 
> 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
> >>
> >> =-=- Updating package repositories =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >> [default] synchronized from https://opam.ocaml.org
> >>
> >> Updates available for 4.02.1, apply them with 'opam upgrade':
> >> ===== ↻  1   ↗  1 =====
> >> 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':
> >> === 1 to reinstall | 1 to upgrade ===
> >> 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 "opam 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.

With an unicode-compatible font, the first glyph looks like a circle
with an arrow, i.e. 1 reinstall, and the second is an arrow pointing
to upper-right, i.e. 1 upgrade.

s.

Re: [Caml-list] OPAM 1.2.1

[Ashish Agarwal]

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

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 <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
>>>
>>> =-=- Updating package repositories =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>> =-=-=-=-=-=-=-=
>>> [default] synchronized from https://opam.ocaml.org
>>>
>>> Updates available for 4.02.1, apply them with 'opam upgrade':
>>> ===== ↻  1   ↗  1 =====
>>> 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':
>>> === 1 to reinstall | 1 to upgrade ===
>>> 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 "opam
>> 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
>

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

Re: [Caml-list] OPAM 1.2.1

[Mr. Herr]

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

Hm, top-posting?

Okay, so we have hieroglyph graphics in 1.2.1, and the update of the local opam 
directories is terse , and everything is fine.

I would have voted against the unicode graphics, they are not enough self explaining 
(I admit though using ✓ in my scripts).

While we are at it: opam has become a well working, very reliable package manager on 
*nix systems, thank you.

/Str.

On 27.03.2015 19:54, Ashish Agarwal wrote:
> 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.
never with dubious binaries... :-)
>
> 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 <misterherr@freenet.de 
> <mailto:misterherr@freenet.de>> wrote:
>
>
>
>     On 27.03.2015 19 <tel:27.03.2015%2019>:09, Anil Madhavapeddy wrote:
>
>         On 27 Mar 2015, at 18:00, Mr. Herr <misterherr@freenet.de
>         <mailto: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
>
>             =-=- Updating package repositories
>             =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>             [default] synchronized from https://opam.ocaml.org
>
>             Updates available for 4.02.1, apply them with 'opam upgrade':
>             ===== ↻  1   ↗  1 =====
>             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':
>             === 1 to reinstall | 1 to upgrade ===
>             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 "opam 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
>
>


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

Re: [Caml-list] OPAM 1.2.1

[Daniel Bünzli]

Le vendredi, 27 mars 2015 à 20:52, Mr. Herr a écrit :
> I would have voted against the unicode graphics,  

There's no voting process but you can disable them, see:  
  
https://github.com/ocaml/opam/issues/2065#issuecomment-83232580

Btw. Louis I think the two level scheme is a little bit overkill and more complex that it should be, you should really keep it to a single variable. That two-level mechanism seem to have been design to work around issues in OS level support for unicode glyphs and it doesn't sound like a good idea. Also the description of OPAMUTF8 is misleading, UTF-8 characters may be output since opam files are UTF-8 encoded and AFAIK you don't transcode any output of the tool to ASCII when OPAMUTF8 is `never` (e.g. opam file messages: fields).  

Best,

Daniel

Re: [Caml-list] OPAM 1.2.1

[Louis Gesbert]

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

Indeed, two variables is a bit overkill, but the OPAMUTF8MSGS variable was kept mostly for backwards-compatibility, and also because I needed a (default) intermediate level with the arrows, but without the camel emojis. On second thought, maybe adding a possible value (i.e. 'always', 'never', 'auto' or 'partial') would be best. And the documentation should indeed specify that it's only for OPAM-generated messages, excluding metadata that may be printed.

Mr. Herr:
indeed, in the case of 'opam update', it's not completely self-explanatory. But I made sure that it is in the case of package actions, which is the one that matters:


    % opam install core_bench --show
    The following actions would be performed:
      ↘  downgrade sexplib       112.24.00 to 112.17.00  [required by core_bench]
      ↘  downgrade pa_ounit      112.24.00 to 112.17.00  [required by core_bench]
      ↘  downgrade bin_prot      112.24.00 to 112.17.00  [required by core_bench]
      ↘  downgrade pa_test       112.24.00 to 111.08.01  [required by core]
      ↻  recompile uri           1.8.0                   [uses sexplib]
      ↻  recompile ipaddr        2.6.1                   [uses sexplib]
      ↻  recompile ezjsonm       0.4.1                   [uses sexplib]
      ↻  recompile cstruct       1.5.0                   [uses sexplib]
      ↘  downgrade custom_printf 112.24.00 to 112.17.00  [required by core]
      ↻  recompile pa_bench      112.06.00               [uses pa_ounit]
      ↘  downgrade typerep       112.24.00 to 112.17.00  [uses bin_prot]
      ↻  recompile ocsigenserver 2.5                     [uses ipaddr]
      ↻  recompile cow           1.2.1                   [uses ezjsonm, uri]
      ↻  recompile conduit       0.7.2                   [uses sexplib]
      ↘  downgrade core_kernel   112.24.00 to 112.17.00  [uses bin_prot]
      ↻  recompile eliom         4.1.0                   [uses ipaddr]
      ↻  recompile cohttp        0.15.0                  [uses sexplib]
      ∗  install   core          112.17.00               [required by core_bench]
      ↻  recompile github        0.9.4                   [uses cohttp, uri]
      ∗  install   textutils     112.17.00               [required by core_bench]
      ∗  install   core_bench    112.17.00             
    ===== ∗  3   ↻  11   ↘  7 =====
    
the glyphs make the information easier to skim through, but the actions are written in text; the summary only shows the glyphs, but you may use the full list as a key to their meaning.
And if you have compatibility problems or just don't like it, set OPAMUTF8 to "never" and you'll get good old plain text:


    % OPAMUTF8=never opam install core_bench --show
    The following actions would be performed:
      - downgrade sexplib       112.24.00 to 112.17.00      [required by core_bench]
      - downgrade pa_ounit      112.24.00 to 112.17.00      [required by core_bench]
      - downgrade bin_prot      112.24.00 to 112.17.00      [required by core_bench]
      - downgrade pa_test       112.24.00 to 111.08.01      [required by core]
      - recompile uri           1.8.0                       [uses sexplib]
      - recompile ipaddr        2.6.1                       [uses sexplib]
      - recompile ezjsonm       0.4.1                       [uses sexplib]
      - recompile cstruct       1.5.0                       [uses sexplib]
      - downgrade custom_printf 112.24.00 to 112.17.00      [required by core]
      - recompile pa_bench      112.06.00                   [uses pa_ounit]
      - downgrade typerep       112.24.00 to 112.17.00      [uses bin_prot]
      - recompile ocsigenserver 2.5                         [uses ipaddr]
      - recompile cow           1.2.1                       [uses ezjsonm, uri]
      - recompile conduit       0.7.2                       [uses sexplib]
      - downgrade core_kernel   112.24.00 to 112.17.00      [uses bin_prot]
      - recompile eliom         4.1.0                       [uses ipaddr]
      - recompile cohttp        0.15.0                      [uses sexplib]
      - install   core          112.17.00                   [required by core_bench]
      - recompile github        0.9.4                       [uses cohttp, uri]
      - install   textutils     112.17.00                   [required by core_bench]
      - install   core_bench    112.17.00             
    ===== 3 to install | 11 to recompile | 7 to downgrade =====
    
This will also be the case, of course, if your current locale isn't UTF8.


Best,
Louis Gesbert - OCamlPro

> - Daniel Bünzli, 27/03/2015 21:24 -
> Le vendredi, 27 mars 2015 à 20:52, Mr. Herr a écrit :
> > I would have voted against the unicode graphics,  
> 
> There's no voting process but you can disable them, see:  
>   
> https://github.com/ocaml/opam/issues/2065#issuecomment-83232580
> 
> Btw. Louis I think the two level scheme is a little bit overkill and more complex that it should be, you should really keep it to a single variable. That two-level mechanism seem to have been design to work around issues in OS level support for unicode glyphs and it doesn't sound like a good idea. Also the description of OPAMUTF8 is misleading, UTF-8 characters may be output since opam files are UTF-8 encoded and AFAIK you don't transcode any output of the tool to ASCII when OPAMUTF8 is `never` (e.g. opam file messages: fields).  
> 
> Best,
> 
> Daniel
> 
> 
> 
> 

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]