bug#37929: clojure is not usable out of the box

2019-10-26 Thread Bradley Haggerty
Sorry about that! I forgot to search the issues before making one.





bug#37850: Glib documentation is missing

2019-10-26 Thread Pierre Neidhardt
Ludovic Courtès  writes:

> Alternately, we could define a new “glib-doc” package that would depend
> on the current “glib” package, assuming the build system allows us to
> build nothing but documentation.

Some possible drawbacks:

- It's not consistent with the other Glib/GNOME libraries like gtk+ or
  webkitgtk which have a "doc" output.

- Previously we had glib:doc and no measure can be taken to let the user
  know that it's now "glib-doc".

So I would got for the glib-minimal route.

This bring me to another problem: "glib:doc" was not deprecated, so
users who installed "glib:doc" cannot update their manifests / profiles
after a guix pull.

Can we actually deprecate single outputs?
If not, isn't it a bug?

-- 
Pierre Neidhardt
https://ambrevar.xyz/


signature.asc
Description: PGP signature


bug#37933: gst* plugins in non-default profile not found by webkitgtk browsers (e.g. epiphany)

2019-10-26 Thread Pierre Neidhardt
Recipe that fails:

--8<---cut here---start->8---
guix remove gst-libav gst-plugins-bad gst-plugins-base gst-plugins-good 
gst-plugins-ugly
guix package -p foo -i gst-libav gst-plugins-bad gst-plugins-base 
gst-plugins-good gst-plugins-ugly epiphany
foo/bin/epiphany https://archive.org/details/guix-videos 
--8<---cut here---end--->8---

Recipe that works

--8<---cut here---start->8---
guix package -i gst-libav gst-plugins-bad gst-plugins-base gst-plugins-good 
gst-plugins-ugly epiphany
foo/bin/epiphany https://archive.org/details/guix-videos 
--8<---cut here---end--->8---

-- 
Pierre Neidhardt
https://ambrevar.xyz/


signature.asc
Description: PGP signature


bug#37935: Erro no upgrade pt-br portuguese

2019-10-26 Thread Pablo Ferreira
Instalei o Guix mas não consigo fazer o upgrade do sistema. Ele falhou por
algum motivo após o download de um pacote. "/gnu/store/...nss-... failed...
try --fallback".

Usei o:

guix pull

então

sudo guix system reconfigure /etc/config.scm


bug#37799: dbus-system

2019-10-26 Thread Gnu Röoty
Manuellement avec la commande udisksctl ça marche mais j'aimerai bien que
les disques montes automatiquement à l'insertion.
Comment dois-j faire ?

Le ven. 25 oct. 2019 à 20:34, Ludovic Courtès  a écrit :

> Bonjour,
>
> Gnu Röoty  skribis:
>
> > Je savais que si j'enlever le udisk-service ça fonctionner mais le
> problème
> > et qu'il est impossible de monter un disque amovible sur xfce4 et je vais
> > pas installer GNOME juste pour obtenir gvfs afin de monter les disques
> > amovibles.
>
> Et donc tu as rajouté « udisks-service » pour pouvoir monter un disque
> amovible ?  Tu le montes avec la commande « udisksctl » ?
>
> Merci,
> Ludo’.
>


bug#37937: Lollypop missing propagated-input gsettings-desktop-schemas

2019-10-26 Thread Sam

Hello,
lollypop is missing gsettings-desktop-schemas as dependency, and fails 
to start without the package.
Below there is a patch where I tried to fix it, but since I couldn't 
find out how to test the effect I chose to not send it to the patch 
mailing list.

I'm sorry for the inconvenience.

diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 8bb891bfb3..a6596bc92d 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -7833,8 +7833,9 @@ views can be printed as PDF or PostScript files, 
or exported to HTML.")

("totem-pl-parser" ,totem-pl-parser)
("webkitgtk" ,webkitgtk)))
 (propagated-inputs
- `(;; gst-plugins-base is required to start Lollypop,
+ `(;; gst-plugins-base and gsettings-desktop-schemas are required 
to start Lollypop,

;; the others are required to play streaming.
+   ("gsettings-desktop-schemas" ,gsettings-desktop-schemas)
("gst-plugins-good" ,gst-plugins-good)
("gst-plugins-ugly" ,gst-plugins-ugly)))
 (home-page "https://wiki.gnome.org/Apps/Lollypop";)






