From: Sergey Trofimov <sarg@sarg.org.ru>
To: Feng Shu <tumashu@163.com>
Cc: 68415@debbugs.gnu.org
Subject: bug#68415: User's shepherd services defined in guix home config can not start after guix pull.
Date: Tue, 16 Jan 2024 07:51:01 +0100 [thread overview]
Message-ID: <87a5p5n4yr.fsf@sarg.org.ru> (raw)
In-Reply-To: <871qalreyk.fsf@163.com>
Feng Shu <tumashu@163.com> writes:
> After I guix pull, services defined in guix home config can no
> start:
>
> -------------------------
> 服务 root 已启动。
> WARNING: Use of `load' in declarative module (#{ g117}#). Add
> #:declarative? #f to your define-module invocation.
> unbound-variable(#f "Unbound variable: ~S" (service) #f)
>
> Some deprecated features have been used. Set the environment
> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
> program to get more information. Set it to "no" to suppress
> this message.
> Creating XDG user directories... done
> Comparing
> /gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts
> and
> /gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts...
> done (same)
> Evaluating on-change gexps.
>
> -----------
>
> When I run command: herd status, show error:
>
> feng@Guix ~$ herd status
> error: connect: /run/user/1000/shepherd/socket: No such file or
> directory
Have you tried debugging it? Is your home shepherd running? Do you
see shepherd mentions in ~/.guix-home/on-first-login?
Have you tried restarting your system?
next prev parent reply other threads:[~2024-01-16 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 5:15 bug#68415: User's shepherd services defined in guix home config can not start after guix pull Feng Shu
2024-01-16 6:51 ` Sergey Trofimov [this message]
2024-01-16 12:44 ` Feng Shu
2024-01-17 7:04 ` Sergey Trofimov
2024-01-17 12:55 ` Feng Shu
2024-03-31 14:19 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5p5n4yr.fsf@sarg.org.ru \
--to=sarg@sarg.org.ru \
--cc=68415@debbugs.gnu.org \
--cc=tumashu@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.