hannes changed the topic of #mirage to: bug cleaning day every first friday in month (14:00 UTC - late, next: April 6th) - retreat 7th-18th March http://retreat.mirage.io - this channel is logged at http://irclog.whitequark.org/mirage/ - MirageOS 3 is released - happy hacking!
balduin has quit [Remote host closed the connection]
gentauro has quit [Ping timeout: 240 seconds]
gentauro has joined #mirage
raboof has quit [Ping timeout: 240 seconds]
raboof has joined #mirage
equalunique[m] has quit [*.net *.split]
equalunique[m] has joined #mirage
gentauro has quit [Ping timeout: 256 seconds]
gentauro has joined #mirage
argent_smith has joined #mirage
lars_kurth has quit [Read error: Connection reset by peer]
lars_kurth has joined #mirage
mort___ has joined #mirage
mort___ has left #mirage [#mirage]
miragebot has joined #mirage
<miragebot>
mirage/dev-solo5 0db7a05 Martin Lucina: Supress lint warnings from generated opam file
miragebot has left #mirage [#mirage]
<miragebot>
[mirage] mato pushed 1 new commit to dev-solo5: https://git.io/vxvKb
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
dtornabene has joined #mirage
<mato>
FYI: I have just merged all the Mirage/Solo5 updates for the API changes, so the https://github.com/Solo5/opam-solo5 remote now works against the new APIs. | Solo5/opam-solo5 | opam-solo5 - Development versions of OPAM packages for Mirage/Solo5
<mato>
Note that packages using mirage-os-shim (i.e. dependencies of eg. static_website_tls) don't work due to changes in the OS module, I will raise an issue on mirage-os-shim about this
<mato>
kensan: opam-solo5 now includes the dev-solo5 feature branch of mirage/mirage so muen support should work from that repo
<kensan>
mato: Ah great, thanks!
<kensan>
mato: Will give it a spin in the next few days (probably not today)
<mato>
...and the mirage-os-shim has a temporary pin also in opam-solo5 so that should work too
<mato>
kensan: please do and report back...
<kensan>
mato: will do!
<kensan>
mato: Should I use 4.06.* or stick with 4.04.*?
<kensan>
or both?
<mato>
kensan: either should work, tho I've been testing with 4.06. But CI is passing on >= 4.04.2
<kensan>
mato: Ok great. I will test with both to be sure.
<mato>
kensan: Unless the cohttp/jbuilder build issue is fixed by then you'll also want to pin jbuilder to 1.0+beta17 if you'll be building anything that does http