bug#71211: %guile-static-stripped crashes with a sigsegv (i.e. the guile used in the initrd (?))

2024-05-26 Thread Attila Lendvai
root symptom: - i think this is the guile binary that is used in initrd. it's been a while i noted this bug. but if it's so, then if error happens early in the boot, then it just dies with a sigsegv; i.e. it's a major hindrance to debuggability. reproducer: --- guix shell

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

2024-05-26 Thread Maxim Cournoyer
Hi, Maxim Cournoyer writes: > 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 reproducib

bug#71133: linux-libre-guix.tar.xz CI times out on aarch64-linux

2024-05-26 Thread Christopher Baines
Richard Sent writes: > On aarch64 platforms, the linux-libre-guix.tar.xz.drv build times out > [1]. > > This package is known to have a long build time [2]. > > Users can work around this by running the build locally with a (very, > very large) max-silent-time (~28800 seconds on my machine). Give

bug#71133: linux-libre-guix.tar.xz CI times out on aarch64-linux

2024-05-26 Thread Richard Sent
Christopher Baines writes: > This derivation seems to have been built fine by the bordeaux build > farm: > > > https://data.guix.gnu.org/gnu/store/ny56fdcig9cd9bd3pssmlraz2c1q10q8-linux-libre-6.8.10-guix.tar.xz.drv You're right. It looks like the derivation itself built fine based on that, bu

bug#71133: linux-libre-guix.tar.xz CI times out on aarch64-linux

2024-05-26 Thread Christopher Baines
Richard Sent writes: > Christopher Baines writes: > >> This derivation seems to have been built fine by the bordeaux build >> farm: >> >> >> https://data.guix.gnu.org/gnu/store/ny56fdcig9cd9bd3pssmlraz2c1q10q8-linux-libre-6.8.10-guix.tar.xz.drv > > You're right. It looks like the derivation i

bug#71214: bordeaux linux-libre-6.8.10-guix.tar.gz corrupt nar

2024-05-26 Thread Richard Sent
Hi Guix! The nar for /gnu/store/y813phs2n9xnb7zbcr07g0j9509bzbsb-linux-libre-6.8.10-guix.tar.xz on Bordeaux seems to have been corrupted by some mechanism. The URL in question is > URL: nar/none/y813phs2n9xnb7zbcr07g0j9509bzbsb-linux-libre-6.8.10-guix.tar.xz >From comments by cbaines on an earli

bug#71133: linux-libre-guix.tar.xz CI times out on aarch64-linux

2024-05-26 Thread Richard Sent
New issue opened at https://issues.guix.gnu.org/71214. I'l close this one. Thanks! -- Take it easy, Richard Sent Making my computer weirder one commit at a time.

bug#71217: gnu: home: dotfiles: Files not excluded when they should

2024-05-26 Thread Nicolas Odermatt-Lemay
Hello, While attempting to setup home-dotfiles-service, I noticed that some files were being symlinked even though they were in the variable `%home-dotfiles-excluded', such as all the files of the .git directory. This patch seems to fix the problem : diff --git a/gnu/home/services/dotfiles.scm b

bug#64734: Recursive hackage import fails

2024-05-26 Thread Saku Laesvuori via Bug reports for GNU Guix
> Hi, > > > $ guix import hackage linear-generics --recursive > > have you ever figured out what caused this? Yes, I fixed it in https://issues.guix.gnu.org/67564 so this issue can now be closed. - Saku signature.asc Description: PGP signature

bug#64734: Recursive hackage import fails

2024-05-26 Thread Saku Laesvuori via Bug reports for GNU Guix
close 64734 thanks signature.asc Description: PGP signature

bug#70349: Clang fails to communicate RUNPATH?

2024-05-26 Thread Liliana Marie Prikler
Hi Ludo, Am Samstag, dem 25.05.2024 um 11:26 +0200 schrieb Ludovic Courtès: > Could this be an issue specific to ‘meson-build-system’? > > For instance, this works fine (both mpfr and mpc use > ‘gnu-build-system’): > >   guix build mpc --with-c-toolchain=mpfr=clang-toolchain > > If we add this

bug#62890: Likely cause found, excess library grafting

2024-05-26 Thread Richard Sent
Hi Guix! Once again I sunk more time into this issue when I should have been sleeping. Here's what I found: Building a grafted stumpwm directly creates one stumpwm:lib output. Building it /indirectly/ as a dependency of, say, sbcl-stumpwm-cpu, creates another, distinct stumpwm:lib output. This di

bug#47115: Another occurence in the wild

2024-05-26 Thread Richard Sent
Hi Guix! I believe I found another instance of this bug coming back to haunt unfortunate, wayward souls. (including me! 😭). https://issues.guix.gnu.org/62890 -- Take it easy, Richard Sent Making my computer weirder one commit at a time.