A minimal rootless podman configuration

Existing attempts to use podman rootless run into issues with the cgroups file system being mounted by elogind. Since we now have seatd and greetd, we can bypass elogind. Using them, I have finally been able to use rootless podman. Since this is something that comes up in IRC with some regul

Preservation of Guix (PoG) report 2023-03-13

Hi Guix, It’s been a while! :) Allow me to present to you a long-overdue update to the Preservation of Guix (PoG) report: . 🎉 Note that you can link to the most recent version of the report using . What is this?

Re: The 🐑 Shepherd gets a service collection

I imagine we could develop more convenient services like this, such as basic command scheduler similar to the ‘at’ command, and a syslogd implementation. The latter could be nice for a couple of reasons: logging would happen from the start and till the end (an improvement over the external syslo

Towards generalized testing (Was: Caching test results separately?)

Hi Josselin, On Mon, Mar 13, 2023 at 3:21 PM Josselin Poiret wrote: > > I would really like for tests to move out of build phases > > That would require a huge change to Guix though Fortunately, there is a great precedent for that work in Debian. It is called autopkgtest. [1] One package I main

Re: Caching test results separately?

--- Original Message --- On Monday, March 13th, 2023 at 10:21 PM, Josselin Poiret wrote: > But I would really like for tests to move out of build phases I've mentioned this previously in IRC as well. Fundamentally, it strikes me as wrong that a change which only affects tests, leaving

Re: Caching test results separately?

Hi, "Dr. Arne Babenhauserheide" writes: > Hi, > > A large part of the build time is being consumed by tests … could we > separate those phases so a package whose tests succeeded once does not > have to be rebuild just because its package got garbage collected? > > (⇒ keep the test result (boolea

Re: The 🐑 Shepherd gets a service collection

Thanks! PS: It just occurred to me that we might as well rename the new (shepherd service …) hierarchy to (shepherd sheep …) or even (shepherd 🐑 …). Its a shame that Directed Acyclic Graphs are part of Guix verbiage, as otherwise Id be suggesting the name 'dags'. (Dags are the yellowe

Caching test results separately?

Hi, A large part of the build time is being consumed by tests … could we separate those phases so a package whose tests succeeded once does not have to be rebuild just because its package got garbage collected? (⇒ keep the test result (boolean) longer than the build result) Keeping just a boolea

Re: bug#61894: [PATCH RFC] Team approval for patches

There is a phenomenon in manufacturing quality control where sometimes adding inspectors decreases the number of defects that get past inspection unnoticed, because one inspector catches a defect that another inspector missed, but other times the number of unnoticed defects actually goes UP, pr

The 🐑 Shepherd gets a service collection

Hello Guix! I pushed some changes yesterday that confirm that the Shepherd paves the way for init system innovation, synergistic cross-domain fertilization, and delimited continuations: https://git.savannah.gnu.org/cgit/shepherd.git/log/?id=31d21fa083872d500c016b6b3b2587d25510702d 31d21fa *

Re: Using Guix inside a Guix container

Hi Konrad, On sam., 18 févr. 2023 at 10:21, Konrad Hinsen wrote: > Both examples are about composing tools freely, without worrying if they > use Guix internally or now. Thanks for explaining and the use-cases. Well, maybe a discussion for gwl-devel… well, I have started one. :-) Cheers, si

Re: State of core-updates

Hi, On ven., 10 mars 2023 at 15:58, Andreas Enge wrote: > let me start with a call for help! I realise that it takes me about one > week and something close to 100GB on my poor 2-core laptop to rebuild > the bulk of core-updates up to the packages in my profile, and that is not > sustainable. It