[MirageOS-devel] nocrypto and opam 1.2.0

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

I notice that nocrypto is now using some newer OPAM variables that were 
introduced in 1.2.1+, and so running it on OPAM 1.2.0 results in:

=-=- Installing packages =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[ERROR] nocrypto-inhibit-modernity is not a valid variable.
[WARNING] Invalid variable nocrypto-inhibit-modernity in filter
[ERROR] 'nocrypto-inhibit-modernity' has type string, but a env element of type 
bool was expected.
[ERROR] The compilation of nocrypto.0.5.1 failed.
Removing nocrypto.0.5.1.
  ocamlfind remove nocrypto

This is a problem since the default OPAM in Ubuntu is 1.2.0, and so it breaks 
out of the box.  Is this inhibit-modernity absolutely required in mainline?  
I'd like a workaround today in the OPAM metadata so that our Ubuntu acceptance 
builds don't break.

It was perhaps a mistake to introduce new OPAM file semantics in a point 
release and not expect anyone to use it, but too late now...(and easily fixed).

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel