Email or username:

Password:

Forgot your password?
81 posts total
Ludovic Courtès

Glad to be joining the fine #Guix London Meetup crowd led by @futurile and @fabionatali for a discussion about Guix, Guile, and life at 7PM CEST today!
libreplanet.org/wiki/Group:Gui

Show previous comments
Anthk

@civodul @futurile @fabionatali
I wish Guile-Studio got an SICP-compat layer =)
With the sicp package it would be the ultimate game changer to learn Scheme (and computer science too).

avp

@civodul @futurile @fabionatali That's really good news indeed. I registered to the online meeting and notified my colleagues from Russian Guix community about the oncoming meeting too; maybe some of them will be joining as well.

Ludovic Courtès

Recently (past week?), #Guix proper passed the 30K package limit, all free software!
repology.org/repository/gnugui

Ludovic Courtès

Third-party channels bring tens of thousands more packages.

For scientific usage: hpc.guix.info/channels
General purpose: toys.whereis.xn--q9jyb4c/chann

Ludovic Courtès

It’s 2024. The ACM and its friends are still ripping public money, asking authors for $1,000 to make their paper “open access”.

One word: parasites.

gerry

@redstarfish @civodul It’s even more disgusting than that because #acm.org is a restricted access #Cloudflare site. Some people are allowed to reach it and some are not.

Ludovic Courtès

Good news for declarative config fans: finally there’s a #Guix System service to deploy home environments!
guix.gnu.org/manual/devel/en/h

Thanks to Richard Sent for implementing it, based on code by @abcdw.

Csepp 🌢

@civodul @abcdw This is cool, I wonder if it would be safe to combine this with the auto upgrade service. It would be cool if less technical (or just forgetful) users would get security updates automatically.

dave

@civodul @abcdw nice!! this should hopefully make things like pulseaudio -> pipewire easier since pipewire requires home services.

Ludovic Courtès

It’s now possible to create a #Guix System instance where the default ‘guix’ command sees the channels of your choosing:
guix.gnu.org/manual/devel/en/h

This is particularly useful if you want to create a ready-to-use system image.

Felix Lechner

@civodul Hi, thamks. That's great news! When and how does that "guix" get "pulled" please?

Felix Lechner

@civodul Also, I can't use the custom system channels yet because my Guix is several months behind. How do I disable authentication for the pull, please?

café au fait
@civodul i finally managed to give this a whirl over the last week, and it's very promising. however! the experience on my old desktop was pretty bad. it had to update its channels and rebuild guix's derivation *three* times each for "system build" and "system reconfigure", so it took well over an hour.

but this large annoyance hides a proper bug: since you have to be root to run "system reconfigure" and because that will trigger three separate channel updates and guix rebuilds over a potentially long period of time, it has a high likelihood leave behind root-owned files in the guix cache, requiring manual intervention to fix.

it's a promising start to a vision of being able to easily layer channels on bare guix, but the current implementation needs to stop constantly pulling channels and rebuilding guix. honestly, i don't think anything should ever pull guix except "guix pull". i assume there was some nasty thorn that made you have to do it this way?
@civodul i finally managed to give this a whirl over the last week, and it's very promising. however! the experience on my old desktop was pretty bad. it had to update its channels and rebuild guix's derivation *three* times each for "system build" and "system reconfigure", so it took well over an hour.
Ludovic Courtès

“Towards reproducible minimal source code tarballs?” by @jas4711:
blog.josefsson.org/2024/04/01/

I think “make dist”-generated tarballs are just one part of the xz debacle (and not the most frightening part), but at least we can do something about them: when they’re the byproduct of a build process, we can build them from source (like Debian does); when they add something that’s not in the VCS (such as .po files), we can at least ensure a reproducible build process as Simon advocates here.

“Towards reproducible minimal source code tarballs?” by @jas4711:
blog.josefsson.org/2024/04/01/

I think “make dist”-generated tarballs are just one part of the xz debacle (and not the most frightening part), but at least we can do something about them: when they’re the byproduct of a build process, we can build them from source (like Debian does); when they add something that’s not in the VCS (such as .po files),...

Vivien the Trumpeting Elephant

@civodul @jas4711 As I use the extended GNU build system for my own personal projects, I find it a bit frustrating that the PO files would not be present in the source tree, but I understand that if they were, then we would have a big bunch of undesirable “Update PO translation” commits.

