<haesbaert>
im emerging from the ashes, pushing some commits now
<haesbaert>
what's going on ? where mirage 3 at ?
<hannes>
heh, then I can leave into the dark...
<hannes>
API breaking changes \o/
<haesbaert>
and happy times were had by all
<haesbaert>
break _ALL_ the things
<hannes>
I suspect there are still some open thingies... like errors, rename of the module, ...
<hannes>
I'd personally expect it at any point this month, likely rather second half
<hannes>
and I think there's good progress underway
<haesbaert>
ah that's nice
<haesbaert>
im holding a charrua release that depends on it
<hannes>
are you in a hurry?
<haesbaert>
never
saite has joined #mirage
<haesbaert>
omg look who it is :D
<hannes>
how did that happen? ;)
<haesbaert>
saite: whats up
<saite>
hey :)
<saite>
last pull request on mirage-block-ccm breaks tests an i dont know how to resolve this...
<saite>
also: procrastinating important stuff
<hannes>
saite: pin mirage-types (in .travis.yml put a PINS="mirage-types" in the PACKAGE=... line (and remove the OPAM_VERSION))
<saite>
hannes: and release a new version to opam after mirage3 is out?
<hannes>
saite: yes, but mirage3 is not there yet.. more breaking changes to come I believe
<hannes>
saite: uhm, changes to .travis.yml shouldn't be necessary, and the failure was likely intermediate (travis ran before the mirage-types got merged to master)
<saite>
yes, i have passing builds now
<saite>
despite OPAM_VERSION=... still in .travis.yml
<hannes>
you might want to remove the OPAM_VERSION, and add a second line with OCAML_VERSION=4.03 ...
<hannes>
(and change the other "latest" to 4.02
<hannes>
)
<saite>
and EXTRA_REMOTES takes care of the pins ?
<hannes>
yes
<saite>
second line inherits stuff from first line ?
<hannes>
no
agarwal1975 has quit [Read error: Connection reset by peer]