hannes changed the topic of #mirage to: MirageOS are OCaml unikernels - https://mirage.io - this channel is logged at http://irclog.whitequark.org/mirage/ - MirageOS 3.7.1 is released - happy hacking!
zkms has quit [Quit: zkms]
zkms has joined #mirage
Haudegen has quit [Ping timeout: 240 seconds]
mahmudov has joined #mirage
<mahmudov> hi
<mahmudov> i got this error
<mahmudov> while installing mirage with opam
<mahmudov> is there any help-hint
nagi has joined #mirage
baka has quit [Ping timeout: 265 seconds]
pie_ has quit [Ping timeout: 268 seconds]
mahmudov has quit [Ping timeout: 260 seconds]
pie_ has joined #mirage
pie_ has quit [Ping timeout: 240 seconds]
oni-on-ion has quit [Ping timeout: 248 seconds]
ehmry has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
ehmry has joined #mirage
mahmudov has joined #mirage
pie_ has joined #mirage
<dinosaure> mahmudov: the problem is not about mirage but lwt, you probably should report an issue here: https://github.com/ocsigen/lwt
pie_ has quit [Ping timeout: 258 seconds]
<mahmudov> dinosaure, i figure out it, it needs to libev library
<mahmudov> i got this when preparing www
<mahmudov> is it related -www package of mirage?
<dinosaure> hmmhmm, it seems related to the c3 package which needs an old version of js_of_ocaml
<dinosaure> from what I know, this package was not updated for a long time
<dinosaure> you probably can fix it with opam pin add c3 --dev
Haudegen has joined #mirage
<mahmudov> i am not sure if i do opam pin, there will be break my mirage setup?
<mahmudov> recompile means, related packages will recompile due to updating c3?
<dinosaure> I would like to say you should do when most of packages will be just a recompilation due to ptime/js_of_ocaml
<dinosaure> so it seems fine for me
<mahmudov> ok-doing
<mahmudov> another issue :)
<mahmudov> should i do same for xapi-rrd?
<dinosaure> I believe :) I'm not really aware about this unikernel :d
<mahmudov> just curious
<mahmudov> it seems 1.0.2 last version
<mahmudov> it seems 1.20
<mahmudov> 1.2.0 *
<mahmudov> so opam repository needs to a pr, i think?
<mahmudov> dinosaure, how can i roll-back my pin add about c3?
<mahmudov> i realized, general issue is out of date of opam repository
<dinosaure> opam pin remove c3
<dinosaure> and then, yes, the global issue is outdated packages
<mahmudov> can we do pull req. for outdated packs
<mahmudov> sorry i am not so aware of ocaml/opam contributing
<mahmudov> though i asked same question in #ocaml
<dinosaure> you can make an issue into dev repository yes, I'm sure Anil will be able to cut a release on them - he takes care about this unikernel :)
pie_ has joined #mirage
pie_ has quit [Ping timeout: 248 seconds]
<mahmudov> ok
pie_ has joined #mirage
mahmudov has quit [Ping timeout: 258 seconds]
jnavila has joined #mirage
Haudegen has quit [Ping timeout: 268 seconds]
Haudegen has joined #mirage
mahmudov has joined #mirage
<nagi> is it possible to do something like an opam-pin based on _date_?
<nagi> as opposed to tracking down version history of all mods by hand and pinning them to the right versions...
<reynir> nagi: you could clone the opam-repository and host your own, and checkout different revisions. I'm not sure the packages contain release date metadata :/
<nagi> reynir: well, the opam web interface shows release dates (even for older versions), so it is there _somewhere_. :)
<nagi> reynir: in related notes, so far i have been unable to summon any working version of ssh-agent.
<reynir> Ah, interesting
<reynir> Oh damn, that's not promising :/
<nagi> well, mainly it means i still have no idea what is actualy exploding.
<nagi> the working build i have is tagged 20190101. so i have been trying to build a new one with "just as things were a year ago". and so far it all still just explodes right after starting.
<nagi> and the current test is _really_ retro already. ocaml 4.05.0 ...
mahmudov has quit [Ping timeout: 265 seconds]
<nagi> i am back to that rapid-devtesting setup with the template-root mounted in the buildvm so i can just copy in the kernel and hit restart without any additional steps
mahmudov has joined #mirage
<nagi> ugh
<mahmudov> nagi i am not sure but i can be done with commit value?
<nagi> this turns out to be even weirder than i thought the last days.
<nagi> the kernels work just fine if i start them directly without grub being involved.
<nagi> now i am really out of ideas. it also suggests the explosion may be in grub, not the mirage kernel at all, but something about the newer mirage kernel confuses grub into exploding.
<nagi> but at the same time it can not be anything really fundamental, because if i copy the old ssh-agent kernel in, or a freshly build mirage-firewall kernel ... grub can start it.
Haudegen has quit [Ping timeout: 265 seconds]
<nagi> i am going to toss marmarek a summary, perhaps he has some idea.
Haudegen has joined #mirage
jnavila has quit [Ping timeout: 245 seconds]
engil has joined #mirage
engil has joined #mirage
engil has quit [Changing host]
Haudegen has quit [Ping timeout: 260 seconds]
jnavila has joined #mirage
Haudegen has joined #mirage
pie_ has quit [Remote host closed the connection]
pie_ has joined #mirage
_whitelogger has joined #mirage
jnavila has quit [Remote host closed the connection]
Haudegen has quit [Ping timeout: 260 seconds]
TheRuralJuror has joined #mirage
TheRuralJuror has quit [Ping timeout: 265 seconds]
Haudegen has joined #mirage
pie_ has quit [Quit: No Ping reply in 180 seconds.]
pie_ has joined #mirage
pie_ has quit [Excess Flood]
pie_ has joined #mirage
pie_ has quit [Ping timeout: 265 seconds]
pie_ has joined #mirage
<nagi> oh boy. so, marmarek figured it out ... https://pastebin.com/raw/JgSmRD6a ... means "not enough memory" ... i had it set to 23MB, it needs at least 24MB now ...
pie_ has quit [Ping timeout: 248 seconds]