From: sirgazil <lizagris@protonmail.com>
To: "25852@debbugs.gnu.org" <25852@debbugs.gnu.org>
Subject: bug#25852: Users not updating their installations of Guix
Date: Thu, 02 Mar 2017 13:16:45 -0500 [thread overview]
Message-ID: <v4Md4LhxBU1MiCxhAdKS27epHDVJwjKS8NhQANfkIBc-nmWLxrByl1PDUbCNJcMa-rpDIbeyPA5gpHTDYJzgemaytikwTA_I2ze66TLHv3E=@protonmail.com> (raw)
In-Reply-To: <20170223211156.GA24382@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Yes, I agree with both of you.
I'd like to see a section in the documentation, referenced from the installation instructions, with prescriptions about keeping Guix(SD) up to date. Say "Keeping a Guix(SD) system up to date". It could have, for example, what to do as a root user, what to do as a non-privileged user.
Also, I usually subscribe to the news feed of the software I use regularly. With Debian, for example, I update the system every time I get notified of new updates.[1] I'm subscribed to Guix news too, but I haven't seen posts recommending users to update their systems to fix security issues (except for release announcements). That's something I'd like to see too.
Guix website is currently using Haunt, which allows to generate feeds per tag in the blog, so we could even recommend users in the documentation to subscribe to a "security" news feed to keep informed of important updates.
My 2¢,
[1]: https://www.debian.org/News/2017/20170114
---
https://sirgazil.bitbucket.io/
[-- Attachment #2: Type: text/html, Size: 1381 bytes --]
next prev parent reply other threads:[~2017-03-02 18:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 21:11 bug#25852: Users not updating their installations of Guix Leo Famulari
2017-02-24 5:42 ` Pjotr Prins
2017-03-02 18:16 ` sirgazil [this message]
2017-03-04 20:29 ` Tomáš Čech
2017-03-04 22:43 ` Leo Famulari
2017-03-05 7:56 ` Tomáš Čech
2017-03-05 9:25 ` Pjotr Prins
2017-03-05 9:43 ` Tomáš Čech
2017-03-06 14:52 ` Ricardo Wurmus
2017-03-07 6:54 ` Pjotr Prins
2017-03-06 21:12 ` Ludovic Courtès
2017-03-06 21:34 ` Leo Famulari
2017-03-07 6:33 ` Tomáš Čech
2017-03-07 19:51 ` Leo Famulari
2017-03-07 20:58 ` Tomáš Čech
2017-03-07 22:22 ` Leo Famulari
2017-03-08 6:25 ` Tomáš Čech
2017-03-08 8:45 ` Leo Famulari
2017-03-08 9:24 ` Tomáš Čech
2017-03-08 18:15 ` Leo Famulari
2017-03-09 7:38 ` Efraim Flashner
2017-03-09 10:58 ` Ludovic Courtès
2017-03-09 12:42 ` Tomáš Čech
2017-03-09 15:42 ` Ludovic Courtès
2017-03-07 7:32 ` Mark H Weaver
2017-03-07 10:35 ` Ludovic Courtès
2017-03-11 1:48 ` Mark H Weaver
2017-05-10 13:12 ` Ludovic Courtès
2017-05-10 14:13 ` myglc2
2017-05-10 20:16 ` Ludovic Courtès
2017-05-12 6:06 ` Ricardo Wurmus
2017-05-12 8:29 ` Ludovic Courtès
2017-05-12 17:10 ` myglc2
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='v4Md4LhxBU1MiCxhAdKS27epHDVJwjKS8NhQANfkIBc-nmWLxrByl1PDUbCNJcMa-rpDIbeyPA5gpHTDYJzgemaytikwTA_I2ze66TLHv3E=@protonmail.com' \
--to=lizagris@protonmail.com \
--cc=25852@debbugs.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).