Hi,
Maxim Cournoyer writes:
> Salut,
>
> Gilles writes:
>
>> Deuxième tentative avec une adresse courriel différente...
>
> C'est quoi l'addresse de courrielle différente? Je vois la même
> (cgocable.ca). As-tu envoyé ton message "À:" (To: en anglais)
> bug-guix@gnu.org? Je ne vois toujours
Salut,
Gilles writes:
> Deuxième tentative avec une adresse courriel différente...
C'est quoi l'addresse de courrielle différente? Je vois la même
(cgocable.ca). As-tu envoyé ton message "À:" (To: en anglais)
bug-guix@gnu.org? Je ne vois toujours pas ton bogue apparaître sur
https://guix.gnu
With some exploration, I figured out I can make the popup work again by doing
the following from inside *Guix Internal REPL*:
```
scheme@(emacs-guix)> ,m (guix gexp)
scheme@(guix gexp)> (read-hash-extend #\~ read-gexp)
(read-hash-extend #\$ read-ungexp)
(read-hash-extend #\+ (cut read-ungex
I've recently noticed that `guix challenge guix` fails since guix isn't
reproducible at the moment. As someone pointed out on XMPP, this is due to
parallelism issues with Guile so running `guix build guix --no-grafts --cores=1
--check` reliably produces the same output.
I've sent a simple patch
I've been trying to look into this more, though my knowledge of guile and the
guix scheme code is, frankly, quite limited. However, it seems like what is
happening is that the guile/guix REPL chokes as soon as it come across its
first gexp in guix/scripts/deploy.scm, line 176
>#~(begin
Now
* gnu/packages/base.scm: Similarly to
nix (https://github.com/NixOS/nixpkgs/pull/190211), disable
tests/cp/reflink-auto.sh test as it can fail on btrfs. This was discovered by
the cuirass.genenetwork.org build farm.
Change-Id: If1cc3d516c5807e580ec64ab93670e30090581a7
---
gnu/packages/base.scm |
Hi lovely maintainers of Guix!
Some time ago I announced the availability of a guix build farm running out of
the University of Tennessee[1]. Some time ago, builds started failing due to a
failure to build coreutils[2]; investigation showed a unexpected failing test:
--8<---cut here
Dear Guix,
/run/setuid-programs was replaced by /run/privileged some time ago.
Some of the users on the-dam.org don't have the new location in their
PATH. I've tracked it down to %default-bash-profile still referencing
the old location (in /gnu/system/shadow.scm):
# Prepend setuid programs.
expo
Hello,
skribis:
> Ludovic Courtès writes:
[...]
>> That warning comes from libgc and there’s no such warning when LC_ALL is
>> left unset, which is why it works in that case.
>
> How about
>
>0. Unsetting LC_ALL on the Hurd
>
> would that work?
I’m not sure, but if it does, it’s only “by