bug#37501: [core-updates] Entropy starvation during boot

2019-10-02 Thread Ludovic Courtès
Hi again, Marius Bakke skribis: > After reconfiguring on the 'core-updates' branch, systems using the > OpenSSH service will occasionally (not always!) hang forever during > boot, waiting for entropy. Moving the mouse or mashing the keyboard > allows the boot to proceed. > > I don't think this

bug#37593: [core-updates] Linux-Libre fails to build on aarch64-linux

2019-10-02 Thread Pierre Langlois
Hi Marius, Marius Bakke writes: > Berlin fails to build "linux-libre" for AArch64 on the 'core-updates' > branch. Here is a recent attempt: > > https://ci.guix.gnu.org/build/1758844/details > > Log file for the latest build: > > https://ci.guix.gnu.org/log/aq2rnrmjsgnyk8vmsm7aa3mgdj39dcwh-linux-

bug#37593: [core-updates] Linux-Libre fails to build on aarch64-linux

2019-10-02 Thread Marius Bakke
Berlin fails to build "linux-libre" for AArch64 on the 'core-updates' branch. Here is a recent attempt: https://ci.guix.gnu.org/build/1758844/details Log file for the latest build: https://ci.guix.gnu.org/log/aq2rnrmjsgnyk8vmsm7aa3mgdj39dcwh-linux-libre-5.2.17.drv This seems to be the salient

bug#37588: Installation error 'emacs-matrix-client'

2019-10-02 Thread SuarezMiguelC via Bug reports for GNU Guix
I'm unable to install emacs-matrix-client, the error is: guix install: error: el perfil contiene entradas en conflicto para emacs-f guix install: error: primera entrada: emacs-f@0.20.0 /gnu/store/7fkbx880319n416nwmdk4mvxn6vlb4xc-emacs-f-0.20.0 guix install: error:... propagada desde emacs-m

bug#37586: Import cycles in unrelated packages should not be an error

2019-10-02 Thread pelzflorian (Florian Pelz)
I am annoyed by another import cycle similar to in an unfinished package I’m writing. They needlessly complicate packaging and make packagers split modules that logically should not be split. Is it possible to make import cycles not an error in Guix packages

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

2019-10-02 Thread Vagrant Cascadian
On 2019-10-02, Ludovic Courtès wrote: > Vagrant Cascadian skribis: > >> Ok, a little further ... >> >> guix environment --ad-hoc epiphany > > It works for me on ‘core-updates’ > ece22ac8ccb6744eaec0320f0c7c9b6680fffa46, but note that my system and > user profile were already on ‘core-updates’, s

bug#37583: Documentation needed: pam-services in operating-system structure

2019-10-02 Thread Jesse Gibbons
The manual has no documentation about how to use pam-services in the operating-system configuration. Information about how to use the pam-service data structure and an example of how to use it would be helpful to administrators who need to use non-default settings, and will help us squash the bugs

bug#37501: [core-updates] Entropy starvation during boot

2019-10-02 Thread Ludovic Courtès
Hello! Marius Bakke skribis: > After reconfiguring on the 'core-updates' branch, systems using the > OpenSSH service will occasionally (not always!) hang forever during > boot, waiting for entropy. Moving the mouse or mashing the keyboard > allows the boot to proceed. > > I don't think this is

bug#37503: dconf-editor build fails on core-updates

2019-10-02 Thread Ludovic Courtès
Hi Jack, Jack Hill skribis: > ../dconf-editor-3.30.2/editor/setting-object.vala > ../dconf-editor-3.30.2/editor/source-manager.vala > error: Only a stable version of GLib can be targeted, use MAJOR.MINOR format > with MINOR as an even number > Compilation failed: 1 error(s), 0 warning(s) > [5/2

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

2019-10-02 Thread Ludovic Courtès
Hi Vagrant! Vagrant Cascadian skribis: > Ok, a little further ... > > guix environment --ad-hoc epiphany It works for me on ‘core-updates’ ece22ac8ccb6744eaec0320f0c7c9b6680fffa46, but note that my system and user profile were already on ‘core-updates’, so presumably that avoids problems with

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

2019-10-02 Thread Ludovic Courtès
Hi, Ludovic Courtès skribis: >> Oh I see. This is fixed by cherry-picking >> 96783ed6275cd2818ff56916274e6e4582f1dc9b from ‘core-updates’ into >> ‘master’. Will push shortly. > > On second thought, that doesn’t solve the problem for revisions on the > current ‘master’ branch between and > 456c