bug#38054: mumble: "QSslSocket: cannot resolve ", Certificate Expiry, segfault

2019-11-21 Thread Ivan Vilata i Balaguer
Ivan Vilata i Balaguer (2019-11-20 00:30:24 -0500) wrote: > Thanks Christopher! I'm currently working in a complete patch, it's > building and running (and it's not suffering from the errors I found!), but > I still need to locate the appropriate icons and include them in the > package. > >

bug#38273: emacs doesn't open files

2019-11-21 Thread Maxim Cournoyer
Hello Zimoun, zimoun writes: > Hi Maxim, > > Thank you to looking. > > On Tue, 19 Nov 2019 at 22:51, Maxim Cournoyer > wrote: > >> Did you sort out your issue? Perhaps logging out then back in could >> define the missing EMACSLOADPATH environment variable? Or manually >> sourcing your

bug#38313: Hexchat Python failure on exit

2019-11-21 Thread Julien Lepiller
Thanks, fixed in 8da527d5bc1a1c6c5718236d1870fe907f80dfc6 thanks for reporting! Le Thu, 21 Nov 2019 16:40:38 +, Francesco Magliocca a écrit : > When I want to quit hexchat, it doesn't end grecefully, but something > regarding the Python embedded engine fails. > > This patch should solve

bug#37850: Glib documentation is missing

2019-11-21 Thread Marius Bakke
Pierre Neidhardt writes: > Oh, that makes total sense, thanks for the explanation Marius! > > Alright, final patch attached. > Let me know if I should merge on master. Looks good! > From 29d27b64fb7bbf96a2ed59a3e1c4179717770f5c Mon Sep 17 00:00:00 2001 > From: Pierre Neidhardt > Date: Mon, 11

bug#38313: Hexchat Python failure on exit

2019-11-21 Thread Francesco Magliocca
When I want to quit hexchat, it doesn't end grecefully, but something regarding the Python embedded engine fails. This patch should solve the issue: https://src.fedoraproject.org/rpms/hexchat/blob/master/f/0001-Python-plugin-Call-EndInterpreter-when-deinit-ing-th.patch

bug#29593: Bug #29593 Hunting: Broken links in the HTML manual

2019-11-21 Thread zimoun
Hi Tobias, My quick tests were really quick! ;-) These links remains broken. Do you have any patch fixing them that you forgot to push? Or do I invest more time to propose a patch? Thank you in advance. Cheers, simon Same with the online "manual/devel". - Package Management[1]: “The

bug#34526: Updating node.js

2019-11-21 Thread Jelle Licht
Christopher Lemmer Webber writes: > That's fair. > > I have a personal project that requires that I use a newer version of > Node (at least version 11). So if anyone has a recipe on how to get > Node running, even the wrong way per Guix standards, maybe useful to > post to this bug in the

bug#38295: manual-config php-fpm mismatch

2019-11-21 Thread Efraim Flashner
On Thu, Nov 21, 2019 at 12:11:51PM +0200, Efraim Flashner wrote: > On Wed, Nov 20, 2019 at 04:43:27PM +0100, Tobias Geerinckx-Rice via Bug > reports for GNU Guix wrote: > > Efraim, > > > > Efraim Flashner 写道: > > > In (gnu services web) for it says that default > > > for 'socket-group' is

bug#38295: manual-config php-fpm mismatch

2019-11-21 Thread Efraim Flashner
On Wed, Nov 20, 2019 at 04:43:27PM +0100, Tobias Geerinckx-Rice via Bug reports for GNU Guix wrote: > Efraim, > > Efraim Flashner 写道: > > In (gnu services web) for it says that default > > for 'socket-group' is "nginx". In the manual, in 8.8.16 (Web Services), > > it says the socket-group