IRC channel logs


back to list of logs

<zimoun>Hi! In case people missed the news: :-)
<civodul>people are shy
<zimoun>civodul: in case you missed yesterday, PurpleSym pointed to this and that
<PurpleSym>(rekado and roptat are both owners of the GitHub organization, in case something happens to me.)
<zimoun>PurpleSym: thanks. And we could discuss how to provide substitutes. Maybe something using the domain name
<PurpleSym>zimoun: I can ask our IT if I can get another server. I basically just need to run `guix publish` there, right?
<civodul>PurpleSym: ooh, thumbs up for setting up this guix-science channel!
<civodul>with authorizations and all, nice
<PurpleSym>Contributions welcome. Do you want to advertise it, even though it’s on github?
<civodul>yeah i'm surely not fond of GitHub :-), but we can advertise it on maybe?
<civodul>definitely on the guix-science list, prolly help-guix
<civodul>maybe you could clarify in the README.rst what kind of contributions are accepted?
<civodul>like if it's only FSDG-compliant packages, if it's partly seen as a "staging" area for Guix, etc.
<PurpleSym>I know, it’s just where all of my work-related stuff is anyway, so that’s just the easiest path.
<PurpleSym>Okay, sure, will clarify.
<civodul>maybe it should point to "Specifying Additional Channels" in the manual, rather than "Using a Custom Guix Channel"
<civodul>(although that section might look scary with its big warning)
<PurpleSym>True, will fix that as well.
<civodul>PurpleSym: anyway, if you want you can write a short article for and then we can also advertise it on the "bird site"
<PurpleSym>Sure, I can try :)
<civodul>posts are Markdown files at
<civodul>maybe you can also get rekado to design a logo ;-)
<zimoun>PurpleSym: awesome! Thanks !
<PurpleSym>A logo would be really nice indeed :D
<zimoun>yeah cool logo! :-)
<civodul>oh, and what's the GitHub Action thing? how does one use it?
<civodul>(forgive my ignorance!)
<PurpleSym>You can use it to install Guix into your CI VM.
<PurpleSym>Like this:
<civodul>ah so it takes that VM and runs "guix lint" and "guix build" inside of it, right?
<civodul>so it uses a fixed revision of the guix channel?
<PurpleSym>No, the action uses the installer to install Guix, then runs `guix pull`.
<PurpleSym>You can see it here:
<PurpleSym>Would be nice if there was a “nightly” installer, which would avoid the costly `guix pull`.
<civodul>the action runs every time you push to guix-science?
<PurpleSym>And for pull requests.
<PurpleSym>And every sunday I think.
<civodul>oh so it must be expensive
<civodul>discontinuous integration
<civodul>(better than continuous disintegration anyway)
<PurpleSym>Yes, exactly.
<zimoun>civodul: that’s why a kind of minimal guix package is required. Because this nightly could be done by these kind of “actions” running on temporary VM.
<civodul>hmm? i don't see how this relates
<civodul>i think running "guix pull" every time is necessarily inefficient
<civodul>nightly builds could reduce that cost
<civodul>but a guix-minimal package wouldn't help, as i see it
<zimoun>because if I want to build nightly my version of Guix (and not the manual), I need to fetch a lot of substitutes (or rebuild them) because of graphviz. And sometimes I cannot cache.
<civodul>unless it's already built that is :-)
<civodul>yeah i see what you mean
<civodul>if we provide pre-built tarballs, we can sidestep that
<efraim>I always wanted to run guix pull and then split it off for all the builds but I don't think I've gotten that figured out
<civodul>PurpleSym: you can be the first to fetch the latest binary tarball from
<PurpleSym>civodul: Wow, that was quick. Thank you! Just need to figure out how to integrate it into… Maybe patch it to accept a tarball as an argument?
<zimoun>PurpleSym: yeah, that could nice to fallback to GNU_URL and otherwise use another URL provided at CLI
<civodul>PurpleSym: we owe it to mothacehe, not me :-)