bug#54864: GNU Cuirass reports arm64 as armhf

2022-04-27 Thread Ludovic Courtès
Hi, Mathieu Othacehe skribis: >> I've had this experience before, it's very confusing (it goes on trying >> to build a toolchain for something that is sure to fail). Perhaps we >> could at least have a place to refer to in the manual for the common GNU >> triplets which make the most sense in f

bug#54864: GNU Cuirass reports arm64 as armhf

2022-04-27 Thread Ludovic Courtès
Hi Maxim, Maxim Cournoyer skribis: > [...] > >> I see, yeah, I eventually figured out that aarch64 was what I was >> supposed to be using (I think I was reading >> https://wiki.debian.org/Multiarch/Tuples when I realized this). >> >> However, what confuses me still was that 'arm64-linux' did wor

bug#55139: package-location is wrong for transformed packages

2022-04-27 Thread Liliana Marie Prikler
Am Dienstag, dem 26.04.2022 um 21:48 -0400 schrieb Maxim Cournoyer: > Hi Guix! > > --8<---cut here---start->8--- > > ,import (gnu packages) (guix packages) > > (car (find-packages-by-name "python2-pyalsaaudio")) > $1 = # 7f2b76fab160> > > (package-definition-loc

bug#55116: gnome-disks can't restore from image

2022-04-27 Thread Maxime Devos
raingloom schreef op wo 27-04-2022 om 01:32 [+0200]: >  you try `guix shell glib gnome-disk-utility` > > instead? > > > > Best, > > That does work. Not great UX. Can we either make it obvious that glib > needs to be in the environment, or just remove the need to explicitly > include it? > > So

bug#55013: Guix-emacs doesn't work

2022-04-27 Thread Giovanni Biscuolo
Hi Ryan, Giovanni Biscuolo writes: [...] > The most similar upstream bug is this one: > https://gitlab.com/emacs-guix/emacs-guix/-/issues/23 > > In that thread Adam Porter points to this comment that explains how to > start Guix REPL instead of Guile REPL, from emacs-guix: > https://gitlab.com/

bug#55013: Guix-emacs doesn't work

2022-04-27 Thread Giovanni Biscuolo
Hi Jan, sorry for this late reply, Jan Nieuwenhuizen writes: [...] > I'm on Guix System and emacs-guix's command line completion hasn't > worked for me for about a year. it does not work for me too, but with a very different behaviour: [...] >> Evaluating the above code /before/ starting an