From mboxrd@z Thu Jan 1 00:00:00 1970 From: Divan Santana Subject: Re: guixsd system reconfigure errors Date: Sun, 05 Aug 2018 20:43:27 +0200 Message-ID: References: <87k1p9ck6n.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46036) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fmOUw-0003UR-CE for help-guix@gnu.org; Sun, 05 Aug 2018 15:15:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fmOUr-00084N-D8 for help-guix@gnu.org; Sun, 05 Aug 2018 15:15:26 -0400 Received: from outmail149075.authsmtp.net ([62.13.149.75]:31619) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fmOUp-0007wK-LT for help-guix@gnu.org; Sun, 05 Aug 2018 15:15:21 -0400 In-reply-to: <87k1p9ck6n.fsf@gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Chris Marusich Cc: "help-guix@gnu.org" >> 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. OK. Cool. I'll try do that sometime and feedback. >> 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. Ah, ok. > Hope that helps! It does thanks.