From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 25139-done@debbugs.gnu.org
Subject: bug#25139: making the update procedure more obvious
Date: Mon, 19 Dec 2016 15:09:45 +0100 [thread overview]
Message-ID: <87twa03t92.fsf@gnu.org> (raw)
In-Reply-To: <874m2e7850.fsf@pc102091.liv.ac.uk> (Dave Love's message of "Thu, 08 Dec 2016 15:28:11 +0000")
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Hi,
Dave Love <fx@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:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1544 bytes --]
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.
[-- Attachment #3: Type: text/plain, Size: 23 bytes --]
Thanks!
Ludo’.
prev parent reply other threads:[~2016-12-19 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 15:28 bug#25139: making the update procedure more obvious Dave Love
2016-12-19 14:09 ` Ludovic Courtès [this message]
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=87twa03t92.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25139-done@debbugs.gnu.org \
--cc=fx@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).