bug#37897: Bug: Resetting locale settings

2019-10-26 Thread o . rojon

Hello Ludo,

maybe I have been a bit unprecise in my wording, Im rather new to that 
level of configurability.


So I was talking about the keyboard layout all along. Not only was my 
locale set to "de_DE.utf8", but my keyboard configuration is set to 
"de-latin1-nodeadkeys". Interestingly, the keyboard layout is different 
in xorg and xfce than it is in the console (the one I reach via C-M-Fx, 
not the terminal emulator). In the console, I have the qwertz keyboard 
layout.


Also find the part of my current configuration file (sitting at 
/etc/config.scm) which specifies both locale and keyboard layout:

(operating-system
  (locale "de_DE.utf8")
  (timezone "Europe/Berlin")
  (keyboard-layout (keyboard-layout "de" "latin1-nodeadkeys"))
  (bootloader
(bootloader-configuration
  (bootloader grub-bootloader)
  (target "/dev/sdb")
  (keyboard-layout keyboard-layout)))

I was surprised by the behaviour described in my bug report because I 
saw that the value for "keyboard-layout", which is set very early in the 
operating-system declaration, is simply copied over in later parts of 
the configuration file.


If you need anything else, please specify. Again, Im rather new to these 
things, so sorry for technical inspecificity.


Greetings!

On 25.10.2019 22:44, Ludovic Courtès wrote:

Hello,

o.ro...@posteo.net skribis:


I believe that a locale-related bug has slipped in somewhere in the
last two-three weeks. During installation and in my configuration
file, I have specified de_DE specified as locale, which should
translate to a german keyboard layout. But since said two-three weeks,
I startup with what I believe is the US layout (qwerty) - and before
this occurred, I was once even unable to login because my keyboard
layout has been changed to something so obscure it didnt even seem to
know basic characters like the exclamation mark, while there was a
number of characters that could not be displayed (probably non-utf
characters I suppose).


Could you be more specific about the context in which you get an
incorrect layout (console, Xorg, Wayland, GNOME, etc.)?

Note that locale settings and keyboard layout settings are entirely
separate—choosing the “de_DE” locale gives you programs that speak
German, but it does not give you a “qwertz” layout.  See:

  https://guix.gnu.org/manual/devel/en/html_node/Keyboard-Layout.html
  https://guix.gnu.org/manual/devel/en/html_node/Locales.html

HTH,
Ludo’.






bug#37937: Lollypop missing propagated-input gsettings-desktop-schemas

2019-10-26 Thread Tobias Geerinckx-Rice via Bug reports for GNU Guix

Sam,

Sam 写道:
lollypop is missing gsettings-desktop-schemas as dependency, and 
fails

to start without the package.


Thanks for reporting this, and for trying to fix it.  I took a 
different approach in commit 
8ac8b3b3601560c4a455543435276a8cdf61b54e: propagation is, at 
heart, a kluge, and one that should be avoided whenever 
possible[0].


I'm closing this bug because it now works for me.

Could you pull, upgrade lollypop, and let me know whether it now 
works for you?



I couldn't find out how to test the effect


Assuming you already have a Guix git checkout to create the patch, 
you simply:


 $ guix environment guix
 $ ./configure --localstatedir=/var
 $ make -j `nproc`
 $ ./pre-inst-env guix lollypop

…or something like that :-)

Kind regards,

T G-R

[0]: https://issues.guix.info/issue/36896


signature.asc
Description: PGP signature


bug#37851: Grub installation only checks for encrypted /boot folder

2019-10-26 Thread Miguel Arruga Vivas
Hi Ludo’,

El Tue, 22 Oct 2019 16:12:49 +0200
Ludovic Courtès  escribió:
> Hola Miguel,
> 
> Miguel Arruga Vivas  skribis:
> > (...)
> > +cryptomount -a  
> 
> Does that cause GRUB to mount all the LUKS partitions it was aware of
> at installation time, or does it cause it to scan all the partitions
> in search of a LUKS signature?

That patch is the first one, it mounts everything it can find, unlike
this one.

