[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos

  • To: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • From: Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>
  • Date: Thu, 18 Sep 2014 23:20:56 +0100
  • Accept-language: en-US, en-GB
  • Acceptlanguage: en-US, en-GB
  • Cc: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 18 Sep 2014 22:21:11 +0000
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>
  • Thread-index: Ac/TjtF7RHJYrPY5RdqdmskZagZZLA==
  • Thread-topic: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos

On 18 Sep 2014, at 22:38, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:

> I've ported the trunks of mirage-skeleton and mirage-www to use the Mirage 2 
> development repositories, since most of us are using the latest libraries in 
> order to test them for release anyway.
> To build mirage-skeleton/mirage-www, you will now need to:
>    opam remote add mirage git://github.com/mirage/mirage-dev
>    opam update -u

fwiw just tried that and ended up at 

mirage-www.1.2.0 Fetching git://github.com/mirage/mirage-www
The following DEV package needs to be upgraded:
 - mirage-www.1.2.0
Updating the cache of metadata (~/.opam/state.cache) ...
0 to install | 103 to reinstall | 14 to upgrade | 1 to downgrade | 0 to remove
You can now run 'opam upgrade' to upgrade your system.
[WARNING] External solver failed with inconsistent return value. Request saved 
to "/Users/mort/.opam/log/solver-error-33616-1.cudf"
Falling back to the internal heuristic.

...at which point i killed it. is this expected, or worth filing an opam issue?



Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.