bug#37520: maxima x86_64/linux build failure

2019-09-28 Thread Christopher Howard
Thank you. It is now building fine for me. On Fri, 2019-09-27 at 00:03 +0200, Diego Nicola Barbato wrote: > Hey Christopher, > > Christopher Howard writes: > > > Running guix overlaid on Debian 9 amd64. Ran guix pull && guix > > package -u. Ran guix install wxmaxima. Build fails with > > > > /

bug#36785: Impossible to pull on foreign distro

2019-09-28 Thread Maxim Cournoyer
Hello Ludovic! Ludovic Courtès writes: > Hi Maxim! > > Maxim Cournoyer skribis: > >> From a289eb3fd6239287d4a802fbba69abf21604591f Mon Sep 17 00:00:00 2001 >> From: Maxim Cournoyer >> Date: Sat, 28 Sep 2019 00:11:28 +0900 >> Subject: [PATCH] doc: Add a 'Upgrading Guix' section to the

bug#37545: epiphany and next broken after webkitgtk upgrade to 2.26.1

2019-09-28 Thread Vagrant Cascadian
Both next and epiphany are very broken for me after the upgrade to webkitgtk to 2.26.1. I first noticed when running core-updates, but then also tested on master (de3896fb79984d545e7fec0b5e4f1ba37983fbce) with the same result. $ guix describe Generation 240 Sep 27 2019 20:47:30(current)

bug#37506: [core-updates] Inferiors cannot reference master branch

