bug#36551: [META] Run Guix System on Purism Librem 5

Further "audio" packages: - wys, daemon for PulseAudio loopbacks for phone calls: https://source.puri.sm/Librem5/wys - haegtesse, daemon for audio between modem and PulseAudio. Seems to only be used on the developer board: https://source.puri.sm/Librem5/haegtesse - sound-theme-librem5:

bug#30961: Byte compilation problem with emacs-org

Hi Maxim, > Does this still occur on latest master? No, the bug disappeared with the update to Emacs 26.3, which comes with org-mode 9. So this bug report can be closed (which I'd have done already if I knew how to do it). Cheers, Konrad

bug#38544: gparted segfaults

This segfaults: sudo /gnu/store/yzxyxnxja4y1riwh3mrqrvb7h4vhxlqb-gparted-1.0.0/bin/gparted --8<---cut here---start->8--- … (gpartedbin:5364): Gdk-CRITICAL **: 11:06:10.219: gdk_cairo_surface_create_from_pixbuf: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

bug#38533: emacs-auctex breaks url package

Hi Maxim, Maxim Cournoyer writes: > Hello Diego, > > Diego Nicola Barbato writes: > >> Hi Guix, >> >> AUCTeX breaks Emacs' bult-in url package. This bug appears to have been >> introduced with commit 3ffdd00 and can be reproduced as follows: >> >> 1) Install ‘emacs’ and ‘emacs-auctex’. >> 2)

bug#35621: Simplify comparing guix challenge results

Hello! Vagrant Cascadian skribis: > I'd like to see a simpler process for comparing challenge results > producing differences. > > While the manual documents how to compare a failing challenge result > > $ wget -q -O - https://ci.guix.info/nar/…-git-2.5.0 \ > | guix archive -x /tmp/git >

bug#37757: Kernel panic upon shutdown

Hello, [+Cc: Andy for a heads-up on the fix below.] Ludovic Courtès skribis: > It turns out the previous patch didn’t work; in short, we really have to > use async-signal-safe functions only from the signal handler, so this > has to be done in C. > > The attached patch does that. I’ve tried

bug#38529: Make --pure the default for `guix environment'?

On Sun, 2019-12-08 at 16:42 +0100, Pierre Neidhardt wrote: > --pure seems to be the more sensible behaviour. "Impure" environments > can have unexpected behaviours, so it makes sense to only allow them > when the user explicitly asks for it. > --pure environments sometimes miss important

bug#38320: Cuirass: Allow to use authenticated Git repositories as inputs

Hello, Here's a patch that add support for ssh authenticated repositories in "clone" and "remote-fetch" methods of Guile-Git. At first, I used Guile-SSH in the tests to start an SSH server, but as "make-server" call of Guile-SSH is really low level, this is not very realistic. I just ended up

bug#38529: Make --pure the default for `guix environment'?

"Thompson, David" writes: > Hi, > > I have long thought that --ad-hoc should be implied, as that is the > mode I use 99% of the time, but I disagree that --pure should be the > default. Most of the time I (and I suspect most other users) just want > to temporarily augment the current environment

bug#38500: Ruby is built against libruby-static.a

I have submitted a patch that will go into core-updates, with bug report #38552. That patch will close both of these bug reports. Thanks. -- Brett M. Gilio https://git.sr.ht/~brettgilio/

bug#38500: Ruby is built against libruby-static.a

Tobias Geerinckx-Rice writes: > You could ask Pjotr Prins and David Thompson but I suspect that it was > simply an oversight: most packages link dynamically by default because > it's the sane thing to do, and it would have been reasonable to assume > Ruby did too. Tobias, I did some

bug#38529: Make --pure the default for `guix environment'?

Hi, I have long thought that --ad-hoc should be implied, as that is the mode I use 99% of the time, but I disagree that --pure should be the default. Most of the time I (and I suspect most other users) just want to temporarily augment the current environment with a package or two and I think that

bug#37757: Kernel panic upon shutdown

Hi, Ludovic Courtès skribis: > My plan is to: > > 1. push the patch below to the ‘stable-2.2’ branch of Guile; > done: > > ; > > 2. use a patched Guile for the ‘shepherd’

bug#38464: python-hy REPL is unusable

On Mon, 2019-12-02 at 17:16 -0700, Jesse Gibbons wrote: > 1. install python-hy > 2. run hy3 (to make sure it's setup to use python 3.7.4) > 3. press with or without typing anything. > It prints the following error at the end of a long stack trace: > > ImportError: invalid flags 1495674643 in

bug#38555: shepherd not working out of the box in Debian

I run shepherd 0.6.1 (with guile 2.2.4) as the init system for Debian buster. It's an installation in the standard place /usr/local. When /usr/local/var/run/shepherd/socket is left dangling due to a crash, shepherd won't start on the next reboot, as error SOCADDRINUSE is raised. Obviously this

bug#38544: gparted segfaults

Hello, Ricardo Wurmus ezt írta (időpont: 2019. dec. 9., H, 11:11): > > This segfaults: > > sudo /gnu/store/yzxyxnxja4y1riwh3mrqrvb7h4vhxlqb-gparted-1.0.0/bin/gparted > > --8<---cut here---start->8--- > … > (gpartedbin:5364): Gdk-CRITICAL **: 11:06:10.219: