bug#74217: Bootstrapping Zig with no Binary Blobs

2024-12-01 Thread Efraim Flashner
On Sun, Dec 01, 2024 at 09:32:01PM +0200, Motiejus Jakštys wrote: > On Fri, Nov 29, 2024 at 2:25 PM Hilton Chain wrote: > > > > On Fri, 29 Nov 2024 04:53:57 +0800, > > Motiejus Jakštys wrote: > > > > > > [1 ] > > > On Thu, Nov 28, 2024 at 5:20 PM Hilton Chain wrote: > > > > Thanks! Then I'll ke

bug#74217: Bootstrapping Zig with no Binary Blobs

2024-12-01 Thread Hilton Chain
On Thu, 28 Nov 2024 19:08:09 +0800, Hilton Chain wrote: > > Made "#:zig-inputs" a private keyword, its value will be passed to inputs like > cargo-build-system (the build system doesn't extract the whole closure for > now, this can be added in the future depending on how Zig ecosystem develops). J

bug#74032: Disarchive certificate expired

2024-12-01 Thread Maxim Cournoyer
Hello, Jakob Kirsch writes: > Hello, > it looks like the HTTPS certificate for https://disarchive.guix.gnu.org/ has > expired 2 weeks ago. > > Could someone refresh it? Thanks in advance. Thanks for the report; that's since been fixed, although if it keeps reoccurring, we should look for a mor

bug#74217: Bootstrapping Zig with no Binary Blobs

2024-12-01 Thread Motiejus Jakštys
On Fri, Nov 29, 2024 at 2:25 PM Hilton Chain wrote: > > On Fri, 29 Nov 2024 04:53:57 +0800, > Motiejus Jakštys wrote: > > > > [1 ] > > On Thu, Nov 28, 2024 at 5:20 PM Hilton Chain wrote: > > > Thanks! Then I'll keep abilists removed before we can reproduce one :) > > > > OK here it is for 0.11:

bug#72686: Impossible to remove all offload machines

2024-12-01 Thread Ian Eure
Hi Maxim, Maxim Cournoyer writes: Hi Ian, Ian Eure writes: [...] The only other option I can see would be to keep the existing filenames for user configuration, and declaritively manage different files -- like declaritive-channels.scm. This comes with its own set of problems, like nee

bug#74632: ‘guix publish’ crashes with “Signals delivery fails constantly”

2024-12-01 Thread Ludovic Courtès
Ludovic Courtès skribis: > I would seem that only one GC-enabled thread is not cooperating (not in > a ‘sigsuspend’ call): the one in ‘fdatasync’. Here’s a counterexample where every thread seems to be cooperating: --8<---cut here---start->8--- (gdb) info thr

bug#74632: ‘guix publish’ crashes with “Signals delivery fails constantly”

2024-12-01 Thread Ludovic Courtès
Ludovic Courtès skribis: > 2024-12-01 15:32:52 Signals delivery fails constantly at GC #284 > 2024-12-01 15:32:52 Signals delivery fails constantly Backtrace: --8<---cut here---start->8--- (gdb) info threads Id Target Id Frame 1LWP

bug#63368: Build coordiantor "Signals delivery fails constantly" crashes

2024-12-01 Thread Ludovic Courtès
Christopher Baines skribis: > Since the recent core-updates merge, I've seen the build coordinator > using less memory, but it's also been crashing in a new way, up to 10 > times a day. > > In the log, you see something like: > > 2023-05-07 09:15:42 Signals delivery fails constantly at GC #7105

bug#74632: ‘guix publish’ crashes with “Signals delivery fails constantly”

2024-12-01 Thread Ludovic Courtès
‘guix publish’ on ci.guix regularly crashes with SIGABRT and gets respawned: --8<---cut here---start->8--- 2024-12-01 15:32:36 GET /qzqxm94y500p94sx8k3l2qqd8i8dgcvc.narinfo 2024-12-01 15:32:36 -> GET /qzqxm94y500p94sx8k3l2qqd8i8dgcvc.narinfo: 404 2024-12-01 15:3