Guix's wireguard service is flawed because it will try to start before
DNS is ready, causing it to fail. I tried to fix this by adding
respawn? #t to the service to make it restart until it succeeds.
https://guix.gnu.org/manual/en/html_node/Shepherd-Services.html#Shepherd-Services
;;definition
Hello,
I did a quick search in the tracker and the mailing list archives but
couldn't find a similar topic, apologies if this was already
discussed.
I was playing with Guix Home and I'm a bit surprised by how user
services are managed, especially the Shepherd itself.
Let's say I start from a
Hi Guix,
I often find my self using inheritance of package to add native-inputs
that are not stricly necessary for building the project, but are used
for developement purpose like so:
-
(define base-native-inputs (list ...))
(define my-package
Hi,
reading [0], I would like to ask if there is any interest in
up-streaming the work I have been doing to build old versions of Emacs
using Guix (the main use-case is to help with testing Emacs packages on
various versions)[1]? My fear is that with further upstream development,
there might
> + (define-public go-github-com-niemeyer-pretty
> + (package
> +(name "go-github-com-niemeyer-pretty")
> +(version "0.0.0-20200227124842-a10e7caefd8e")
> +(source
> + (origin
> +(method git-fetch)
> +(uri (git-reference
< + (url
