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

Re: [MirageOS-devel] dns, conduit, cohttp: hit the release train



I am just cutting a new release of alcotest which will break some packages:

```
$ grep alcotest -r packages/ | grep 0.8.0
packages//angstrom/angstrom.0.1.0/opam:  "alcotest" {test & >= "0.4.1" & < 
"0.8.0"}
packages//angstrom/angstrom.0.1.1/opam:  "alcotest" {test & >= "0.4.1" & < 
"0.8.0"}
packages//angstrom/angstrom.0.2.0/opam:  "alcotest" {test & >= "0.4.1" & < 
"0.8.0"}
packages//angstrom/angstrom.0.3.0/opam:  "alcotest" {test & >= "0.4.1" & < 
"0.8.0"}
packages//angstrom/angstrom.0.4.0/opam:  "alcotest" {test & >= "0.4.1" & < 
"0.8.0"}
packages//angstrom/angstrom.0.5.0/opam:  "alcotest" {test & >= "0.4.1" & < 
"0.8.0"}
packages//anycache/anycache.0.6.0/opam:  "alcotest" { test & >= "0.7.2" & < 
"0.8.0"}
packages//datakit/datakit.0.10.0/opam:  "alcotest"       {test & >= "0.7.0" & < 
"0.8.0"}
packages//datakit/datakit.0.10.1/opam:  "alcotest"       {test & >= "0.7.0" & < 
"0.8.0"}
packages//datakit/datakit.0.11.0/opam:  "alcotest"          {test & >= "0.7.0" 
& < "0.8.0"}
packages//datakit/datakit.0.9.0/opam:  "alcotest"       {test & >= "0.7.0" & < 
"0.8.0"}
packages//datakit-bridge-github/datakit-bridge-github.0.11.0/opam:  "alcotest" 
{test & < "0.8.0"}
packages//datakit-client-git/datakit-client-git.0.11.0/opam:  "alcotest"  {test 
& < "0.8.0"}
packages//digestif/digestif.0.1/opam:  "alcotest"       {test & < "0.8.0"}
packages//duration/duration.0.1.0/opam:  "alcotest" {test & >= "0.6.0" & < 
"0.8.0"}
packages//mechaml/mechaml.0.1/opam:  "alcotest" {test & < "0.8.0"}
packages//mirage-net-fd/mirage-net-fd.0.1.0/opam:  "alcotest" {test & < "0.8.0"}
packages//mirage-net-fd/mirage-net-fd.0.2.0/opam:  "alcotest" {test & < "0.8.0"}
packages//mirage-net-fd/mirage-net-fd.0.2.1/opam:  "alcotest" {test & < "0.8.0"}
packages//mirage-net-flow/mirage-net-flow.1.0.0/opam:  "alcotest" {test & < 
"0.8.0"}
packages//protocol-9p/protocol-9p.0.8.0/opam:  "alcotest" {test & >= "0.4.0"}
packages//tyre/tyre.0.1/opam:  "alcotest" {test & >= "0.6.0" & < "0.8.0"}
packages//tyre/tyre.0.1.1/opam:  "alcotest" {test & >= "0.6.0" & < "0.8.0"}
packages//tyre/tyre.0.2/opam:  "alcotest" {test & >= "0.6.0" & < "0.8.0"}
packages//tyre/tyre.0.3/opam:  "alcotest" {test & >= "0.6.0" & < "0.8.0"}
```

I haven't reported all the constraints upstream yet, so would make sense to 
double-check them. Also, that would be great to enable `install -t` in the CI 
(or just set OPAMBUILDTEST=1 in the environment) as I spent the week fixing 
test constraints which were pretty broken[1].

Thomas

[1]: 
https://github.com/ocaml/opam-repository/pulls?q=is%3Apr+author%3Asamoht+is%3Aclosed
 (2 pages)

> On 23 Jun 2017, at 14:17, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> 
> We have got significant PRs active for DNS, Conduit, Cohttp and Charrua that 
> port them all them all to use Jbuilder, in the master branches of the 
> relevant repos.
> 
> This speeds up the build, removes the use of -pack in favour of module 
> aliases, and also removes depopts.
> 
> Releasing them will require quite a few upper bounds, and so I am starting to 
> cut releases and stage them in https://github.com/mirage/mirage-dev.
> 
> I have started with dns:
> - https://github.com/mirage/ocaml-dns/releases/tag/v1.0.0
> 
> And will move onto Conduit next, and then Charrua, and then Cohttp.  Upper 
> bounds will be placed in opam-repo for older versions, so we'll need to some 
> work to port older packages to the new package layout.  When the upper bounds 
> are in place in the opam repository, I will export the releases from 
> mirage-dev to the stable upstream opam, and post on discuss.ocaml.org.
> 
> Is there anything else that needs to hit the build-system release train at 
> this time?
> 
> thanks
> Anil
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
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®.