>>> Is it possible that I have a version mismatch where the version of conduit >>> (0.8.4) is incompatible with mirage-http (2.2.0)? >> >> indeed. >> >> conduit 0.8.4 works with mirage-http 2.3.0 (cohttp 0.17.*) and mirage-http >> 2.4.0 (cohttp 0.18.*). If you wait a little bit more, all these package will >> be in opam. >> > > But how did the incorrect existing version constraint get installed? Before > merging the new packages, shouldn't the old packages all have correct version > information?
There were indeed a missing constraint in mirage-http 2.2.0. Should be fixed by https://github.com/ocaml/opam-repository/pull/4214 Thomas _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
