System log (syslogd) for the Shepherd

Hello Guix! I recently pushed a ‘wip-syslogd’ branch in the Shepherd, which should be ready to merge in ‘devel’ in the coming days. It implements an in-process “system log” service that does the same job as good’ol syslogd as currently used in Guix System (info "(inetutils) syslogd invocation").

Re: Reducing "You found a bug" reports

Hi, Simon Tournier skribis: > On Mon, 17 Jun 2024 at 14:59, Ludovic Courtès wrote: > >>> It doesn’t feel great to tell users to report a bug for things that >>> aren’t bugs. They’re either closed, or never followed up on; it’s a >>> poor experience on both end

Re: EU NGI funding cut engagement opportunity

Hi! Ekaitz Zarraga skribis: > On 2024-07-21 01:15, Juliana Sims wrote: >> Greetings comrades, >> As many of you are likely already aware, the European Union has >> recently made plans to cut funding to its Next Generation Internet >> (NGI) initiative which funds hundreds of FOSS projects,

Re: Update default Golang version on go-team branch

Hello Sharlatan, Sharlatan Hellseher skribis: > I had a courage to refresh the default Goang version to build packages > from 1.17 to 1.21 as all version before it are already EoL. After > rebuilt 900+ packages locally I've fixed some failing to build packages. > > The packages in golang-build

Re: ‘core-updates’ rebased: testing needed!

Leo Famulari skribis: > On Mon, Jun 17, 2024 at 11:30:37PM +0200, Ludovic Courtès wrote: >> 1. Checking whether your favorite packages build and work. > > Libreoffice is blocked on core-updates, due a build failure of > libetonyek, caused by a bug in Boost: > > htt

Re: ci.guix.gnu.org is getting back to life

Hello! Ludovic Courtès skribis: > • We upgraded the Honeycombs (AArch64) and POWER9 build machines. At > this stage 3 AArch64 and 2 POWER9 build machines are fully > operational behind ci.guix: > > https://ci.guix.gnu.org/workers > > Another

Re: Should we document how to detect if build machines are reachable before trying to offload?

Hi, Sergio Pastor Pérez skribis: >> Do you remember exactly under what circumstances it hangs? I think >> ‘guix offload’ should handle that situation gracefully and we should fix >> it if it does not. > > Yeah. It happens when I have a build machine configured like so and I > disconnect it

Re: Sustainable funding and maintenance for our infrastructure

Simon Tournier skribis: > Well, from my perspective, the question is architecture per > architecture. I mean, I think it’s doable to find sponsor (companies or > academic institutions) for x86_64 because it’s commonly used. And > that’s not the case for less used others. In the past we got

Re: bug#69456: Cuirass 1.2.0-2.7bcd3d0 (and manual): latest install image not available for download (wrong URL?)

Hello, Giovanni Biscuolo skribis: > IMO there is a bug in the CI UI > > Tanguy LE CARROUR writes: > >> In order to test the latest installer, I went to the "latest download" >> page [1] and clicked on "x86_64-linux" under "GNU Guix System on Linux" >> and ended up on an error page [2]: >> >>

ci.guix.gnu.org is getting back to life

Hello! Last month, we discussed¹ slow progress with builds (and ‘core-updates’ in particular) on ci.guix, especially on AArch64 and POWER9. Those turned out to be mostly due to scalability issues in Cuirass. Likewise, the front page at https://ci.guix.gnu.org was timing out for almost two

Re: New North American based Guix Substitute Server, cuirass.genenetwork.org Now Available

Hi Collin, "Collin J. Doering" skribis: > I am excited to announce that Guix substitutes (for x86_64) are now available > in North America, thanks to the generous contribution of server hardware and > infrastructure from GeneNetwork.org. > > This new server enhances the availability and

Re: How to invoke shepherd action from shepherd action?

