Xen project Mailing List

[MirageOS-devel] upper bounding of mirage packages in mainline opam-repo

To: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>

From: Anil Madhavapeddy <anil@xxxxxxxxxx>

Date: Tue, 6 Dec 2016 16:12:03 +0000

Delivery-date: Tue, 06 Dec 2016 16:12:26 +0000

Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:to; q=dns; s=selector1; b=JyN/Z2fCWODNnCw3IFMXk 3M05mM3j5RNsOj9ufKQW65T2cgMoxp3bv5iOXUfqGRcE8lcIxcnC7tjmpiQMyZMR lJyzNNWbbjr9gLE92nKW6Qnp4vrrNO6II2RTIo6pY4XOrWinQlbdb96gWBSIyyP+ r/ffKwsJpmiMZcqAJwAhns=

List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

Dear all, The mainline OPAM repository needs to have an upper bound on Mirage2 related packages to make room for the incoming 3.0 releases (that are currently staged in https://github.com/mirage/mirage-dev). Thanks to a fancy new CLI-based upper-bounding tool from Mindy Preston, and more importantly, the tool's application to opam-repository, these 3 PRs have now been merged: https://github.com/ocaml/opam-repository/pull/7975 https://github.com/ocaml/opam-repository/pull/7974 https://github.com/ocaml/opam-repository/pull/7973 Please let us know if you spot any unexpected package regressions due to this. If anyone wishes to help Mindy to generalise the CLI upperbound-constrainer, the source is here: https://github.com/yomimono/upperbound-constrainer regards, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.