bug#18838: zsh test suite failures

Is this still happening? I searched a bit on ci.guix.gnu.org... We have a failure on 5.8 armhf (already present on 5.7.1 version) but it looks like it is a different set of tests that is failing... -- Vincent Legoll

bug#39924: Issue tracker display multiple times the same issues

When refreshing or relaunching a search, the guix issue tracker displays multiple times the same entries. I cannot reliably trigger it, but it happens often enough. Seen it on chromium & firefox on debian. Any hint to investgate the matter further ? -- Vincent Legoll

bug#39924: Issue tracker display multiple times the same issues

here is a screenshot showing the problem. It looks like the number of shown items is the number of replies to each bug. Maybe they should all be collapsed into a single entry. Or maybe they should link to the indvidual replies with an HTML anchor. -- Vincent Legoll

bug#39925: `guix pull` failure in multi-machine setup

Hi, I’m using guix on a multi-machine setup with a single remote guix-daemon that can be reached via SSH. Thus GUIX_DAEMON_SOCKET=ssh://master. on the compute nodes. Running `guix pull` on master works fine (the variable is not set here), but it does not on a compute node. Instead it fails with th

bug#39926: Regression introduced by Shepherd 0.7.0 ('make check-system TESTS=btrfs-root-os' fails)

Hello, Recently, I noticed that 'make check-system TESTS=btrfs-root-os' stopped working at all, even on master without my changes. So, I've git bisected the faulty commit, and got: --8<---cut here---start->8--- git bisect start # good: [35cb2ac56cce1496c622958

bug#36882: Qemu 4.2.0 build for x86_64-linux fails

Hi! Mathieu Othacehe skribis: >> Yup, turned out patching GCC was too difficult. I'm experimenting a >> filter over inputs passed to set-path-environment-variable in set-paths. > > This is also quite tricky, because the "libc" input passed to set-paths > must not be removed from C_INCLUDE_PATH i

bug#36882: Qemu 4.2.0 build for x86_64-linux fails

Ludovic Courtès writes: > Hi! > > Mathieu Othacehe skribis: > >>> Yup, turned out patching GCC was too difficult. I'm experimenting a >>> filter over inputs passed to set-path-environment-variable in set-paths. >> >> This is also quite tricky, because the "libc" input passed to set-paths >> must

bug#39930: python-virtualenv produces a broken pip when network is available

I am encountering a weird error: | ~/tmp$ guix environment --pure --ad-hoc python python-virtualenv coreutils | ~/tmp% pip3 --version | pip 19.0.3 from /gnu/store/az4z48nrlyhrpkj2njs6xz3p0mj71wi7-profile/lib/python3.7/site-packages/pip (python 3.7) | ~/tmp% virtualenv venv | Using base prefix '/

bug#39926: Regression introduced by Shepherd 0.7.0 ('make check-system TESTS=btrfs-root-os' fails)

Hi Maxim, Maxim Cournoyer skribis: > So, it seems that updating shepherd to 0.7.0 caused this regression > (commit 205c1e04e04b9a9338c7219ff82bd13f000fb8c8). Could it be something similar to , fixed in commit 00500449b0d53bb9219608a3cbee8faf7a3edae1? Thanks, Ludo’.

bug#39925: `guix pull` failure in multi-machine setup

Hi, Lars-Dominik Braun skribis: > I’m using guix on a multi-machine setup with a single remote guix-daemon that > can be reached via SSH. Thus GUIX_DAEMON_SOCKET=ssh://master. on the > compute nodes. Running `guix pull` on master works fine (the variable is not > set here), but it does not on a

bug#39936: How To Resolve "LC_ALL: cannot change locale (en_US.utf8)"

System: Ubuntu 18.04 Guix: 1.0.1 Whenever I "guix pull" I see the error "LC_ALL: cannot change locale (en_US.utf8)". I installed "glibc_utf8_locales" and it seems to have had no effect. In my .profile I am pointing to "/home/username/.guix-profile/lib/locale". Am I missing something? I have e

bug#39937: Cuirass evaluations of master branch are failing

Guix, The CI is currently unable to evaluate the 'guix-master' specification: https://ci.guix.gnu.org/jobset/guix-master Excerpt from the log file: @ build-succeeded /gnu/store/lg55vig7qp8qwrx4hlsq8mnq8h6vkik0-profile.drv - Backtrace: 7 (apply-smob/1 #) In ice-9/boot-9.scm: 705:2

bug#39939: python-tables tunes itself to the CPU at build time

python-tables is not reproducible. It tries to figure out what the CPU of the build node supports and then adjusts the build. This leads to crashes on CPUs that have fewer features. -- Ricardo

bug#36882: Qemu 4.2.0 build for x86_64-linux fails

Hey, > clang-runtime requires a similar fix for CPLUS_INCLUDE_PATH. No idea > what's up with GHC@8.4 yet, but unsurprisingly removing libc from the > include paths does not make a difference. Closing this one, thanks for pushing! Mathieu

bug#39941: Disk-image size increase on core-updates.

Hello, When building the attached operating-system (very close to bare-bones.tmpl) with the following command: guix system disk-image --target=aarch64-linux-gnu mini.scm --no-grafts the produced disk-image weights 2.6G (2717242368 bytes). On the same branch in January it was around 1.5G. I'll

bug#39925: `guix pull` failure in multi-machine setup

Hi Ludo, > This is a limitation in ‘build-aux/build-self.scm’: […] I don’t understand what’s going on there unfortunately. Is there a high-level explanation somewhere in the manual? > We could work around it by letting the ‘GUIX_DAEMON_SOCKET’ environment > variable through, along these lines: No