IRC channel logs
2021-01-14.log
back to list of logs
<zimoun>civodul: yes, I can give a try for the HPC report this year :-) <zimoun>rekado: about service and pack, we discussed with mothacehe last year at FOSDEM exactly this. Well, his views were about images and mine about packages. Somehow, it is similar: provide a file (manifest or operating system) and return an (docker or board) image or tarball. Well, Mathieu or I have been postponing because of the Web UI frontend… Anyway, this service could be awesome! :-) <zimoun>civodul: I do not see the use case for Nixery… personally. <zimoun>rekado: your presentation looks really great! Well, the visuals are really nice. <civodul>oh the presentation is already visible? <civodul>zimoun: the nixery.dev thing generates Docker images for the packages you give <zimoun>but already based on Docker images <zimoun>it use a Docker image to generate another Docker image. But I could have missed something. <civodul>my understanding is that it generates Docker images exclusively using Nixpkgs <zimoun>ah yeah, you have right. Big player, it is sponsored by Google: «// Copyright 2019 Google LLC» :-) <civodul>i heard "someone else" had their account blocked <rekado>civodul: no news from Twitter. They must be too busy with their purge and all the appeals. Now is a bad time to contest account suspension, I think. <rekado>I trying to record the video for my talk, but I really don’t have a suitable setup for this. I’ll just record video for the intro and outro to simplify things. <civodul>i did the whole thing live but the result is probably not as good as it could be <rekado>I’ve got a headache and the longer this takes the more self conscious I become… I’m beginning to think that maybe this was a mistake… :) <civodul>i've been through that and that's in part why i set myself a hard deadline <civodul>so i can only cheer you, you're almost done, be brave! :-) <rekado>thanks for tolerating my whininess :) <rekado>I should get myself a UML book to replace this wobbly tripod I have. <civodul>heheh, i had forgotten i had such a thing, and i'm glad i've finally put it too good use <civodul>there was also a natural language processing book (from my partner) <civodul>i didn't dare put my Guile 2.0 Reference Manual there, it would have been unreasonable <zimoun>civodul: you setup looks like using Pléiade books ? :-) <civodul>heh, but these are much less fancy :-) <zimoun>for the HPC report, do I send email on guix-science or simply to the usual suspect for the first round ? *rekado renders the video <rekado>I’m surprised that blender does so poorly when given a very simple video to render. <rekado>most of the video is static images. I would have thought it would have some fancy optimizations to cut down on render times, but that’s not the case. <rekado>this will probably take another hour or so <rekado>I gave up on my original plan of interspersing little video chunks in between slides after re-recording the same first two sentences for over an hour… <rekado>so now it’s just an intro video, lots of slides with audio, and an outro video <rekado>not my proudest accomplishment, but I was never comfortable with video editing anyway, so that’s not unexpected. <rekado>aw, you’re the best cheerleader :) <rekado>now comes the next task: implementing the features that I mention in the video <rekado>I say that the GWL inherits the ability to bundle up whole workflows (like ‘guix pack’); I should implement this before the video goes live. <civodul>it has to interact with the job scheduler, right? <bavier[m]>I like packs, but after using a bunch of them over many months, I kinda wish we had a sort of "pack manager". <civodul>bavier[m]: sorta like a pack(age) manager? :-) <civodul>also what rekado wrote on the ML a while ago <civodul>it's kinda weird: it's tempting to go beyond the simple one-shot usage *bavier[m] hasn't been able to keep up on the ML for a bit <civodul>but then you'd need additional tools to make that viable <civodul>and at that point you might just as well want to run Guix <rekado>civodul: it would be all the generated job scripts, all the packages referenced by processes, and (a part of) the GWL itself to launch and inspect the thing. <bavier[m]>I've written a few simple scripts to help with upgrades and gc and such. <civodul>bavier[m]: did you try running guix-daemon from a -RR pack? would that be helpful for your use cases? <rekado>I dreamed about it and thought that this could be expanded to produce workflows-as-applications much like PiGx tries to be. <rekado>whenever I feel tempted to use more than one pack I think I should install Guix instead. <rekado>it would be nice if packs could be generated in cooperation with a remote $prefix/gnu/store <civodul>if adjusting "guix copy" to cope with that can be done without too much trouble, that sounds like a good path to explore <civodul>IWBN to have a proper "store" abstraction in Guix <bavier[m]>huh,no, I hadn't though of trying to run the daemon from a pack <rekado>I just uploaded the rendered video to Penta <rekado>the audio is a little … muffled sometimes, probably because I wasn’t very careful with lv2-speech-denoiser; was necessary because of very noticeable background noise, though.