bug#64762: Guix sometimes doesn't support most packages for i686-linux and armhf-linux

Hey, I spotted this issue a few days ago, but I'm still pretty confused by it. Both instances of the data service have sometimes been reporting only a small number of package derivations for i686-linux and armhf-linux. I think the first revisions to exhibit this on the master branch for the two d

bug#64760: make check fails on 182be30fb1a8b847c30492462ec22c08ec7a9849

Hi Janneke, Janneke Nieuwenhuizen writes: > Hi, > > Make check gives three failures for me on current master > > FAIL: tests/packages (package->bag) > FAIL: tests/store-roots (gc-roots, initial) > FAIL: tests/texlive (texlive->guix-package, meta-package) > > using this sn

bug#64760: [PATCH 2/3] tests: store-roots: Initial gc-roots should be empty.

From: Josselin Poiret * tests/store-roots.scm ("gc-roots, initial"): Set expected result to empty. Also do not error out if /profiles doesn't exist. --- tests/store-roots.scm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tests/store-roots.scm b/tests/store-roots.scm in

bug#64760: [PATCH 1/3] tests: packages: Set system for expected result of package->bag.

From: Josselin Poiret * tests/packages.scm ("package->bag"): Parameterize the expected result by the system used to lower the package to a bag. --- tests/packages.scm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tests/packages.scm b/tests/packages.scm index 2b7ab01f7d

bug#64760: [PATCH 3/3] tests: texlive: Remove texlive-texworks from propagated-inputs.

From: Josselin Poiret * tests/texlive.scm ("texlive->guix-package, meta-package"): Remove texlive-texworks from expected propagated-inputs, as it is now ignored by texlive->guix-package. --- tests/texlive.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/texlive.scm b

bug#64760: make check fails on 182be30fb1a8b847c30492462ec22c08ec7a9849

Josselin Poiret writes: Hi Josselin, >> Make check gives three failures for me on current master >> >> FAIL: tests/packages (package->bag) >> FAIL: tests/store-roots (gc-roots, initial) >> FAIL: tests/texlive (texlive->guix-package, meta-package) >> >> using this snippet.

bug#64762: Guix sometimes doesn't support most packages for i686-linux and armhf-linux

Christopher Baines writes: > To confirm that this is an issue with the supported systems as reported > by Guix, I had the data service print out the transitive supported > systems for the guix package: > > debug: Starting getting derivations for (i686-linux . #f) > looking at guix package (s

bug#64745: [guix-past] channel derivation broken after recent u-boot update

Hi Ludovic, Thanks a lot for the prompt resolution. Ludovic Courtès writes: > Hi, > > Maxim Cournoyer skribis: > >> It appears that the Guix-Past channel now fails to build like so: >> >> substitute: ^Msubstitute: ESC[Kupdating substitutes from >> 'https://ci.guix.gnu.org'... 0.0%^Msubstitute

bug#64772: TeXlive (specifically LuaLaTeX) has become terribly slow

Hi, i'm building a small document with LuaLaTeX, for that i have use the following manifest --8<---cut here---start->8--- (specifications->manifest (list "texlive-amsmath" "texlive-todonotes" "texlive-xpatch" "texlive-collection-luatex" "t

bug#64775: /run should be cleaned on boot

So, if there are files sitting around in /run, they do not get cleaned up unless it is something guix is already aware of (e.g. /run/setuid-programs). I noticed this when experimenting with: https://issues.guix.gnu.org/61462 Add support for file capabilities(7) Even after a reboot, the lefto

bug#64775: /run should be cleaned on boot

Vagrant Cascadian writes: > [[PGP Signed Part:Undecided]] > So, if there are files sitting around in /run, they do not get cleaned > up unless it is something guix is already aware of > (e.g. /run/setuid-programs). > > I noticed this when experimenting with: > > https://issues.guix.gnu.org/61

bug#64775: /run should be cleaned on boot

On 2023-07-21, Csepp wrote: > Vagrant Cascadian writes: >> While I know that Guix does not really follow the FHS in most respects, >> maybe the intention of /run defined there should still be respected? >> >> https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s15.html >> >> 3.15. /run : Run-

bug#64774: RISC-V 64 Python 3.10.7 build failure when building git 2.41.0 @ commit eb12f3f

Hello, The command `guix shell -s riscv64-linux -Kc $(($(nproc)/2)) git` fails due to test failures while building Python 3.10.7. Notably, creating a shell with just Python (so, swapping "python" for "git" in the command) works fine. Here is my channel information: ``` (channel (name

bug#64593: ‘guix system image’ fails to create image while invoking ‘grub-bios-setup’

Hello, as it was after discussion with Ludovic that he posted this bug report, let me express my opinion as a simple user. it's just a matter of consistency: very basically, the examples mention grub-bootloader. With the default image type (efi-raw), it's been working perfectly for years (mayb

bug#64593: ‘guix system image’ fails to create image while invoking ‘grub-bios-setup’

Hi Ludovic, shouldn't it be `(bootloader grub-efi-bootloader)` if you're building a `efi-raw` image? With efi grub it builds and boots just fine, as I've tested before submitting the patch. Ludovic Courtès writes: Hello, There seems to be a recent regression: $ cat mini-os.scm (use-mod

bug#64775: /run should be cleaned on boot

> > I vote for TMPFS, since that would also reduce flash wear. > > Honestly I don't get why it's not already using TMPFS. > > One argument could be how much ram it takes: > > $ du -sc /run/* > 12 /run/blkid > 0 /run/booted-system > 0 /run/current-system > 1312/run/se

bug#48018: [PATCH core-updates 2/4] gnu: imagemagick: Fix converting webp images

Fixes . * gnu/packages/imagemagick.scm (imagemagick)[inputs]: Add libwebp. --- The comments in the code imply that this could be applied to master, but `guix refresh` claimed it to have over 3 000 dependents. Go figure. gnu/packages/imagemagick.scm | 2 ++ 1 fi

bug#64753: compute-guix-derivation

Hello! I can't update my Guix derivation for a few weeks. Here's the output: Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Authenticating channel 'guix', commits 9edb3f6 to 6547d38 (2 231 new commits)... Building from this channel:  guix https://

bug#64782: Installing guile-imanifest in Profile Causes Problems with Guix

Hello All, I have recently tried to expand my use and knowledge of guile libraries, and in doing so came across guile-imanifest, which is meant to be a library to create guix manifests interactively. However, upon installing it in my guix-home profile, I found that it propagates the guix package…

bug#64736: pipewire doesn't provide libspa-libcamera.so

Alexandre Hannud Abdo writes: > Uou, thank you. Let me know if and how I can help. Best, .~´ > I had submit patches for it at https://issues.guix.gnu.org/64767. It builds fine, but I haven't test the camera (no camera here), it will be good if you can test it... It can be fetched in a local gui

bug#64663: obs is broken (does not open window)

This problem was resolved for me with the trick from the thread at help-guix "OBS Studio memory leak": Robby Zambito <…> writes: > Guillaume Le Vaillant <…> writes: > >> It looks like an issue with the shader cache of mesa. >> After clearing it, I don't see the memory leak anymore. >> >> Could yo

bug#64783: Build of texlive-font-maps fails

Dear Guix Hackers, I see consistent failures of the package texlive-font-maps. It logs the error: updmap [ERROR]: The following map file(s) couldn't be found: updmap [ERROR]: dvips35.map (in builtin) updmap [ERROR]: pdftex35.map (in builtin) updmap [ERROR]: ps2pk35.map (in