As for Gnulib more specifically, I have noticed that in several places, you can safely commit (semi-)generated files, and rely on syntax-check to detect when they should be updated.

Janneke

@civodul @jas4711
The benefits of Reproducible tarballs are a no-brainer to me.

I've been carrying and developing reproducible source tarball patches for Autotools and GNU Mes for quite some time, party courtesy of Timothy Sample.

I'm embarrassed and confused that after over 10y of Reproducible Builds, GNU and Autotools still need to get used to these ideas (and don't seem to make any progress at all).

Ludovic Courtès

My friends, I made a terrific (terrible?) discovery that goes by the name ‘sdlpop’:
packages.guix.gnu.org/packages

I spent hours on this as a kid and it was great, even though I’m not sure I ever went past level 2 (I didn’t today).

Ludovic Courtès

“Adventures on the quest for long-term reproducible deployment”
guix.gnu.org/en/blog/2024/adve

On addressing build reproducibility problems on “old” packages, in particular time-related, to ensure #ReproducibleBuilds and #ReproducibleResearch with #Guix.

Cc: @reproducible_builds

Ludovic Courtès

“Guix Days 2024 and FOSDEM recap” (Steve George)
guix.gnu.org/en/blog/2024/guix

Great summary of the many friendly and fruitful discussions we had last week!

#Guix #FOSDEM

Ludovic Courtès

“HIP and #ROCm come to #Guix
hpc.guix.info/blog/2024/01/hip

New blog post on the 100+ Guix packages contributed by AMD, our preliminary tests on one the French national supercomputers, and how it can benefit going forward to both AMD and the French and European #HPC environments.

Ludovic Courtès

📺 Videos of the Nov. 2023 Workshop on Reproducible Software Environments for Research and High-Performance Computing are on-line!
hpc.guix.info/events/2023/work

Videos include short interviews with the speakers. Tutorial material is also available from that page.

Many thanks to the speakers and to the video team at Institut Agro!

#ReproducibleResearch #OpenScience #HPC #Guix

Ludovic Courtès

It’s wonderful: mastodon.el now automatically resolves URLs to Mastodon posts, such that you can view these posts and interact with them without ever leaving the comfort of Emacs. 👍

mousebot

@civodul yeah, mastodon-url-lookup can be called on any url. Tusky devs taught me how to implement it, bless em.

Ludovic Courtès

Virtual build machines to the rescue of software archaeologists:
issues.guix.gnu.org/68677

Not just archaeologists actually: it’s something you need to rebuild packages that include “time traps” (fail to build after some time). It’s relatively rare, but when you need them, you’d rather have a simple way to work around the problem.

#Guix #ReproducibleBuilds #ReproducibleResearch

Vagrant Cascadian

@civodul

Also, running builds in the future can help detect time bombs before they happen so that you can fix it now, before it is a more bothersome problem!

I am interested in using this to introduce problems...
changing the clock, kernel, CPU, hostname and username is really useful for #ReproducibleBuilds troubleshooting, as all of these things have been known to affect build results in the wild.

Looking forward to playing with this, thanks!

Csepp 🌢

@civodul I was gonna ask if this could be achieved with namespace but apparently time is not namespaced. Sigh.

David Wilson

@civodul I saw that on one of the mailing lists recently, really excellent design. The Guix community is lucky to have @luis_felipe

Ludovic Courtès

#Guix packagers: you may like these new REPL commands to inspect a package’s configure flags, phases, etc. 👇
guix.gnu.org/manual/devel/en/h

Show previous comments
Csepp 🌢

@civodul I don't quite get why these need to be REPL commands instead of normal functions. 🤔

Janneke

@civodul the ",phases grep" is pretty nice; how would you print grep's phases for --system=i586-gnu?

Sharlatan

@civodul Why not to include the common Guix's modules to load as an entry point? To reduce the number of representative commands:
```
scheme@(guix-user)> ,use (guix)
scheme@(guix-user)> ,use (gnu packages base)
```

Maybe (guix), (guix utils) and some others.

Ludovic Courtès

I made an incredible discovery: xterm, the venerable terminal emulator, can make SVG screen dumps! (And XHTML.) 🤯

(From the menu on control-left-click. How come I never noticed before?)

Ludovic Courtès

Magit-todos-mode is neat but it can make you feel like you’re facing one more set of Sisyphean tasks—Guix in this case.

Go Up