2019-09-28 Thread Ludovic Courtès
Hi Marius! Marius Bakke skribis: > Here is a manifest that reproduces this failure: > > (use-modules (guix channels) > (guix inferior) > (srfi srfi-1)) > > (define channels > (list (channel > (name 'guix) > (url

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread Ludovic Courtès
Hi Danny! Danny Milosavljevic skribis: > So we could have a one-shot service "term-auto" which checks /proc/cmdline > (which can't change until the next reboot anyway), and if there's a serial > console, register a new (normal) service "term-ttyACM0" or whatever. > Otherwise > it would just

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread Ludovic Courtès
Danny Milosavljevic skribis: > On second thought, maybe it would be easiest to make term-auto "succeed" when > it can't find that serial console. Shepherd would think everything is a-ok > and > nobody would tell it any better :P Well, that’s true! :-) Ludo’.

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread Danny Milosavljevic
On second thought, maybe it would be easiest to make term-auto "succeed" when it can't find that serial console. Shepherd would think everything is a-ok and nobody would tell it any better :P pgpX_bhuaNlLm.pgp Description: OpenPGP digital signature

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread Danny Milosavljevic
Hi everyone, On Sat, 28 Sep 2019 19:44:16 +0200 Ludovic Courtès wrote: > ‘term-auto’ is actually something that doesn’t start; it’s confusing, we > should present it differently, maybe as a one-shot service. term-auto automatically provides a shell on the console if that is a serial console.

bug#36785: Impossible to pull on foreign distro

2019-09-28 Thread Ludovic Courtès
Hi Maxim! Maxim Cournoyer skribis: > From a289eb3fd6239287d4a802fbba69abf21604591f Mon Sep 17 00:00:00 2001 > From: Maxim Cournoyer > Date: Sat, 28 Sep 2019 00:11:28 +0900 > Subject: [PATCH] doc: Add a 'Upgrading Guix' section to the 'Installation' > chapter. > MIME-Version: 1.0 >

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread Ludovic Courtès
Hi, "pelzflorian (Florian Pelz)" skribis: > Perhaps /tmp is the wrong directory to store such an early log? No, that’s fine. /tmp is accessible at that point. > I have a Guix virtual machine where ssh-daemon, httpd, php-fpm and > term-auto cannot be started on boot. ‘term-auto’ is

bug#37369: Getting network-manager-openconnect to work

2019-09-28 Thread pelzflorian (Florian Pelz)
On Sat, Sep 28, 2019 at 04:16:40PM +0200, Divan Santana wrote: > So firstly I can't edit the connection as my user, without sudo. Not > sure if I need to be in some group to do that? > P.S. I use (users (cons (user-account (name "florian") (comment "Florian Pelz")

bug#37369: Getting network-manager-openconnect to work

2019-09-28 Thread pelzflorian (Florian Pelz)
For me, before editing the connection, NetworkManager crashed with a segfault and restarted after attempting to connect with a faulty VPN connection. The same may be what happens to you. However, I can add a new connection with gnome-control-center or nm-connection-editor (without using any

bug#37369: Getting network-manager-openconnect to work

2019-09-28 Thread Divan Santana
pelzflorian (Florian Pelz) writes: > Hello! > > There might be a workaround: > > NetworkManager stopped segfaulting for me after I “edited” the > openconnect VPN connection in nm-connection-editor without making any > changes to the connection. Apparently this fixed get_secrets_done_cb > being

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread Ludovic Courtès
"Brant Gardner" skribis: > Okay, I did those steps exactly: > > - clone > - patch -p1 < your-patch > - ./bootstrap > - ./configure --localstatedir=/var > - make check > - sudo -E ./pre-inst-env guix system reconfigure /path/to/myconfig.scm > - reboot > > I had no issues or errors

bug#37369: Getting network-manager-openconnect to work

2019-09-28 Thread Divan Santana
pelzflorian (Florian Pelz) writes: > Hello! > > There might be a workaround: > > NetworkManager stopped segfaulting for me after I “edited” the > openconnect VPN connection in nm-connection-editor without making any > changes to the connection. Apparently this fixed get_secrets_done_cb > being

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread pelzflorian (Florian Pelz)
On Sat, Sep 28, 2019 at 07:38:49AM -0500, Brant Gardner wrote: > Hi Ludo; > > Okay, I did those steps exactly: > > - clone > - patch -p1 < your-patch > - ./bootstrap > - ./configure --localstatedir=/var > - make check > - sudo -E ./pre-inst-env guix system reconfigure

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread Brant Gardner
Hi Ludo; Okay, I did those steps exactly: - clone - patch -p1 < your-patch - ./bootstrap - ./configure --localstatedir=/var - make check - sudo -E ./pre-inst-env guix system reconfigure /path/to/myconfig.scm - reboot I had no issues or errors at any step and on reboot ssh-daemon

bug#37422: Setting keyboard layout with SLiM login manager doesn't work

2019-09-28 Thread Jan Wielkiewicz
On Sat, 28 Sep 2019 09:35:52 +0200 Wiktor elazny wrote: > My wild guess at it would be: > > diff --git a/config.scm b/config.scm > index 83044a1..1c07417 100644 > --- a/config.scm > +++ b/config.scm > @@ -15,8 +15,7 @@ > ;; (xorg-configuration > ;; (keyboard-layout

bug#34580: Service ssh-daemon could not be started

2019-09-28 Thread Ludovic Courtès
Hi Brant, "Brant Gardner" skribis: > Going to show my ignorance here - I've contributed some packages by > making things in a 'guix environment' and then extracting patches, but > what you need me to do is activate a configuration change in a 'live' > guix install (and on a service rather than

bug#37482: Guix fails to build libreoffice

2019-09-28 Thread Ludovic Courtès
Hello, Jan skribis: > On Thu, 26 Sep 2019 22:04:50 +0200 > Ludovic Courtès wrote: > >> There’s no way to skip it. However, there are a couple of tricks: > What about adding an option to only download substitutes for older > devices? That’s not possible in the general case. Also, it would be

bug#37422: Setting keyboard layout with SLiM login manager doesn't work

2019-09-28 Thread Wiktor Żelazny
On Thu, Sep 26, 2019 at 10:46:45PM +0200, Jan Wielkiewicz wrote: > guix system: error: failed to load '/etc/config.scm': > /etc/config.scm:66:57: Wrong type to apply: #< name: > "pl" variant: "legacy" model: #f options: ()> > > Don't really know why this happens. Here's my config.scm: > >