Re: [MirageOS-devel] Mirage 1.1.0 pull req

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 10 Feb 2014, at 12:28, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> 
> On 10 Feb 2014, at 10:08, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> 
>> On 9 Feb 2014, at 19:00, Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx> 
>> wrote:
>> 
>>> 
>>> On 9 Feb 2014, at 18:24, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
>>> 
>>>> On 9 Feb 2014, at 18:17, Richard Mortier 
>>>> <Richard.Mortier@xxxxxxxxxxxxxxxx> wrote:
>>>> 
>>>>> ack; it might be useful to write down (or collate) the assumptions we're 
>>>>> making about package dependencies to check that we're coherent. i'm 
>>>>> having problems at the moment trying to go from a clean opam install on 
>>>>> xen to even being able to "mirage configure" my website -- there seem to 
>>>>> be some weird package version incompatibilities. (eg., if 
>>>>> mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; 
>>>>> but if mirage-types is not installed at all, it seems to install 1.1.0.)
>>>> 
>>>> Be sure to `opam update -u` before attempting a compilation, as that will 
>>>> give you the latest package sets and upgrade all relevant packages.
>>>> 
>>>> The "opam install" that is invoked by the unikernel build won't upgrade 
>>>> everything, hence the problems you're seeing.  If it persists after an 
>>>> upgrade, we have a constraint problem.
>>> 
>>> this was after a "rm -rf ~/.opam" etc -- trying again from clean.
>> 
>> In that case, can you reproduce on Travis from a clean installation?  That'd 
>> greatly help debug it.
> 
> I just pushed a fix to one bad dependency here:
> 
> https://github.com/mirage/opam-repository/commit/f43c77cc8413fe9f0ec710cc893eb9031a56c641

Ahh, I found the root cause of all these little build failures. I had 
accidentally released the cohttp-0.9.15 archive as 0.9.16.

Re-released cohttp here:
https://github.com/ocaml/opam-repository/pull/1660

And has been merged into the Mirage 1.1.x branch, and all is suddenly now 
compiling far more happily.  I hadn't spotted this during development as my 
cohttp was pinned to my working branch :-)

-anil


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