[Caml-list] opam update failing

[Caml-list] opam update failing

[Malcolm Matalka]

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?

Thanks,
/M

Re: [Caml-list] opam update failing

[Török Edwin]

On 10/06/2012 10:57 PM, 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!

I had a similar 'Bad format' message a while ago, and it went away
after upgrading to opam 0.7.
For some reason the download instructions took me to version 0.6
at the time, even though 0.7 was already available.
The download instruction point to 0.7 now though, which version do you have?

Now I only get these errors:
Package wdialog.2.1.3 depends on the unknown package ocaml-inifiles
Package why.2.31 depends on the unknown package frama-c
  'opam update' failed

Best regards,
--Edwin

Re: [Caml-list] opam update failing

[Mike McClurg]

On Sat, Oct 6, 2012 at 9:49 PM, Török Edwin <edwin+ml-ocaml@etorok.net> wrote:
> On 10/06/2012 10:57 PM, 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!
>
> I had a similar 'Bad format' message a while ago, and it went away
> after upgrading to opam 0.7.
> For some reason the download instructions took me to version 0.6
> at the time, even though 0.7 was already available.
> The download instruction point to 0.7 now though, which version do you have?

Opam changes very often. The latest tag on github is 0.7.5, which is
working well for me. I recommend rebuilding opam regularly, but only
from the tagged versions.

Mike

Re: [Caml-list] opam update failing

[Malcolm Matalka]

Bringing my opam up to date was the trick.  Works like a charm now.

On Sun, Oct 7, 2012 at 1:56 AM, Mike McClurg <mike.mcclurg@gmail.com> wrote:
> On Sat, Oct 6, 2012 at 9:49 PM, Török Edwin <edwin+ml-ocaml@etorok.net> wrote:
>> On 10/06/2012 10:57 PM, 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!
>>
>> I had a similar 'Bad format' message a while ago, and it went away
>> after upgrading to opam 0.7.
>> For some reason the download instructions took me to version 0.6
>> at the time, even though 0.7 was already available.
>> The download instruction point to 0.7 now though, which version do you have?
>
> Opam changes very often. The latest tag on github is 0.7.5, which is
> working well for me. I recommend rebuilding opam regularly, but only
> from the tagged versions.
>
> Mike
>
> --
> 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

Re: [Caml-list] opam update failing

[Malcolm Matalka]

On a side note, I was very surprised when an 'opam upgrade' didn't
actually bring me to the latest versions of everything.  Specifically
all of the jane st stuff was an older version than the latest.  I
ended up wiping my entire opam, "opam remove" was not working for me
either, and starting from scratch, which worked.  I'm sure that makes
sense for someone that knows opam but I found it counter intuitive.

On Sun, Oct 7, 2012 at 2:22 AM, Malcolm Matalka <mmatalka@gmail.com> wrote:
> Bringing my opam up to date was the trick.  Works like a charm now.
>
> On Sun, Oct 7, 2012 at 1:56 AM, Mike McClurg <mike.mcclurg@gmail.com> wrote:
>> On Sat, Oct 6, 2012 at 9:49 PM, Török Edwin <edwin+ml-ocaml@etorok.net> wrote:
>>> On 10/06/2012 10:57 PM, 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!
>>>
>>> I had a similar 'Bad format' message a while ago, and it went away
>>> after upgrading to opam 0.7.
>>> For some reason the download instructions took me to version 0.6
>>> at the time, even though 0.7 was already available.
>>> The download instruction point to 0.7 now though, which version do you have?
>>
>> Opam changes very often. The latest tag on github is 0.7.5, which is
>> working well for me. I recommend rebuilding opam regularly, but only
>> from the tagged versions.
>>
>> Mike
>>
>> --
>> 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

Re: [Caml-list] opam update failing

[Anil Madhavapeddy]

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

Re: [Caml-list] opam update failing

[Anil Madhavapeddy]

On Sun, Oct 07, 2012 at 02:51:03AM +0200, Malcolm Matalka wrote:
> On a side note, I was very surprised when an 'opam upgrade' didn't
> actually bring me to the latest versions of everything.  Specifically
> all of the jane st stuff was an older version than the latest.  I
> ended up wiping my entire opam, "opam remove" was not working for me
> either, and starting from scratch, which worked.  I'm sure that makes
> sense for someone that knows opam but I found it counter intuitive.

This is actually correct behaviour, although OPAM could explain its
reasoning to the user better.

The latest JSC packages (108.07.00+) introduced a backwards-incompatible
API change in type_conv.  Type_conv is very commonly used by third-party
packages such as OASIS (via ODN) and would break if compiled against the
newest version.

Luckily, OPAM supports constraints on the package versions that let it
figure out a workable strategy, which in this case will use the older
version of type_conv.  Since the Core suite has an exact dependency on
type_conv, this will also pin the rest of Core and Async to that older
version.

I've been patching a few of the type_conv packages to support the newer
API, and once these are merged [1], an 'opam upgrade' should recompile
your packages up to the latest version.

[1] https://github.com/OCamlPro/opam-repository/pull/107

-- 
Anil Madhavapeddy                                 http://anil.recoil.org

Re: [Caml-list] opam update failing

[Török Edwin]

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