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

Re: [MirageOS-devel] mirageos version 3 beta - less code, less magic, more results


  • To: Mindy Preston <mindy@xxxxxxxxxxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Fri, 3 Feb 2017 09:53:52 +0000
  • Cc: "mirageos-devel@xxxxxxxxxxxxxxxxxxxx" <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 03 Feb 2017 09:54:07 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=j2ur4BJoeA24CTLR36y4TFpMRBGcf1UNI+cnChV1Qc1ueNKGUlv eeLgESuZZtwqiyPVOK/dCMmLEaIaI5r374K6oHMBmbFF7D1L52kP7xNXKFCGNHU9 Dr6edVwS6rzRfO97i53EXYleHaNpvzryPkee3JUAnEKEz+rypbMuTyNE=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

On 2 Feb 2017, at 19:50, Mindy <mindy@xxxxxxxxxxxxxxxxxxx> wrote:
> 
> I'm very pleased to let you know that a minimal package universe for the 
> MirageOS 3 beta is available at https://github.com/mirage/mirageos-3-beta .  
> Instructions for trying it out are in the README there.  A summary of the 
> changes in MirageOS 3 is available at 
> https://github.com/mirage/mirage/releases/tag/v3.0.0 , with more detailed 
> writeups forthcoming (and volunteers welcome!).
> 
> Please note that if you've added the https://github.com/mirage/mirage-dev 
> remote, you'll need to remove it to get the package versions in the beta 
> repository, as the versions noted for packages in mirage-dev will always be 
> higher than those in mirageos-3-beta and thus preferred by the solver if opam 
> knows about them.
> 
> What's expected to work:
> - any library that's used to fulfill a request you make to the `mirage` 
> frontend tool via the `Mirage` module in your config.ml (like tls, 
> fat-filesystem, or mirage-net-solo5)
> 
> What probably won't work:
> - other libraries that depend on or implement the module type definitions in 
> `mirage-types`, but aren't integrated into the `mirage` frontend tool (like 
> irmin, shared-block-ring, or 9p-protocol).  If you're a maintainer of such a 
> library, have a look at https://github.com/mirage/mirageos-3-beta/issues/1 
> for an explanation of how to get a prerelease into the repository. PRs there 
> are welcome :)
> 
> You may also find the `mirage-dev` branches of the `mirage-skeleton` and 
> `mirage-www` repositories to be of help in trying out MirageOS 3.  See 
> https://github.com/mirage/mirage-skeleton/tree/mirage-dev and 
> https://github.com/mirage/mirage-www/tree/mirage-dev , respectively.
> 
> More documentation is coming, and the remaining TODOs for general release are 
> tracked at https://github.com/mirage/mirage/issues/592 .
> 

Thank you for the release assembly and tagging, Mindy!  Ive activated CI for 
the mirageos-3-beta branch at:

  https://ci.ocaml.io/mirage/mirageos-3-beta/ref/heads/master

You can also find differential bulk build results with and without mirage-dev 
included at:

  https://ci.ocaml.io/mirage/opam-repository/ref/heads/bulk

The differences are:

datakit (0.8.0 -> dev~mirage) fails now
dog (0.2.1 -> 0.2.1) fails now
ezirmin (0.1.0 -> 0.1.0) fails now
jitsu-libxl (0.0.1 -> 0.0.1) broken before and now builds
mirage-block-xen (1.4.0 -> dev~mirage) broken before and now builds
mirage-console-xen (1.0.2 -> dev~mirage) fails now
mirage-entropy-xen (0.3.0 -> 0.3.0) fails now
mirage-git (1.6.0 -> 1.6.0) fails now
mirage-irmin (0.9.8 -> 0.9.8) fails now
mirage-net-solo5 (0.1.1 -> dev~mirage) fails now
mirage-net-xen (1.6.1 -> dev~mirage) still broken
mirage-qubes (0.3 -> dev~mirage) fails now
mirage-xen (2.6.0 -> dev~mirage) fails now
mirage-xen-minios (0.8.0 -> 0.8.0) fails now
mirage-xen-ocaml (2.6.0 -> dev~mirage) fails now
mirage-xen-posix (2.6.0 -> 2.6.0) fails now
qcow (0.7.0 -> dev~mirage) fails now
qcow-format (0.5.0 -> 0.5.0) fails now
session (0.3.0 -> dev~mirage) fails now
vhd-format (0.8.0 -> dev~mirage) fails now
vpnkit (0.0.0 -> 0.0.0) fails now
xenctrl (0.9.30 -> dev~mirage) broken before and now builds
datakit-ci (new dev~mirage) fails now
mirage-www (new dev~mirage) fails now
prometheus-app (new dev~mirage) fails now
shared-block-ring (new dev~mirage) fails now

Some of these failures need triage, but there are almost certainly a few 
genuine build failures in there. Any debugging or PRs fixing your libraries are 
most welcome.  I'll switch this testing over to the mirageos-3-beta branch on 
Monday.  I am also deploying the beta branch for live infrastructure as well, 
so we will move to Solo5 and Xen simultaneously as soon as everything is 
compiled and deployed.

regards
Anil


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

 


Rackspace

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