@ekaitz_zarraga Are there instructions somewhere on how to test it?

(Don’t hold your breath though, I think it’s too late for Guile 3.0.9.)

@ekaitz_zarraga I guess the only thing I miss is a RISC-V board? :-)

With my #Guile hat on, I can tell you that being able to test complex setups in a single command is pretty cool. Example:

guix build guile-next --with-git-url=guile-next=$HOME/src/guile \
--with-branch=guile-next=main --target=x86_64-w64-mingw32

Those #Guix folks are doing a great job. 😇

#Guix gets a new ‘--with-version’ package transformation option, to deploy a specific package version straight from upstream!
https://guix.gnu.org/manual/devel/en/html_node/Package-Transformation-Options.html#index-upstream_002c-latest-version

@ekaitz_zarraga The closure of ‘vim-full’ is at 825 MiB, which is better but not brilliant either. :-)

#Guile has a new ‘spawn’ procedure that wraps ‘posix_spawn’, and ‘system*’, ‘open-pipe’ and friends are now based on ‘posix_spawn’ as well!
https://issues.guix.gnu.org/52835

More robust & more efficient thank fork+exec. 👍
Kudos to Josselin!

Am I the only one to find “lock file” a poorly chosen term when referring to a file that specifies package versions or similar?

To me a “lock file” is, well, a ‘.lock’ file as you can find them in /var/run & co.

#PyTorch victim of a “supply chain” attack:
https://pytorch.org/blog/compromised-nightly-dependency/#how-to-check-if-your-python-environment-is-affected

It boils down to “dependency confusion” (really: confused deputy problem), where PyPI packages refer to dependencies by name, which (surprise!) is ambiguous.

Another good illustration for https://hpc.guix.info/blog/2021/09/whats-in-a-package/.

#GNU #Guix 1.4.0 released! 🎉
https://guix.gnu.org/en/blog/2022/gnu-guix-1.4.0-released/

So many exciting things since 1.3.0, starting with ‘guix shell’ and Guix Home. Check it out!

Plus, it comes with cute artwork by @luis_felipe.

Thanks to the tireless work of @cbaines, the #Guix issue tracker at https://issues.guix.gnu.org now includes “QA” badges that link to https://qa.guix.gnu.org, showing whether patches apply, build, and add new packages that build fine.

This qa.guix.gnu.org automation is a game changer. 👍

TIL: “FORTRAN” stands for “Formula Translating System”.

Shouldn’t a formula translating system remain the horizon for #HPC developers and users, as opposed to manipulating bits and bytes in C?

💡 #Guix question: What do the checks that ‘--skip-checks’ skips check?

Answer 👇

#GNU #Guix 1.4.0rc2 is available for testing!
👉 https://lists.gnu.org/archive/html/guix-devel/2022-12/msg00145.html

Just fiddled with a bunch of VMs imperatively using ClusterSSH. For someone used to declarative deployment, it feels lighthearted and brittle.

“Let’s hope we don’t need to redeploy them ever” is the thought that came to mind.

“Stay Together for the Kids” (Andrew Kelley)
https://www.youtube.com/watch?v=stChOsejLEQ

Hilarious talk shared on guix-devel about the conflict between “system package managers” and “language package managers”.

The speaker explains how they went to great lengths trying to address the “JavaScript packaging dystopia” @cwebber famously described some years ago, eventually managing to get their NodeJS app in Debian. Amazing, and insightful.

“We speculate that the availability of distributions such as Guix and NixOS that apply reproducibility to support the deployment of reproducible systems, as well as Debian will lead to the use of R-Bs in long-term software maintenance becoming commonplace.”

Here’s hoping they’ll be proved right.

“On business adoption and use of reproducible builds for open and closed source software”
https://link.springer.com/article/10.1007/s11219-022-09607-z

Alright, the title didn’t attract me at first :-) but it’s a well-documented overview of #ReproducibleBuilds work, and the study gives interesting insight into industry practices.

@w96k @cwebber Fun fact: until recently, GCC’s code was very much “Lisp in C”, with dynamic typing and garbage collection. Working with the ‘tree’ type and related code was similar to working with libguile in C. (That was until Google employees pushed for C++, and shortly before their employer found greener pastures for them to go to.)

@ekaitz_zarraga I was a bit afraid too but it turned out to be an opportunity for an overdue spring/summer cleanup for me. Easy satisfaction. :-)

#Guix Home now has an OpenSSH service, to populate ~/.ssh/config & co.!
https://guix.gnu.org/manual/devel/en/html_node/Secure-Shell.html