<div dir="ltr">I'm trying the option of doing `opam-admin upgrade-format`, but what's the best way to get `opam-admin`? Is it by chance available as a pre-compiled binary like `opam` is?<div><br></div><div>I'm trying to compile opam myself, but getting this:</div><div><br></div><div><div>ocamlfind ocamlc -package unix,bigarray,extlib,re,re.str,re.pcre,re.glob,cmdliner,ocamlgraph,cudf,dose3.common,dose3.algo,jsonm,no -c -g -w +a-4-44-48 -bin-annot -short-paths -safe-string -I core -I format -I solver -I repository -I state -I client -I core/ core/opamCompat.mli</div><div>ocamlfind: Package `no' not found</div></div><div><br></div><div>Unfortunately "no" isn't very easy to search for. Is that really the name of an ocamlfind package?</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 13, 2016 at 6:46 AM, <span dir="ltr"><<a href="mailto:louis.gesbert@ocamlpro.com" target="_blank">louis.gesbert@ocamlpro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That's not true. opam won't upgrade your repositories implicitely at the<br>
moment (I am considering it, but am afraid it may lead to more difficult to<br>
track errors). The only thing it rewrites is opam files found in source trees<br>
when you pin them.<br>
<br>
I will add a warning in opam2 when use of a 1.2 repository is detected.<br>
<br>
Best,<br>
Louis Gesbert - OCamlPro<br>
<div class="HOEnZb"><div class="h5"><br>
On samedi 10 décembre 2016 21:36:08 CET Drup wrote:<br>
> opam 2.0 upgrades the format automatically when pinning a repository<br>
> with an older opam format.<br>
><br>
> Le 10/12/2016 à 21:05, Anil Madhavapeddy a écrit :<br>
> > You can run "opam admin upgrade-format" to upgrade the repository, but I'm<br>
> > not sure of how to convert individual `opam` files. This seems like it<br>
> > would be useful in order to upgrade working repositories for pinning<br>
> > purposes...<br>
> ><br>
> > Anil<br>
> ><br>
> >> On 7 Dec 2016, at 21:52, Ashish Agarwal <<a href="mailto:agarwal1975@gmail.com">agarwal1975@gmail.com</a>> wrote:<br>
> >><br>
> >> Seems the issue is mis-interpretation of a deprecated constraint. I'm<br>
> >> using Jane Street's opam repository [1], which contains constraints<br>
> >> like:<br>
> >><br>
> >> available: [ ocaml-version >= "4.03.0" ]<br>
> >><br>
> >> After replacing this with a normal constraint in the `depends` field, it<br>
> >> worked fine. Is there a tool to convert old opam files?<br>
> >><br>
> >> [1] <a href="https://github.com/janestreet/opam-repository" rel="noreferrer" target="_blank">https://github.com/janestreet/<wbr>opam-repository</a><br>
> >><br>
> >><br>
> >> On Wed, Dec 7, 2016 at 8:04 AM, Ashish Agarwal <<a href="mailto:agarwal1975@gmail.com">agarwal1975@gmail.com</a>><br>
> >> wrote: I'm getting this:<br>
> >><br>
> >> $ opam install ppx_sexp_conv.114.10+84<br>
> >> [ERROR] ppx_sexp_conv.114.10+84 has unmet availability conditions:<br>
> >> ocaml-version >= "4.03.0"<br>
> >><br>
> >> So opam thinks my ocaml version is < 4.03.0, but I'm in a 4.03.0 switch.<br>
> >> I've certainly run "eval `opam config env`". I created a new switch with<br>
> >> 4.03.0 to try it from scratch, but get the same issue.<br>
> >><br>
> >> Sanity checks:<br>
> >><br>
> >> $ ocaml -version<br>
> >> The OCaml toplevel, version 4.03.0<br>
> >><br>
> >> $ opam info ocaml | grep all-installed-versions<br>
> >> all-installed-versions 4.03.0 [4.03.0] 4.04.0 [4.04.0]<br>
> >><br>
> >> Incidentally, I'm confused about the output of `opam info ocaml`. I have<br>
> >> 6 switches on this computer. How come only 2 are listed above?<br>
> >><br>
> >> $ opam --version<br>
> >> 2.0~alpha5<br>
> >><br>
> >><br>
> >> ______________________________<wbr>_________________<br>
> >> opam-devel mailing list<br>
> >> <a href="mailto:opam-devel@lists.ocaml.org">opam-devel@lists.ocaml.org</a><br>
> >> <a href="http://lists.ocaml.org/listinfo/opam-devel" rel="noreferrer" target="_blank">http://lists.ocaml.org/<wbr>listinfo/opam-devel</a><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > opam-devel mailing list<br>
> > <a href="mailto:opam-devel@lists.ocaml.org">opam-devel@lists.ocaml.org</a><br>
> > <a href="http://lists.ocaml.org/listinfo/opam-devel" rel="noreferrer" target="_blank">http://lists.ocaml.org/<wbr>listinfo/opam-devel</a><br>
><br>
> ______________________________<wbr>_________________<br>
> opam-devel mailing list<br>
> <a href="mailto:opam-devel@lists.ocaml.org">opam-devel@lists.ocaml.org</a><br>
> <a href="http://lists.ocaml.org/listinfo/opam-devel" rel="noreferrer" target="_blank">http://lists.ocaml.org/<wbr>listinfo/opam-devel</a><br>
<br>
______________________________<wbr>_________________<br>
opam-devel mailing list<br>
<a href="mailto:opam-devel@lists.ocaml.org">opam-devel@lists.ocaml.org</a><br>
<a href="http://lists.ocaml.org/listinfo/opam-devel" rel="noreferrer" target="_blank">http://lists.ocaml.org/<wbr>listinfo/opam-devel</a><br>
</div></div></blockquote></div><br></div>