unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Divan Santana <divan@santanas.co.za>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: guixsd system reconfigure errors
Date: Thu, 02 Aug 2018 00:16:32 -0700	[thread overview]
Message-ID: <87k1p9ck6n.fsf@gmail.com> (raw)
In-Reply-To: <cuc1sbuqt22.fsf@santanas.co.za> (Divan Santana's message of "Mon, 23 Jul 2018 10:01:41 +0200")

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

Divan Santana <divan@santanas.co.za> writes:

> adding group 'tty'...
> groupadd: GID '996' already exists
>
> [...]
>
> Not sure if the system got in a strange state as a result of me changing
> my first user accounts name. Perhaps.

Could you share a minimal operating system configuration file that
reproduces the issue, and describe any specific steps you took that will
reproduce it (e.g., changing your first user account's name)?  You can
use "guix system vm" to quickly prototype a system for reproducing the
issue (see "Invoking guix system" in the manual), and this will make it
easier for everyone to pitch in and investigate.

> guix system: unloading service 'term-auto'...
> shepherd: Removing service 'term-auto'...
> shepherd: Done.
> guix system: loading new services: user-homes term-auto...
> shepherd: Evaluating user expression (register-services (primitive-load "/gnu/st?") #).
> shepherd: Service user-homes could not be started.
> shepherd: Service term-auto could not be started.
>
> The last two lines. Are these normal safe to ignore errors? Known bug or
> something specific to my system?

During reconfigure, Guix does not (currently) attempt to restart
currently running services.  So this is normal.  When you reboot, the
new version of the services should be used; you should reboot and verify
that they are running to complete the reconfigure action.  If things
don't work out, you can always select the previous version from the GRUB
menu or run "guix system roll-back" to go back to the previous system
generation.

Hope that helps!

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-08-02  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23  8:01 guixsd system reconfigure errors Divan Santana
2018-08-02  7:16 ` Chris Marusich [this message]
2018-08-05 18:43   ` Divan Santana

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1p9ck6n.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=divan@santanas.co.za \
    --cc=help-guix@gnu.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).