Hi,
yann writes:
> Then I tried to run it by putting myself in the directory and running:
>
> guix shell -f gnome-shell-extension-desktop-icon-ng.scm
Looks like your file gnome-shell-extension-desktop-icon-ng.scm does not
return a package object. You have to add
‘gnome-shell-extension-desktop-
Hi Guix,
My `dockerd` service has stopped working weeks (months!?) ago, but I've
had no use for it in the meantime, so it was no big deal, until today…
My configuration looks like this:
```scm
;…
(use-service-modules desktop docker)
(operating-system
;…
(services
(append
(list
At the moment, when I run: icedove -ProfileManager
it gives me 8 options:
1. Default Default runs the new icedove
2. Default asks me to set up icedove
3. Default 1runs the new icedove
4. Default 2runs the new icedove
5. Default 3
signature.asc
Description: PGP signature
Hi!
Tanguy LE CARROUR writes:
> Hi Guix,
>
> My `dockerd` service has stopped working weeks (months!?) ago, but I've
> had no use for it in the meantime, so it was no big deal, until today…
>
> My configuration looks like this:
>
> ```scm
> ;…
> (use-se
Thanks, Vagrant.
> For changes going into upstream Guix, generally yes. Because guix is
> functional package management, you need to know the hashes of your
> inputs in advance.
>
> The exception might be that some upstream software provides a guix.scm
> to be able to build from the current git c
