From: Gottfried <gottfried@posteo.de>
To: help-guix@gnu.org
Subject: guix pull
Date: Wed, 16 Feb 2022 16:28:08 +0000 [thread overview]
Message-ID: <678d7b85-d8b3-6d84-b569-d3e3298ec95f@posteo.de> (raw)
Hi,
how often do I have to do a "guix pull"? Once a week, or twice a week,
or every second week?
Are there possibilities to know, when security updates are made and I
should do a guix pull?
Should I do a guix pull basically in my user account?
Or should I do a guix pull basically in the root account?
As far as I understood if I do a gux pull in my user account, it has no
influence to the root account?
But If I do a guix pull only in my user account, it would mean, as far
as I understand it, the root account would not get security updates?
What should be the procedure?
Gottfried
next reply other threads:[~2022-02-16 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:28 Gottfried [this message]
2022-02-16 17:19 ` guix pull Leo Famulari
2022-02-16 17:55 ` pelzflorian (Florian Pelz)
2022-02-16 19:22 ` Gottfried
2022-02-16 19:28 ` Gottfried
2022-02-16 20:27 ` Leo Famulari
2022-02-16 20:09 ` Ricardo Wurmus
2022-02-16 20:35 ` Gottfried
2022-02-16 22:36 ` Ricardo Wurmus
2022-02-16 20:38 ` Gottfried
2022-02-16 22:58 ` Ricardo Wurmus
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=678d7b85-d8b3-6d84-b569-d3e3298ec95f@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@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.
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).