IRC channel logs


back to list of logs

<PurpleSym>The environment.scm is not working for me, unless I change guile-syntax-highlighting into guile-syntax-highlight
<zimoun>PurpleSym: I do not think guile-syntax-highlighting is/was the name of a Guix package.
<zimoun>Or maybe it was long time; but ’git log --oneline | grep guile-syntax-highlighting’ returns nothing.
<zimoun>Well, I do not know what is the context. :-)
<civodul>PurpleSym: thanks! i'll check that environment.scm
<civodul>otherwise "guix shell -D hpcguix-web" should work
<PurpleSym>Oh, I did not realize we had a package in Guix proper.
<rekado>I wonder if r-build-system has a problem
<rekado>I just built simplermarkdown after patching its references to pandoc
<rekado>but the resulting package has no reference to the pandoc package
<rekado>none of the source files I patched made it to the output
<rekado>there’s just and rdx and rdb file, but they are gzipped.
<rekado>I worry that other packages that we’ve patched with references to the store won’t prevent the GC from collecting their dependencies.
<civodul>hey ho!
<zimoun>civodul: oh thanks for the quick fix about git-download and SWH.
<civodul>zimoun: now we'll have to check whether it actually fixes the CRLF issue :-)
<civodul>it's a nice bug that you found!
<zimoun>The patch somehow reads (invoke "git" "clone" …) which means to have the plain git-minimal instead of libgit2, right? If yes, why?
<civodul>git-minimal is already what's used in that file
<civodul>see #:git-command
<zimoun>yep, I have seen. :-) Do you remember why?
<zimoun>My attention had never been attracted by that. :-)
<zimoun>Because plain Git allows some features for clone that libgit2 does not implement as shallow.
<civodul>it's just that it was easier to implement and yeah, shallow clones are nice
<civodul>we don't need tight integration in this context, so less of an incentive to use Guile-Git
<civodul>(it's very different from the channel code from that perspective)
<zimoun>ok, thanks for the explanations.
<zimoun>I willl drift another day. ;-)
<zimoun>civodul: test done and fix works. Cool! But it will be unpractical at scale. Well, let discuss with SWH folks. :-)
<civodul>or inconvenient?
<zimoun>well, the cooking is already slow for some cases, and here it is much much slower – that’s for the inconvient part.
<civodul>oh didn't know it would be slower than the "flat" thing
<civodul>long ago they offered to pre-cook revisions that correspond to Git tags
<zimoun>For the impractical part, well, I am doubtful it will work for large repository with many files and with a large history too.
<civodul>or revisions that we refer to in packages.json
<civodul>ah true, getting a copy of the whole repo can be a problem
<civodul>i didn't even think about that :-)
<civodul>so yes, maybe not the best approach
<civodul>if it's just CR/LF, we can just as well implement it ourselves?
<zimoun>I think the best approach is try flat and fallback to git-bare
<civodul>fall back, how? when? :-)
<civodul>devil is in the details
<zimoun>yeah, I agree. :-)
<zimoun>A checksum would be necessary in the download part.
<zimoun>Well, for now it is only CR/LF so yeah maybe fix that ourself could be an option. Applying .gitattributes if any.
<zimoun>civodul: let me know what you think about v2 of #61910 :-)
<civodul>rekado, PurpleSym: do you have a public instance of Cuirass and/or 'guix publish' at your institute?
<civodul>i'm trying to document practices in this area
<PurpleSym>We do have
<PurpleSym>Which is driven by
<civodul>neat, thanks
<civodul>PurpleSym: so you're not using Cuirass, right?
<PurpleSym>civodul: Nope, for what we do we don’t need CI, just the pre-built substitutes.
<civodul>ok, and you build the relevant packages "manually" more or less?
<civodul>or maybe that's triggered by psychnotebook usage?
<PurpleSym>I’m using your cron script 🙂
<PurpleSym>And everything else comes from Guix’ substitute servers.
<civodul>oh nice :-)
<PurpleSym>Nowadays guix weather chokes on the manifest though ☹️
<PurpleSym>So I’m also running a script to bake nars – one by one – in a tmux pane 🤦‍♂️
<civodul>chokes, like how?
<civodul>efraim: is managed by Arun? i'm also curious about the setup
<PurpleSym>Not sure, but it seems to ignore guix-cran entirely for some reason.
<PurpleSym>(I think guix build does too, not just guix weather)
<PurpleSym>Maybe I should switch to cuirass when I move to a bigger server… That server currently shuts down when I try to install Guix though. Very weird.
<civodul>indeed :-)
<efraim>civodul: I think so
<civodul>efraim: apparently it's running Laminar, but do you know more? is there a public "guix publish" instance as well?
<efraim>civodul: there's one at
<civodul>awesome, thanks!
<civodul>rekado, PurpleSym, efraim: here's a draft post about CI/CD with Guix:
<civodul>the goal is to make something approachable by sysadmins not familiar with Guix so they get a feel of what can be done
<civodul>Todd Gamblin of Spack presented their WIP on CI at FOSDEM:
<civodul>so you could think of it as the Guix take on that topic
<civodul>as always, feedback welcome!
<zimoun>civodul: hum, I probably messed up something somewhere… about #61343 (channels and guix repl)
<zimoun>because 1. the patch is fixing “guix repl” and not “guix repl script.scm”.
<zimoun>and 2. (current-profile) does not seem to do the correct.
<zimoun>Messed something because I am sure to have run the test in the patch! Anyway.