Notices by Ludovic Courtès (civodul@toot.aquilenet.fr)

There’s a patch adding a Hetzner backend to ‘guix deploy’:
https://issues.guix.gnu.org/75144

I think that’s pretty cool.

#Guix

@crowdagger Mais donc oui, peut-être « pensé » ?

@VioB

@crowdagger Je me suis toujours demandé d’où venait ce mot, mais Wiktionary a une théorie :
https://en.wiktionary.org/wiki/thunk#Etymology_3

@VioB

Du coup j'ai eu un doute mais oui c'est possible (j'ai pas réussi à le faire avec defmacro parce que skill issues)

@csantosb Definitely, we should do that! I had to fix a couple of minor issues this morning, but really, I’m totally sold.

@mousebot

I played with it some more and this fj.el thingie by @mousebot is looking great already!
https://codeberg.org/martianh/fj.el

#Emacs #Forgejo #Codeberg

@hisham_hm À bientôt à Bruxelles ! 👍

@cwebber Amazing. :-)

What’s that “phone” that runs Guix?

@csantosb I would say that niche scientific packages should definitely go to Guix-Science.

Also, contributing to Guix-Science is usually deemed easier, first because it’s on a forge of the kind most people are familiar with, with a clear feedback loop, and second because it’s a small repo without the ./bootstrap && ./configure && make step.

@daviwil As one of the folks trying to keep Guix infra afloat, I would rather reduce its scope than increase it right now.

But one thing that I find important is plausible self-hosting. And indeed that’s something we get with Forgejo, much less with GitLab (which is much more complex and cannot realistically be packaged in Guix).

Sounds like the right stance to me for anyone who cares about the human beings out there and about free-software-for-freedom:
https://drewdevault.com/2025/01/16/2025-01-16-No-Billionares-at-FOSDEM-please.html

@Guillawme That’s something for the community to decide but I’m willing to propose it once I have enough confidence, hopefully soon (maybe that’ll be the first RFC?).

@zimoun No, not yet.

‘gitea.el’ and ‘forgejo.el’ in https://github.com/magit/forge are still almost empty.

Just now I tried ‘fj.el’ by the amazing @mousebot. There are rough edges (I didn’t manage to view the body of messages, almost!) but it looks promising: simple to use, convenient, and with apparently good coverage of the API.

I should say I’m pretty happy with the workflow we have on Codeberg and the many tiny features that overall make it easier to keep track of pull requests and ensure they reach the right people.

It’s routine for anyone who’s been using a “modern forge” but it’s good to see concretely how it could play out for a project like Guix.

“Join the Guix-Science community!”
https://hpc.guix.info/blog/2025/01/join-the-guix-science-community/

Where we #ReproducibleResearch and #HPC users of #Guix report on our adventure moving to #Codeberg, coming up with suitable CI/CD support, and call for like-minded #OpenScience folks to join!

@zwol In particular, I doubt eudev can be restarted currently; I would definitely remove it from the list.

Restarting ‘networking’ is obviously risky and doesn’t bring much; restarting ‘syslogd’ is less risky but not super useful IMO.

Always amazed that when yt-dlp doesn’t work (it was unable to fetch an audio track in my case), you can run ‘guix shell --with-latest=yt-dlp yt-dlp -- yt-dlp …’ and it just works.

@zwol Oh, I see, weird. (So you had (reboot? #t) in the unattended upgrade config, IIUC?)

@zwol How exactly did it “crash”? Any idea what happened?

I’ve been using it on a server for a long time and so far, so good.

In a recent stream, I started using the Fibers library for Guile Scheme to learn more about how it enables Go-style concurrency in Scheme programs.

Here's a clip from that stream where I explain what Fibers is for, read through an example snippet using channels, and set up a basic HTTP request handler that uses Fibers' own server backend.

Let me know what you think about the clip format!

https://youtu.be/fYyZuYKjmWc

#guile #scheme #golang #programming