From: "Mr. Herr" <misterherr@freenet.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OPAM ppx_tools problem?
Date: Wed, 22 Oct 2014 17:13:35 +0200 [thread overview]
Message-ID: <5447C99F.2050408@freenet.de> (raw)
In-Reply-To: <b79f38726d14829475623a03a34abe1b@whitequark.org>
Am 22.10.2014 um 17:05 schrieb Peter Zotov:
> On 2014-10-22 18:51, Mr. Herr wrote:
>> I am getting these error messages in opam 1.1.1 when doing 'opam update':
>>
>> [WARNING] Errors while parsing ppx_tools.0.1 OPAM file, skipping.
>> [WARNING] Errors while parsing ppx_tools.0.99 OPAM file, skipping.
>> [WARNING] Errors while parsing ppx_tools.0.99.1 OPAM file, skipping.
>> [WARNING] Errors while parsing ppx_tools.0.99.2 OPAM file, skipping.
>> Updating the cache of metadata (/opt/opam/state.cache) ...
>> [WARNING] External solver failed with inconsistent return value.
>> Request saved to "/opt/opam/log/solver-error-2458-1.cudf"
>> Falling back to the internal heuristic.
>>
>> Is it a local problem, or do others see this also?
>
> This is my fault--I accidentally put 1.2-specific syntax into opam-repository.
> There should actually be some provisions for porting syntax back to 1.1-compatible
> form, I'm not sure why are they not working.
>
I have seen warnings before:
[WARNING] dev-repo is an unknown field in
/opt/opam/repo/default/packages/eliom/eliom.4.1.0/opam: is your OPAM up-to-date ?
[WARNING] dev-repo is an unknown field in
/opt/opam/packages/ocsigenserver/ocsigenserver.2.5/opam: is your OPAM up-to-date ?
but they did not kill the opam update function. And 1.2 is not out yet...
/Str.
----
Please ignore the Reply-To header and reply to the list.
prev parent reply other threads:[~2014-10-22 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 14:51 Mr. Herr
2014-10-22 14:56 ` Mr. Herr
2014-10-22 15:05 ` Peter Zotov
2014-10-22 15:13 ` Mr. Herr [this message]
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=5447C99F.2050408@freenet.de \
--to=misterherr@freenet.de \
--cc=caml-list@inria.fr \
/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