bug#70954: No 'guix pull' substitutes for foreign distros?

Hello Guix! I have two systems: first (A) is a full Guix system and second (B) is a foreign distribution with Guix package manager installed onto. I have noticed when I'm performing 'guix pull' system B always build 'guix pull' derivations by itself while system A most often just download sub

bug#70838: guix pull fails

> As pointed by Chris [1], this report seems a duplicate of #70663. Now, > it should be fixed. Could you try again “guix pull” with a recent > revision? yes that guix pull was successful -Jeremiah

bug#70877: guix-daemon fails to copy 4+GB file to store

BTW, the newly updated ‘guix’ package is 8% smaller, as a result of : --8<---cut here---start->8--- $ guix describe Generation 302 May 12 2024 23:29:11(current) guix 89cd778 repository URL: https://git.savannah.gnu.

bug#70943: linux-libre is not reproducible (regression)

Hello, I've investigated non-determinism in our linux-libre package, which sadly appears to have regressed in that regard since I last looked into it 3 years ago (see commit 01ea70a29c5c1ded31c37ce8c43192bc1956b2ca ("gnu: linux-libre: Make build reproducible.")). I'm currently seeing these differ

bug#69308: linux-libre-documentation fails to build

Hi, Gabriel Wicki writes: > linux-libre-documentation fails to build (see > https://ci.guix.gnu.org/build/3512631/details) This was fixed by Tomas in b6f82b9ef1a3d51a39995598eab9f793656e9123 ("gnu: linux-libre-documentation: Fix compilation."). Closing! -- Thanks, Maxim

bug#70663: nss@3.99 is really hard to build

Hi Maxim, Maxim Cournoyer writes: > Christopher Baines writes: [...] >> At least from what I can see on the issues, the problem was introduced >> with the update to 3.98.0 [3] and then continued with the update to 3.99 >> [4]. Given the changes in 70662 were sent to guix-patches and then >> mer

bug#70663: nss@3.99 is really hard to build

"pelzflorian (Florian Pelz)" writes: > Hello Christopher. > > Christopher Baines writes: >> Had the changes waited for longer, then these failures should have been >> spotted by QA, I would guess that the revision might have failed to be >> processed, and if it was processed successfully, the ns

bug#70663: nss@3.99 is really hard to build

Maxim Cournoyer writes: >> Before closing this bug, it would be good to understand more about how >> this happened and from that try to think if anything can be done to >> prevent similar issues in the future? >> >> At least from what I can see on the issues, the problem was introduced >> with th

bug#70663: nss@3.99 is really hard to build

Hi, Christopher Baines writes: [...] >> I think there's two issues here, was this spotted before merging, and >> what if anything can be done about this now. Where there's not a >> substitute available for nss@3.99, this will affect guix pull/guix >> time-machine, e.g. >> >> → guix time-machi

bug#70932: FAIL tests/guix-shell.sh

When attempting to update the guix package, I got this failure. The test log makes no sense though, as it's trying to test for errors, so I have no idea where to start in working out what is wrong. I thought maybe the issue was here: guix shell: error: package intelmetool@4.7 does not support a

bug#70663: nss@3.99 is really hard to build

Hello Christopher. Christopher Baines writes: > Had the changes waited for longer, then these failures should have been > spotted by QA, I would guess that the revision might have failed to be > processed, and if it was processed successfully, the nss failures should > have shown up, so maybe we

bug#70662: Scheduling a new release?

Hi, On 08/05/2024 14:01, Christopher Baines wrote: I think it would be nice to have a new release, and indeed release more often, I think the way to get there is for less things to be broken between releases, such that releasing takes less effort in terms of testing and fixing things. To give s

bug#70838: guix pull fails

Hi Jeremiah, On lun., 13 mai 2024 at 21:05, jerem...@pdp10.guru wrote: >> That’s said, could you confirm (guix describe) that you are currently >> pulling from 0f68306268773f0eaa4327e1f6fdcb39442e4a34? > yes guix describe does display that checksum. > >> I think ’nss’ is substitutable, so I guess

bug#70838: guix pull fails

Hi Chris, On lun., 13 mai 2024 at 18:45, Christopher Baines wrote: >> Hum, I do not know what could be the origin of the failure. Maybe on >> your side (free space). Or maybe hardware specific? > > See https://issues.guix.gnu.org/70663 , that nss derivation is really > hard to build so it's no

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, you can control the tests b

bug#70781: Same situation in GuixSD install

Hello Kristofer. Even though I do not understand at all how to get into such a state, it appears using an older guix has helped you before, so you could try running /var/guix/profiles/per-user/dev/current-guix--link/bin/guix instead of guix. Regards, Florian

bug#70663: nss@3.99 is really hard to build

Christopher Baines writes: > nss@3.99 is really hard to build, it's so hard and so important that > data.guix.gnu.org is still after two days trying to process [1]. I say > so important because you have to build nss@3.99 to compute the channel > instance derivations for Guix. > > 1: https://data.

bug#70910: xdot has stopped working after update to 1.3

Hi all, I've tested the patch on a fresh checkout. LGTM! Thanks for looking into this, Ludo', Artyom! Warmly, Ada