From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#25139: making the update procedure more obvious Date: Mon, 19 Dec 2016 15:09:45 +0100 Message-ID: <87twa03t92.fsf@gnu.org> References: <874m2e7850.fsf@pc102091.liv.ac.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48256) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cIyef-0001BN-L2 for bug-guix@gnu.org; Mon, 19 Dec 2016 09:11:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cIyec-0003Xo-GW for bug-guix@gnu.org; Mon, 19 Dec 2016 09:11:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:59807) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cIyec-0003XZ-EG for bug-guix@gnu.org; Mon, 19 Dec 2016 09:11:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cIyec-0001UL-An for bug-guix@gnu.org; Mon, 19 Dec 2016 09:11:02 -0500 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <874m2e7850.fsf@pc102091.liv.ac.uk> (Dave Love's message of "Thu, 08 Dec 2016 15:28:11 +0000") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Dave Love Cc: 25139-done@debbugs.gnu.org --=-=-= Content-Type: text/plain Hi, Dave Love 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: --=-=-= Content-Type: text/x-patch Content-Disposition: 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. --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thanks! Ludo=E2=80=99. --=-=-=--