bug#48591: ugrep: illegal instruction

2021-07-01 Thread Leo Famulari
On Wed, Jun 30, 2021 at 11:41:11PM +0200, raingloom wrote: > TIL about that. There really ought to be a more obvious way to do that. Agreed! It's a common use case.

bug#49088: grub-hybrid fails to build on aarch64-linux: error: --enable-stack-protector is not supported

2021-07-01 Thread Tobias Geerinckx-Rice via Bug reports for GNU Guix
Chris, Thanks for catching, fixing, and committing this! I managed to miss your original CC. I need to configure mu4e to make ‘personal’ mail stand out from the din somehow… Kind regards, T G-R signature.asc Description: PGP signature

bug#49088: grub-hybrid fails to build on aarch64-linux: error: --enable-stack-protector is not supported

2021-07-01 Thread Christopher Baines
Christopher Baines writes: > This is the relevant derivation [1], this change was probably introduced > here [2]. > > 1: /gnu/store/vmpn3xk6mzns9zvq7dvlpj67ld3fv48p-grub-hybrid-2.06.drv > 2: > https://git.savannah.gnu.org/cgit/guix.git/commit/?id=018f95094153660e3041ec160718f0bda286a3dc > > >

bug#49089: --fallback doesn't do anything when 'connect*' fails

2021-07-01 Thread Maxime Devos
Mathieu Othacehe schreef op vr 18-06-2021 om 17:36 [+0200]: > Hello Maxime, > > > guix substitute: warning: [...].local: host not found: Naam of dienst is > > niet bekend > > guix substitute: warning: tijdens het binnenhalen van > >

bug#49320: guix import hackage does not support build-tools and build-tool-depends stanzas

2021-07-01 Thread Philip Munksgaard
The two stanzas build-tools[0] and build-tool-depends[1] are not supported by the cabal importer[2], which means that the generated build files for a package such as language-c-quote[3] doesn't work. For instance, the attached language-c-quote.scm was generated by amending the result of

bug#49307: clisp: build failure: failing tests

2021-07-01 Thread Christopher Howard
Hi, yes, I am able to reproduce the error, even when I switch to your guix commit (using time-machine).

bug#48944: haskell build-system cannot build pcg-random

2021-07-01 Thread Philip Munksgaard
Hi John Kehayias, The patch seems to work! What will it take for us to get it merged? Best, Philip

bug#48701: Closed by 48943

2021-07-01 Thread Philip Munksgaard
This issue has been fixed by #48943 and should be closed.

bug#48903: guix substitute: error: TLS error in procedure 'read_from_session_record_port': Error decoding the received TLS packet.

2021-07-01 Thread Ludovic Courtès
Hi, Maxim Cournoyer skribis: > I've tried with the following modified version which runs multiple > threads in parallel (to mimic --max-jobs=4 on the daemon), and I've yet > to trigger it, although the hard drive is grinding heavily: Note that ‘--max-jobs=4’ leads guix-daemon to spawn 4 ‘guix

bug#48064: texlive-* packages fail to build non-deterministically

2021-07-01 Thread Ludovic Courtès
Thiago Jung Bauermann skribis: > Em quarta-feira, 30 de junho de 2021, às 09:46:01 -03, Thiago Jung > Bauermann escreveu: >> I will use your command line to get a Valgrind report for TeX Live 2021 >> and post it to the dev-luatex mailing list as well. > > Unfortunately I’m still having problems

bug#48756: guix offload: error: corrupt input while restoring archive from #

2021-07-01 Thread Ludovic Courtès
Hi, (+Cc: 48...@debbugs.gnu.org, so we record the end of the story.) Madhavan Krishnan skribis: > 89747 pipe([8, 10]) = 0 > 89748 > execve("/gnu/store/6rn4l3h0p9x0m615pp1ynlv9v0743kl3-guix-1.2.0/bin/guix", >

bug#49307: clisp: build failure: failing tests

2021-07-01 Thread Guillaume Le Vaillant
Christopher Howard skribis: > Attempting to build clisp from source results in these test failures: > ```(echo *.erg | grep '*' >/dev/null) || (echo "Test failed:" ; ls -l > *erg; echo "To see which tests failed, type" ; echo "cat > "`pwd`"/*.erg" ; exit 1)Test failed:-rw-r--r-- 1 nixbld

bug#49304: Acknowledgement (`make check-system` fails to run on master)

2021-07-01 Thread Mathieu Othacehe
Hello, > After some more discussion with Tobias on IRC, it seems that this was caused > by a `git pull` followed by a `make` and lacked a `make clean-go`. After > running > `make clean-go` and rebuilding, the problem went away. I can confirm this was caused by an API mismatch in