bug#57134: [PATCH] powerpc64le: gst-plugins-good build link error on aalib (libgstaasink.so)

Hi Marcel, Marcel van der Boom writes: > * gstreamer.scm (gst-plugins-good): > skip aalib input on ppc64le I managed to find the root issue in aalib and sent a patch fixing it in https://issues.guix.gnu.org/65646. -- Thanks, Maxim

bug#65560: You found a bug:

guix pull Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Authenticating channel 'guix', commits 9edb3f6 to 5856e18 (61,866 new commits)... Building from this channel: guix https://git.savannah.gnu.org/git/guix.git 5856e18 substitute: updating substit

bug#65471: home mcron service overwrites PATH with a GuixSD-only directory

Hello, when using the home-mcron-service, PATH is set to /run/current-system/profile/bin . This directory is empty when using guix home on a foreign distro, meaning all executable paths would need to be absolute. This includes stuff like /usr/bin/ssh, /usr/bin/nice etc.. My guess for the cul

bug#64571: harfbuzz package has a duplicated definition

Hi, Yes, that fixed the issue. Thanks. On Fri, Aug 18, 2023 at 8:07 PM Simon Tournier wrote: > > Hi, > > On Tue, 11 Jul 2023 at 11:15, Jean-Pierre De Jesus Diaz via Bug reports for > GNU Guix wrote: > > > guix shell harfbuzz > > guix shell: warning: ambiguous package specification `harfbuzz'

bug#65587: secrets crashes on launch

Traceback (most recent call last):   File "/gnu/store/xm51sy8wrzvf5ls6x5ls3cp03c45zr11-secrets-6.5/bin/.secrets-real", line 66, in     main()   File "/gnu/store/xm51sy8wrzvf5ls6x5ls3cp03c45zr11-secrets-6.5/bin/.secrets-real", line 57, in main     from gsecrets.application import Application

bug#65522: Documentation for some home services disappeared from 1.4 manual

Hello, I noticed some help nodes under https://guix.gnu.org/en/manual/en/html_node/Home-Services.html disappeared fairly recently. They are still available in the devel docs under https://guix.gnu.org/en/manual/devel/en/html_node/Home-Services.html The following topics are missing: * GPG: GNU

bug#65606: Cuirass Compute Guix Derivation Bug

This error occurred on a Cuirass system using guix 4dfdd82 on a Guile project. cuirass-compute-guix-derivation.log Description: Binary data

bug#65572: Black screen in installer

Hello, I'm trying to install Guix system on an i386 laptop. When the installer should reach the GUI, only a black screen is displayed. I tried to boot by editing Linux boot parameters in GRUB and set `nomodeset` and removed `quiet`. Now without `quiet` I saw the following messages before the blac

bug#65521: Error updating qtwayland

Hello, I'm getting an error when running guix upgrade The error occurs with qtwayland as it tries to upgrade 6.3.2 to 6.5.2 The error happens during the check phase after the build phase is complete  The error message is:  building /gnu/store/jdp3jwd4yac606pglqvc500qifjrs6xm-qtwayland-6.5.2.d

bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that)

Hi Arne, "Dr. Arne Babenhauserheide" writes: [...] > Please don’t remove packages that are broken on the CI. I often had a > case where no substitute was available but the package built just fine > locally. This is not a perfect situation (nicer would be to track why it > doesn’t come from CI

bug#65633: python-selenium raises a WebDriverException because driver is not found in PATH

Hi Guixers, I'm adding this as a future TODO for myself or anyone else that would like to work on it. python-selenium fails with the following when webdriver.Chrome is called: driver = webdriver.Chrome('./chromedriver') File "/gnu/store/hz5k0k0lggsn6j2ij49xriawbwrq988n-profile/lib/python3.1

bug#54447: cuirass: missing derivation error

Maxim Cournoyer writes: > I wonder if these could be related to the DDoS protection discovered on > the Berlin network. I'll keep looking for other, potentially different > occurrences. Hello, this one for ddd: https://ci.guix.gnu.org/build/1372655/log/raw cannot build missing derivation ?

bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that)

[...] Maxime Devos writes: The first part looks reasonable to me (though I would decrease 7 days to daily or even hourly, as I don't see a point in the delay), but how does the second part (removing packages) make sense at all? I mean, if you do that: 1. Build failures happen (independent of

bug#65594: [feature] [qa] Notify users by email of problems

Maxim Cournoyer writes: > Hi, > > This is a feature request for QA: I think it'd be nice if it sent > notifications by email when a submitted patch or series has any kind of > issues, such as lint warnings, newly introduced breakage, etc. > > That'd be less clicking around to navigate to the info

bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that)

Maxim Cournoyer writes: > Believe it or not, I actually did! :-) I was replying to the first part > of your message, where you mentioned you were against packages removal. > My reply was giving support to devising policy that would define when > it's acceptable to prune the distribution of broken

bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that)

Maxime Devos writes: >> Maybe we can automatically report the failures as bugs, say every 7 >> days, and remove a package if it still fail to build in 90 days? > > The first part looks reasonable to me (though I would decrease 7 days > to daily or even hourly, as I don't see a point in the delay)

bug#65614: cgroups increase to 65555 preventing docker to start

Hi, when I try to start a docker container, I get the erro docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: mkdir /sys/fs/cgroup/docker/dac0a619a2d6f980095c74a6a2