Hi, Tomas Volf <~@wolfsden.cz> skribis: > I am currently in the process of writing a new service, and I have run into > bit > of a wall. I need to invoke shepherd action after my one-shot service > finishes. > > The code (relevant bits) for my service is pretty simple: > > (define

Re: Should we document how to detect if build machines are reachable before trying to offload?

Hello! Sergio Pastor Pérez skribis: > I recently discovered that offloading builds to remote machines[1], > hangs when the machines are not available; instead of defaulting to > building locally[2]. This forces the user to use the `--no-offload` > flag. Do you remember exactly under what

Re: Sustainable funding and maintenance for our infrastructure

Vagrant Cascadian skribis: > On 2024-07-02, Ludovic Courtès wrote: >> We (Andreas, Chris, Ricardo, Romain, and myself) were having a >> discussion about what it would take to set up a build farm similar to >> what’s behind ci.guix: roughly 30 x86_64 servers, with 32-c

Re: Sustainable funding and maintenance for our infrastructure

Hi, Efraim Flashner skribis: > Looking at Hetzner, they have an option to rent a dedicated ARM server > with 80 cores/threads with 256GB of RAM and 2x3.84 TB NVMe drives for > under €300/month and a €94 setup charge. Correct me if I"m wrong, but > that one box is ~20x our current active

Re: Sustainable funding and maintenance for our infrastructure

Hello, Simon Tournier skribis: > However, the implicit question is a chicken-or-the-egg problem: in order > to know what we would like to invest in, we need to know how much we > would be able to invest; and to know how much, we need to determine for > what. We currently have ~50k USD at the

Re: [bug#71876] [PATCH] gnu: ci: Cross-build for fewer platforms.

Hi, Efraim Flashner skribis: > * gnu/ci.scm (%dead-platform-triplets): New variable. > (cross-jobs): Also don't build for systems listed in > %dead-platform-triplets. > > Change-Id: Ic31ae6d307f2d243c098ec050bdb9d09060466ac [...] > +(define %dead-platform-triplets > + ;; These systems are

Sustainable funding and maintenance for our infrastructure

Hello Guix! We (Andreas, Chris, Ricardo, Romain, and myself) were having a discussion about what it would take to set up a build farm similar to what’s behind ci.guix: roughly 30 x86_64 servers, with 32-core/64-thread CPUs and 128 GiB of RAM. The reason for this discussion is that we were

Sustainable funding and maintenance for our infrastructure

Hello Guix! We (Andreas, Chris, Ricardo, Romain, and myself) were having a discussion about what it would take to set up a build farm similar to what’s behind ci.guix: roughly 30 x86_64 servers, with 32-core/64-thread CPUs and 128 GiB of RAM. The reason for this discussion is that we were

Re: 01/03: gnu: clang-15: Fix building on i686-linux.

Hey Efraim, guix-comm...@gnu.org skribis: > + ;; The build daemon goes OOM on i686-linux on this phase. > + ,@(if (and (version>=? version "15") > + (target-x86-32?)) > +'((delete 'make-dynamic-linker-cache))

Re: Next Steps For the Software Heritage Problem

Hi, Ian Eure skribis: > While this is what their paper claims[1], it doesn’t appear to be > true, since I can see my own GPL’d code in the training set. I’ve > since moved nearly all of my code off GitHub, but if you visit their > "Am I in The Stack?" page[2] and enter my old username

Re: Our mips64el support is really really dead

Efraim Flashner skribis: > I suggest that we stop cross-compiling packages to mips64el since it is > really dead-dead, and not just mostly-dead or nearly-dead. Agreed. Maybe send a patch, Cc’ing guix-devel, and apply after two weeks if there are no objections? Ludo’.

Re: ci.guix.gnu.org homepage is down

Hi Ada, Ada Stevenson skribis: > I just wanted to send an email out to let people know that the > homepage of CI, ci.guix.gnu.org, is down. It returns a 504 Gateway > Timeout error. Thanks for the heads-up! We’ve been aware of this for a few days, with some discussions on guix-sysadmin

Re: An IRC bot called Peanuts

Hi, Leo Famulari skribis: > It's an opinion. I wish that whoever said that would have said it in a > more friendly way. We try to avoid communicating so harshly within Guix > and I hope they learn to do that. We not only try, we actually enforce a code of conduct. (This one was a private

Re: Of Guix London, Guix Social, and a Guix outreach group

Hello! Fabio Natali skribis: > - Guix London will be renamed to Guix Social. > - We'll be starting a "Guix outreach group", open to everyone who wants > to discuss/organise events and social activities.  Lovely. Super happy to see you all continue this initiative; it’s proved very

Re: New procedure to modify operating-system records

Hi Sergio, Sergio Pastor Pérez skribis: > I'm writing this mail from a system that grafts `mesa` for the > `nvidia-driver` available in [1]. Although I'm aware that this is not > the place to discuss proprietary stuff, this is not about running an > NVIDIA system. This enables any Guix user to

Re: Debugging failing shepherd startup

Hi maya, m...@zenmaya.xyz skribis: > I have an issue with my Guix configuration. From a certain update my > system fails to boot. It successfully boots into kernel and starts > shepherd. But after that shepherd fails to activate some necessary > service and the system is softlocked. > > The

Re: Starting a Quality Assurance Meeting/Team/Sociocracy circle

Hi Christopher, Christopher Baines skribis: > Following on from the governance discussion at the Guix Days earlier > this year, I'm not sure what progress has been made. None, I’m afraid, so what you propose is a great step in that direction. OTOH, teams are picking up steam, and AIUI, the

Re: Next Steps For the Software Heritage Problem

Ian Eure skribis: > Guix sends archive requests to SWH. SWH gives that source code to > HuggingFace. HuggingFace demonstrably violates the licenses. Which licenses? As has been said previously, and you can verify for yourself, it does not ingest code under copyleft licenses. Ludo’.

Re: ‘core-updates’ rebased: testing needed!

Hello! 宋文武 skribis: > Hello, there are 399 build failed which only on core-updates if I count > it correctly (1 at the end of each line come from ci status, I think 2 > are for dependencies failed), the 4xx are build number, which can be > used as

GNU Shepherd 0.10.5 released

[ undef ] Ludovic Courtès uid [ undef ] Ludovic Courtès uid [ undef ] Ludovic Courtès (Inria) If that command fails because you don't have the required public key, or that public key has expired, try the following commands to retrieve or refresh it, and then rerun

Re: Disabling authentication checks for tests in local Guix checkouts

Suhail Singh skribis: > Ludovic Courtès writes: > >> I’m not sure how to integrate it though: in the general case, we >> probably want to keep authentication enabled by default, but how to >> allow users to easily disable it when using a personal checkout? > > Coul

‘core-updates’ rebased: testing needed!

Hello! I have just rebased ‘core-updates’ on ‘master’ (commit bd5c61781c13611ed16686513980907c6ee34ae6): 6e5ecfd0fb7 gnu: libarea: Fix build. 41e2cd0dd0e gnu: txr: Add missing input. 1c27fa835d9 gnu: grass: Fix build. 399a4e8afd3 gnu: python-magic: Adjust test suite. 8e6ad35f1d7 gnu:

Re: "guix pack -f docker" does too much work

Hi, Michal Atlas skribis: >>> Also seems that Nix's way only quickly imports the changed layers? And >>> Guix's always imports the whole thing, at least I think? >> What do you mean by “imports the whole thing”? > > I'm not sure what exactly happens, so correct me if I'm wrong, however > if I

Re: [PATCH Cuirass v2] cuirass: Fix handling of SPECIFICATION-NAME.

Romain GARBAGE skribis: > Fixes a regression introduced in > 1da873b0e23eceb3c239dd6dc6781debf23bec63, where the NAME field of the > SPECIFICATION record type is forced to be a symbol as stated by the > documentation. > > * src/cuirass/base.scm (jobset-registry): Handle SPECIFICATION-NAME as a >

Re: [PATCH Cuirass] cuirass: Fix handling of SPECIFICATION-NAME.

Hi! Romain GARBAGE skribis: > Fixes a regression introduced in > 1da873b0e23eceb3c239dd6dc6781debf23bec63, where the NAME field of the > SPECIFICATION record type is forced to be a symbol as stated by the > documentation. Yay, that was fast! > * src/cuirass/base.scm: Handle SPECIFICATION-NAME

Re: [PATCH maintenance] hydra: services: Reload nginx when certbot updates certificates.

Hi, Carlo Zancanaro skribis: > * hydra/modules/sysadmin/services.scm (%certbot-deploy-hook): New > variable. > (%certbot-job): Pass %certbot-deploy-hook to certbot invocation. Applied, thanks! > I think this patch should resolve the certificate issue more > permanently. I haven't tested it at

Re: networking service not starting with netlink-response-error errno:17

Hi Giovanni, Giovanni Biscuolo skribis: > after a reboot on a running remote host (it was running since several > guix system generations ago... but with no reboots meanwhile) I get a > failing networking service and consequently the ssh service (et al) > refuses to start :-( > > Sorry I've no

Re: [PATCH Cuirass 1/4] specification: Ensure name is a symbol.

Hi, Ludovic Courtès skribis: > I’ve applied the whole series to Cuirass: > > 81d2530 * http: Add /admin/gitlab/event. > 10cf59f * gitlab: Add module for Gitlab JSON objects definition. > 1da873b * specification: Ensure name is a symbol. After doing some more testi

Re: Guix + GNUNet update ?

Hi Noé, Noé Lopez via "Development of GNU Guix and the GNU System distribution." skribis: > I was looking at the previous GSoC projects page and the GNUNet project > seems really cool to me. I had already dreamed about having > decentralized substitutes, so I would love to have this. I would

Re: New mumi am subcommand

Howdy Arun! Arun Isaac skribis: > First, set the current issue (say 61036). > > $ mumi current 61036 > > Then, apply the latest patchset using > > $ mumi am > > You may also apply a patchset of a specific version (say, v3) using > > $ mumi am v3 Woow, very nice! (Also great that pages at

Re: Disabling authentication checks for tests in local Guix checkouts

Hi Ada, Ada Stevenson skribis: > I'm currently trying to help test the changes to GRUB submitted in > issue #71348[1]. Unfortunately, `make check`, whilst building the > local Guix channel, authenticates every commit. That means commits not > signed by people in `guix-authorizations` will stop

Re: [PATCH] cuirass: check for null on specification edition page.

Hi, Jaming skribis: > From a5a99b1a7f930614bd88cadfe7a3470805403d48 Mon Sep 17 00:00:00 2001 > From: Justin Martin > Date: Sun, 9 Jun 2024 11:20:25 -0400 > Subject: [PATCH] cuirass: check for null on specification edition page. > > * src/static/js/cuirass.js: check '.remove-channel' for null.

Re: Reducing "You found a bug" reports

Hi, Ian Eure skribis: > Is there some way for this code to be smarter about when it prints the > "report a bug" message, so it doesn’t tell users to report bugs when > none exist? Is there a way for it to notice that the problem is > related to networking, and tell the users to try again in a

Re: CLISP test failures on ‘core-updates’

Guillaume Le Vaillant skribis: > Guillaume Le Vaillant skribis: > >> Maybe the CI just had a hiccup... I restarted the build, maybe it will >> be enough. > > It looks like it worked. Oh well, thanks for taking a look! Ludo’.

Re: /run/setuid-programs via the Shepherd?

Hi Juliana, Juliana Sims skribis: > To bring this email back to directly the topic you raise, a Shepherd > run0 is complementary to a future ocaps-ification of the broader > process environment; they support and reinforce each > other. Furthermore, with ocaps, the Shepherd could grow beyond

Re: Disabling Shepherd services across reboots?

Hi, Felix Lechner via "Development of GNU Guix and the GNU System distribution." skribis: > Is there a way to disable Shepherd services across reboots without > reconfiguring the system? No, it’s not supported (I never thought about this use case). > If not, what is the purpose of 'herd

Re: Call for contribution to the Guix infrastructure

Hi Zach, Zach Oglesby skribis: > I would be happy to give a hand, but I am not sure that I qualify as a > known guix community memeber. I have been around a while and am also > active in the system crafters community. I also had access to Fedora > Infrastructure for years to work on docs build

Re: Call for contribution to the Guix infrastructure

Hi Wilko, Wilko Meyer skribis: > Ludovic Courtès writes: >> - Improve infra monitoring: set up a dashboard to monitor all the >> infrastructure, and an out-of-band channel to communicate about >> downtime. > ... >> - Support mirror

qa.guix delays in processing patches

Hi Philip, "Philip McGrath" skribis: > For some reason QA still doesn't seem to be working for > https://issues.guix.gnu.org/71203 (a Racket update I sent on May 26), which I > suspect may be related to this. Could someone take a look? > > The page at https://qa.guix.gnu.org/issue/71203 says

Little progress on powerpc64le and aarch64 builds on ci.guix

Hello! Andreas Enge skribis: > Am Thu, Jun 06, 2024 at 07:48:27PM +0200 schrieb Andreas Enge: >> Could the graph on >>https://ci.guix.gnu.org/metrics >> be augmented by the number of packages to be built for the different >> architectures? That would be nice, I agree (I haven’t looked much

Re: Are 'guix gc' stats exaggerated?

Andreas Enge skribis: > In my experience on ext4 (also not backed by looking at the code), "guix gc" > always deletes substantially less than what I ask for. I always thought it > just counted hard linked files even when the link count does not go to 0 > and the file is not actually deleted.

Re: "guix pack -f docker" does too much work

Hi, Michal Atlas skribis: > I greatly agree, it would be an awesome QOL improvement. If there’s consensus, let’s see how we can get that done. The advantage of having (guix docker) & co. all in Scheme is that moving it from a derivation to code running straight from ‘guix pack’ is definitely

Re: [PATCH Cuirass 1/4] specification: Ensure name is a symbol.

Hi Romain, I’ve applied the whole series to Cuirass: 81d2530 * http: Add /admin/gitlab/event. 10cf59f * gitlab: Add module for Gitlab JSON objects definition. 1da873b * specification: Ensure name is a symbol. I took the liberty to merge the commit that adds test with the one that defines

Disappearing development installation images

Hello Guix! We got a couple more reports that installation images at would disappear. After investigating, it turns out we had a periodic job on berlin removing GC roots for *.iso and *.qcow2—no wonder they’d disappear earlier than expected. That job

CLISP test failures on ‘core-updates’

Hello Lisp team! :-) The ‘clisp’ package has a few test failures on ‘core-updates’ (x86_64-linux): --8<---cut here---start->8--- finished 57 files: 6 errors out of 11,960 tests 1 alltest:0 errors out of 636 tests 2

Re: Call for contribution to the Guix infrastructure

Hello Carlo, Carlo Zancanaro skribis: > On Fri, May 24 2024, Ludovic Courtès wrote: >> • Day-to-day system administration >> >> We’re also looking for people who’d be willing to have SSH access to >> some of the infrastructure to help with day-to-day mai

Re: Come speak at the Guix Social meetup

Hi Steve, Steve George skribis: > We're looking for speakers - of any level - to give talks at the Guix online > meetup. We're a small, friendly group at all levels of experience. Talks can > be about anything Guix associated, for example: That’s a great initiative! It would probably make

Re: Improving the speed of guix time-machine for development environments

Richard Sent skribis: >2. Less maintainence burden to regularly update pinned commits, >particularly as a channel dependency tree grows. > > I feel that soft-pinning strikes a balance between those two goals that > is useful when dependencies on a frequently updated channel are unlikely

Re: CI is not processing jobs

Hi Guix! Ludovic Courtès skribis: > Ludovic Courtès skribis: > >> The longer story is that Ricardo noticed that the build backlog had been >> growing for a couple of months (see “Pending builds”): >> >> https://ci.guix.gnu.org/metrics >> >> We

Re: A paper about Plan 9 and Guix

Hi Edouard, Edouard Klein skribis: >> I wonder to what extent the combination of ‘make-inetd-constructor’ and >> ‘least-authority-wrapper’ would fit the bill for you? (This is currently >> used for the bitlbee, dicod, and rsync services.) It seems to address >> the main shortcomings listed in

Re: Are 'guix gc' stats exaggerated?

Hi Felix, Felix Lechner via "Development of GNU Guix and the GNU System distribution." skribis: > It probably makes more sense to focus on the Guix daemon here. I hope > you don't mind a few clarifying questions. > > Why, please, does the benefit of de-duplication approach a fixed ratio > of

Re: 02/02: gnu: linux-libre: Update to 6.9.

Hi Leo, guix-comm...@gnu.org skribis: > commit 5d3edff1a604414a3c42b89fcbc007e9d573993d > Author: Leo Famulari > AuthorDate: Sun Jun 2 16:48:44 2024 -0400 > > gnu: linux-libre: Update to 6.9. > > * gnu/packages/linux.scm (linux-libre-version, linux-libre-gnu-revision, >

Re: Improving the speed of guix time-machine for development environments

Hi Richard, Richard Sent skribis: > If I want to use time-machine as part of entering a development > environment for some channel collection and a new guix commit is pushed, > then the next time I invoke that same time-machine command there will be > a large delay as Guix fetches,

Re: CI is not processing jobs

Hi, Ludovic Courtès skribis: > The longer story is that Ricardo noticed that the build backlog had been > growing for a couple of months (see “Pending builds”): > > https://ci.guix.gnu.org/metrics > > We discussed this on guix-sysadmin and found that this was due to the

Re: CI is not processing jobs

Hi Lars, Lars-Dominik Braun skribis: > I’d like to merge the haskell-team branch. Changes are rather small > this time, but I still need CI to build the branch to be able to assess > the damage done. Unfortunately Cuirass has not been processing scheduled > jobs of this evaluation[1] for about

Re: I'm retiring (for a while); help needed

Hi! jbra...@dismail.de skribis: > I've done some web work in the past. I could probably help with the > bootstrap -> pico move. I’m also interested in helping land it. Did you have a preliminary branch for this, Ricardo? Thanks for the heads-up! Ludo’.

Re: Call for contribution to the Guix infrastructure

Hi Jonathan, Jonathan Brielmaier skribis: > Am 24.05.24 um 15:51 schrieb Ludovic Courtès: >>• Hosting >> >> We’re looking for people who can host machines and help out whenever >> physical access is needed. More specifically: >> >>

Re: How to write a compute-file producing utf8 output?

Tomas Volf <~@wolfsden.cz> skribis: > I am currently struggling when trying to create a computed-file producing > internationalized content. Simple reproducer is: I think you found out in the meantime :-), but for posterity, one possibility is to set ‘%default-port-encoding’: (fluid-set!

Re: Changes to managing branches

Hi, Christopher Baines skribis: > I've now merged the most recent batch [1] of changes to the process for > managing patches and branches. There was a previous thread on guix-devel > discussing the changes here [2]. > > 1: https://issues.guix.gnu.org/70549 > 2:

Re: Shepherd log rotation service

Hi, Felix Lechner skribis: > I should will make an immediate dent in my 200 MB log file for Fcgiwrap, > but not for an Rspamd file of similar size. Also, my Nginx log file > with 1.3 GB will remain unaffected. Most significantly, it simplifies a > lot of code. Right. I think we should

Re: Shepherd log rotation service

Hi Felix, Felix Lechner skribis: > Sorry to double up on my messages. I might further rename the somewhat > generic sounding %default-calendar-event to %default-rotation-event, or > perhaps even %default-rotation-calendar-event. Good idea, I’ll do that. > Also, the #:compression parameter

Re: How to test fixed output derivations in the bordeaux build farm?

Hi! Christopher Baines skribis: > I've had a look at the GUIX_DOWNLOAD_METHODS environment variable, which > is looked at by the url-fetch procedure, but this seems to work by > generating different derivations, rather than changing the behaviour of > the derivation at build time. Yes. You

Re: Upgrading Shepherd services

Hello! Felix Lechner via "Development of GNU Guix and the GNU System distribution." skribis: > (define (garbage-collector-shepherd-service config) FWIW, if it can help, I have something very similar in my config: --8<---cut here---start->8--- (define

Re: Improving the speed of guix time-machine for development environments

Hi Richard, Richard Sent skribis: >> I think channels listed in channels.scm files should optionally support >> using whatever channel version is already in the user's profile, if >> present. This would significantly speed up entering development >> environments composed of Guix channels. > >>

Call for contribution to the Guix infrastructure

Since its inception, the Guix project has always valued its autonomy, and that reflects in its infrastructure: our servers run Guix System and exclusively free software, none of them is hosted by one of these transnational companies, and they’re administered by volunteers. Of course this comes at

Postmortem of service downtime

From Sunday May 19th to Tuesday may 21st, for about 36h, bayfront.guix.gnu.org, the machine behind many services went down: https://lists.gnu.org/archive/html/info-guix/2024-05/msg0.html Affected web sites and services included: guix.gnu.org bordeaux.guix.gnu.org logs.guix.gnu.org

Re: `make check` fails when trying to build from Git

Hi, Ashvith Shetty skribis: > $ file > /home/ashvith/Desktop/guix/test-tmp/store/a2k16z6jzwzvvg00bhf4mf9v0k65r7kq-guile-bootstrap-2.0/bin/guile > /home/ashvith/Desktop/guix/test-tmp/store/a2k16z6jzwzvvg00bhf4mf9v0k65r7kq-guile-bootstrap-2.0/bin/guile: > empty This suggests that this file is

Shepherd log rotation service

Hello Guix! I’ve just pushed a simple log rotation service for Shepherd: https://git.savannah.gnu.org/cgit/shepherd.git/commit/?h=devel=0484726801c2b5c1b7deecb9a96054c2c510ac71 It rotates log files roughly the same way we’ve been doing since the 70’s, but there’s a couple of advantages

Re: Upgrading Shepherd services

Hi Felix, Felix Lechner via "Development of GNU Guix and the GNU System distribution." skribis: > I have a lot of custom Shepherd services. Every so often I make a > mistake that stalls the step in 'guix deploy' that upgrades Shepherd > services, but without any error messages. > >

Re: [PATCH 0/1] Possible fix of the Cuirass build with the latest Guix

Hi, Rodion Goritskov skribis: > Got some problems due to the change re-exports in (guix utils). > Also, should I send patches for Cuirass here or to the guix-patches? Good catch! I see that Maxim fixed these issues just recently; it should be fine now. Thanks, Ludo’.

Re: `make check` fails when trying to build from Git

Hi Ashvith, Ashvith Shetty skribis: > while setting up the build environment: executing > `/home/ashvith/Desktop/guix/test-tmp/store/a2k16z6jzwzvvg00bhf4mf9v0k65r7kq-guile-bootstrap-2.0/bin/guile': > Exec format error What does this command return: file

Re: Guix pull: avoiding "Computing Guix derivation"

Hi, Edouard Klein skribis: > - Why is this step not substitutable ? The inputs are known, a hash can > be derived, a substitute server could be queried for an output of that > hash ? What am I missing ? Does the guix derivation not end up in the > store ? What makes it so special that it can't

Re: New mumi www and mumi compose subcommands

Hello, Arun Isaac skribis: > $ mumi current 22138 > #22138 Search paths of dependencies are not honored > opened on 10 Dec 2015 09:36 by Ludovic Courtès > > $ mumi www > [opens the issue in your web browser] > > $ mumi compose > [opens your mail client to com

Re: Re-activate Coirass specification

Hi, Sharlatan Hellseher skribis: > In the end I've deactivated golang-team specification attempting to > resurrect already existing go-team one, but there is no any UI option to > re-activate the specification. It may well be the case that one has to spawn ‘psql’ on the machine and change the

Re: Demystifying SSH configuration for remote software forges on Guix System

Hi, Ashvith Shetty skribis: > And finally, I've come across `home-openssh-service-type` - which I've yet > to try, but reading from the docs, am I supposed to put my private and > public keys in the repository? How do I go about this? Isn't that a > security risk? Never ever put private keys

Re: time-bomb and CI? (was bug#69800: kcalendarcore time-bomb)

Hi, Simon Tournier skribis: > Other said, would it be possible to have one (or more) node that build > with a date in the future? Say 3 years. In Bordeaux? Or in Berlin? > Using the “Dolorean VM” [2], it could be nice to setup one node. [...] >

Re: Scheduling a new release?

Hi Christopher, Christopher Baines skribis: > While releases will still require bursts of effort, I think we need a > more sustainable approach to actually achieve more frequent releases. I think this is largely an organizational problem. As discussed at the 2023 Guix Days (!), we could

Re: [PATCH] gnu: glibc: Update patches following upstream's master branch.

Hi, Josselin Poiret skribis: > From: Josselin Poiret > > * gnu/packages/patches/glibc-2.39-git-updates.patch: New patch. > * gnu/local.mk (dist_patch_DATA): Register it. > * gnu/packages/base.scm (glibc): Use it. > > Change-Id: I13ff3fa2eddd8296d138f87c9069487e9543b3bd > --- > How about the

Re: `make check` fails when trying to build from Git

Hi Ashvith, I pushed the commits below, which should address the two failures you reported: 7ca9809cdbf tests: Skip ‘terminal-string-width’ test on encodings other than UTF-8. 723d45866f1 tests: Remove interference from the user’s Git config. Lemme know if that helps! Thanks, Ludo’.

Re: bug#40316: nss not reproducible

Hi, Christina O'Donnell skribis: > On 06/05/2024 11:12, Ludovic Courtès wrote: [...] >> For sure I’d be happy if the test suite could run faster, but does >> upstream offer such an option? When you say “a single pass”, is that >> something upstream supports? > Yes, y

Re: `make check` fails when trying to build from Git

Hi Ashvith, (Cc: guix-devel.) Thanks for the logs! They show two test failures: Ashvith Shetty skribis: > test-name: terminal-string-width Japanese > location: /home/ashvith/Desktop/guix/tests/syscalls.scm:590 > source: > + (test-equal > + "terminal-string-width Japanese" > + 6 > +

Re: Core updates status

Hi Josselin and all, Josselin Poiret skribis: > Maxim Cournoyer writes: >> Josselin Poiret writes: [...] >>> I'm worried this will keep accumulating a bunch of world rebuilds, >>> slowing down c-u some more. I'd vote to keep the pkgconf switch for >>> later and focus on merging the rest of

Re: `make check` fails when trying to build from Git

Hi, Steve George skribis: > Hi Ashvith - are you building the master branch with a recent checkout? > > I also get some FAILS, but not as many as you. It would be nice if you could report it: the list of FAILs and the corresponding .log files. Also please mention how you run them: Guix System

Re: bug#40316: nss not reproducible

Hi, Christina O'Donnell skribis: > Tangentially, given how long nss takes to build, do you think that > it'd be worth shaving it down to a single test pass? Currently it runs > each test up to 3 times, which takes ~1h on my machine with no other > build running. Running only the standard pass

Re: Changing the defaults for --localstatedir and --sysconfdir?

Hi, Ricardo Wurmus skribis: > Ludovic Courtès writes: > >> At this point I think defaulting >> to /var and /etc would do more good than harm. > > Are those the only defaults that should change? These are the only ones > we are actively using, but perhaps it

Re: Changing the defaults for --localstatedir and --sysconfdir?

Efraim Flashner skribis: > On Thu, May 02, 2024 at 02:58:39PM +0200, Andreas Enge wrote: >> Am Thu, May 02, 2024 at 11:00:15AM +0200 schrieb Ludovic Courtès: >> > That was 8 years ago though (eight!). At this point I think defaulting >> > to /var and /etc would do mor

Re: Concerns/questions around Software Heritage Archive

Hi Ian, Ian Eure skribis: > Summarizing the situation: > > - SHF has an opaque, difficult, and undocumented process for > handling name changes. I’s like to stress again that this is > *not* strictly a transgender issue (though it likely affects them > more, or in worse/different ways)

Re: Value in adding Shepherd requirements to file-systems entries?

Hi! Richard Sent skribis: > Before hacking away at this myself, I'd like to get other people's > thoughts on the best way to proceed. Do others agree that (file-system) > entries should support networked devices? Should this be transparent > depending on the type, or require explicit

Re: Potential security issue with make authenticate and mitigation

Hi! John Kehayias skribis: > In 2020, the "guix git authenticate" tool was added in order to secure > updates (1). This protection is still intact! The tool also had the > secondary effect of protecting developers against malicious commits > while we are developing. In fact, the manual

  1   2   3   4   5   6   7   8   9   10   >