The only option I've seen was to modify boot-parameters (as in #35394,
wink wink nudge nudge) in order to store the needed partitions.  I've
reduced it this time to one patch, is it somehow easier to read this
way?  I could split it in two stages (one add the boot-parameters
field, the other one to make use of it) or squash the three for the
other feature into one if that easier for the review.  The main issues
I've found is that the source of the device-mappings needed for boot up
has to be declared by the UUID to ensure they are not system
dependent.  Also, the warning is shown several times and the message
isn't quite good, any idea how to fix/improve this?

Happy hacking!
Miguel
From f6438d1175a1d60d842ab502255a7685b05f4e7d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Miguel=20=C3=81ngel=20Arruga=20Vivas?=
 
Date: Sun, 27 Oct 2019 01:35:59 +0200
Subject: [PATCH] system: Use of mapped-devices for boot process.

* gnu/bootloader/depthcharge.scm (depthcharge-configuration-file): New
parameter crypto-devices, not used.
* gnu/bootloader/extlinux.scm (extlinux-configuration-file): Likewise.
* gnu/bootloader/grub.scm (grub-configuration-file)[declaration]: New
parameter crypto-devices, used to ensure unlock every encrypted
partition needed by the bootloader.
[device-uuid->gexp]: New function, emits cryptomount calls.
[body]: Map crypto-devices with device-uuid->gexp.
* gnu/machine/ssh.scm (roll-back-managed-host): Use the crypto-devices
stored from the selected generation in the call to the bootloader
configuration generator.
* gnu/scripts/system.scm (reinstall-bootloader): Likewise.
* gnu/system.scm (define-module)[export]: Export new accessor
boot-parameters-crypto-devices.
(boot-parameters)[crypto-devices]: New field.
(read-boot-parameters)[uuid-sexp->uuid]: New function.
(read-boot-parameters)[body]: Read new field crypto-devices.
(operating-system-boot-parameters-file): Add the new field.
(operating-system-boot-crypto-devices): New function.  Warn about
devices without an UUID.  They are ignored as they would be dependant
on the hardware configuration.
(operating-system-bootcfg): Use operating-system-boot-crypto-devices in
the call to the bootloader configuration generator.
(operating-system-boot-parameters): Use
operating-system-boot-crypto-devices to store the needed devices.
---
 gnu/bootloader/depthcharge.scm |  1 +
 gnu/bootloader/extlinux.scm|  1 +
 gnu/bootloader/grub.scm| 14 
 gnu/machine/ssh.scm|  3 +++
 gnu/system.scm | 40 ++
 guix/scripts/system.scm|  2 ++
 6 files changed, 61 insertions(+)

diff --git a/gnu/bootloader/depthcharge.scm b/gnu/bootloader/depthcharge.scm
index 58cc3f3932..fe4302e93c 100644
--- a/gnu/bootloader/depthcharge.scm
+++ b/gnu/bootloader/depthcharge.scm
@@ -82,6 +82,7 @@
 (define* (depthcharge-configuration-file config entries
  #:key
  (system (%current-system))
+ (crypto-devices '())
  (old-entries '()))
   (match entries
 ((entry)
diff --git a/gnu/bootloader/extlinux.scm b/gnu/bootloader/extlinux.scm
index 40108584a8..3defeab3dd 100644
--- a/gnu/bootloader/extlinux.scm
+++ b/gnu/bootloader/extlinux.scm
@@ -28,6 +28,7 @@
 (define* (extlinux-configuration-file config entries
   #:key
   (system (%current-system))
+  (crypto-devices '())
   (old-entries '()))
   "Return the U-Boot configuration file corresponding to CONFIG, a
  object, and where the store is available at STORE-FS, a
diff --git a/gnu/bootloader/grub.scm b/gnu/bootloader/grub.scm
index d984d5f5e3..8b5cf848af 100644
--- a/gnu/bootloader/grub.scm
+++ b/gnu/bootloader/grub.scm
@@ -3,6 +3,7 @@
 ;;; Copyright © 2016 Chris Marusich 
 ;;; Copyright © 2017 Leo Famulari 
 ;;; Copyright © 2017 Mathieu Othacehe 
+;;; Copyright © 2019 Miguel Ángel Arruga Vivas 
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -316,6 +317,7 @@ code."
 (define* (grub-configuration-file config entries
   #:key
   (system (%current-system))
+  (crypto-devices '())
   (old-entries '()))
   "Return the GRUB configuration file corresponding to CONFIG, a
  object, and where the store is available at
@@ -345,6 +347,17