GNU bug report logs - #25139
making the update procedure more obvious

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: tracker <at> debbugs.gnu.org
Subject: bug#25139: closed (making the update procedure more obvious)
Date: Mon, 19 Dec 2016 14:11:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 19 Dec 2016 15:09:45 +0100
with message-id <87twa03t92.fsf <at> gnu.org>
and subject line Re: bug#25139: making the update procedure more obvious
has caused the debbugs.gnu.org bug report #25139,
regarding making the update procedure more obvious
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
25139: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25139
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Dave Love <fx <at> gnu.org>
To: bug-guix <at> gnu.org
Subject: making the update procedure more obvious
Date: Thu, 08 Dec 2016 15:28:11 +0000

It's not very obvious to a newcomer how to update to a new release as
it's rather buried in the doc.  I think it would help to reference
"pull" in the installation section of the manual, and maybe in release
announcements, and to index "upgrading" and/or "upgrades" in the manual.
I'm not sure it's worth me suggesting a patch, but I could if it helps.

[Message part 3 (message/rfc822, inline)]

From: ludo <at> gnu.org (Ludovic Courtès)
To: Dave Love <fx <at> gnu.org>
Cc: 25139-done <at> debbugs.gnu.org
Subject: Re: bug#25139: making the update procedure more obvious
Date: Mon, 19 Dec 2016 15:09:45 +0100

[Message part 4 (text/plain, inline)]

Hi,

Dave Love <fx <at> gnu.org> skribis:

> It's not very obvious to a newcomer how to update to a new release as
> it's rather buried in the doc.  I think it would help to reference
> "pull" in the installation section of the manual, and maybe in release
> announcements, and to index "upgrading" and/or "upgrades" in the manual.
> I'm not sure it's worth me suggesting a patch, but I could if it helps.

I made these changes:

[Message part 5 (text/x-patch, inline)]

modified   doc/guix.texi
@@ -359,6 +359,9 @@ without interference.  Its data lives exclusively in two directories,
 usually @file{/gnu/store} and @file{/var/guix}; other files on your
 system, such as @file{/etc}, are left untouched.
 
+Once installed, Guix can be updated by running @command{guix pull}
+(@pxref{Invoking guix pull}).
+
 @menu
 * Binary Installation::         Getting Guix running in no time!
 * Requirements::                Software needed to build and run Guix.
@@ -2308,6 +2311,7 @@ this option is primarily useful when the daemon was running with
 @section Invoking @command{guix pull}
 
 @cindex upgrading Guix
+@cindex updating Guix
 @cindex @command{guix pull}
 @cindex pull
 Packages are installed or upgraded to the latest version available in
@@ -6949,6 +6953,14 @@ initialized by running the @command{passwd} command as @code{root},
 unless your configuration specifies otherwise
 (@pxref{user-account-password, user account passwords}).
 
+@cindex upgrading GuixSD
+From then on, you can update GuixSD whenever you want by running
+@command{guix pull} as @code{root} (@pxref{Invoking guix pull}), and
+then running @command{guix system reconfigure} to build a new system
+generation with the latest packages and services (@pxref{Invoking guix
+system}).  We recommend doing that regularly so that your system
+includes the latest security updates (@pxref{Security Updates}).
+
 Join us on @code{#guix} on the Freenode IRC network or on
 @file{guix-devel@@gnu.org} to share your experience---good or not so
 good.

[Message part 6 (text/plain, inline)]

Thanks!

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.