19:24 <olle> So, hi!

19:25 <olle> I’m digging into why https://github.com/mirage/mirage-skeleton/ fails its build .

19:32 <olle> "ocamlfind: Package `nocrypto.mirage' not found”

19:40 <olle> @hannes Could these two things be interconnected?

19:40 <olle> 1 - https://github.com/mirage/mirage-skeleton/blame/cc3f78e36e77b188b821b5fde3f876b762df7297/device-usage/prng/config.ml#L11

19:41 <olle> and 2 - https://github.com/ocaml/opam-repository/pull/9416/files

19:41 <olle> That is, would it make sense to offer “mirage-solo5” to the ocamlfind package finding instead of the earlier “ocaml-freestanding” thing?

19:42 <olle> mato: Would you know the answer to this?

19:49 <olle> opam update

20:23 <hannes> olle: hmm yes... that makes sense... someone moved it to mirage-solo5 for unknown reasons... this dependency cone is clearly not good atm

20:26 <hannes> olle: replacing the ocaml-freestanding there in config.ml with mirage-solo5 should do the trick

20:26 <olle> I’ll make the tiny PR, see what Travis reacts with. /me lazy

20:31 <hannes> olle: \o/

20:42 <olle> hannes: Hm, “ - mirage-xen-ocaml>=3.0.4 is not available because your system doesn't comply with ocaml-version >= "4.04.2" & ocaml-version < "4.05.0" & os = "linux”.”

20:42 <olle> hannes: https://travis-ci.org/mirage/mirage-skeleton/jobs/281451043#L1081

20:45 <hannes> olle: oh :/ it seems that mirage-xen is then only working with OCaml-4.04.2 atm. (kvm&unix work fine with at least 4.04 and 4.05)

20:45 <olle> hannes: Is there a kind way for me to mark certain combinations as allow_failure

20:46 <hannes> this got "adjusted" in mirage commit a78bc0c18c545203a74323f98dd70b8be02b9fa6

20:47 <hannes> olle: well, the second job in .travis.yml can just be removed (the one with 4.03 and MODE=xen)

20:47 <olle> OK, removing

20:48 <olle> dropping " - OCAML_VERSION=4.03 WITH_TRACING=1 POST_INSTALL_HOOK="make MODE=xen && make clean""

20:52 <olle> hannes: You made a salient point by noting this exclusion. Now, I’m looking at another build, which reached longer. Its missing package seems to be dns.mirage.

20:53 <olle> https://travis-ci.org/mirage/mirage-skeleton/jobs/281451045#L2343 Got any ideas about _that_?

20:56 <hannes> olle: ups, in applications/dns/config.ml, there are some adjustments to make..

20:56 <olle> I have the file open

20:56 <hannes> (a) require dns 1.0.0 (b) add mirage-dns package

20:56 <hannes> so, adjust the min: constraint, and add another package named mirage-dns

20:57 <hannes> I suspect the sublibs: mirage can be removed as well

20:57 <olle> “ let packages = [package ~min:"1.0.0" "dns"; package "mirage-dns"; package "duration"] in|

20:58 <hannes> yes!

22:18 <olle> Oh, look, it got merged: https://github.com/mirage/mirage-skeleton/pull/239

22:25 <hannes> \o/

22:26 <olle> hannes: What do you think of this one? https://github.com/mirage/functoria/pull/146 In order to reduce confusion about “what does the build badge mean?”, this changes the build badge to display the build status of master.

22:26 <hannes> olle: it looks good to me! thanks!

22:28 <olle> Super. Good to have closure.

22:32 <olle> https://github.com/mirage/ocaml-rpc/pull/61 Add a Travis build badge (where there was none)

22:33 <hannes> that's not for me.. I only press buttons for repositories I care about / have contributed to / ..

22:41 <olle> Totally fair

22:46 <olle> https://github.com/mirage/mirage-clock

22:46 <olle> It seems like that library is missing from the build of mirage-entropy

22:48 <olle> “mirage-xen -> mirage-clock-freestanding” & “No package named mirage-clock-freestanding found” - does that mean that we need to offer mirage-clock somewhere in the package definition?