From: Gottfried <gottfried@posteo.de>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: guix pull
Date: Wed, 16 Feb 2022 19:28:35 +0000 [thread overview]
Message-ID: <2b539a93-d9e8-a561-2bf4-15b62717965a@posteo.de> (raw)
In-Reply-To: <Yg0yPpS4VgVTwCha@jasmine.lan>
In other Linux distros there is always an immediate announcement if
there are security updates and package updates available.
In guix system it seems, according to Your answer, it does not
happen. (May be in future if it will be developed?)
regards
Gottfried
Am 16.02.22 um 18:19 schrieb Leo Famulari:
> On Wed, Feb 16, 2022 at 04:28:08PM +0000, Gottfried wrote:
>> how often do I have to do a "guix pull"? Once a week, or twice a week, or
>> every second week?
> You never *have* to do it, but I recommend you do it at least once a
> week, if that works for you. There are security problems fixed in every
> update of packages with big codebases, such as browsers, kernels, etc.
>
>> Are there possibilities to know, when security updates are made and I should
>> do a guix pull?
> Currently we only announce security fixes in Guix itself. That is, we
> do not announce security updates of packages, although we do often
> mention them in the Git log:
>
> https://git.savannah.gnu.org/cgit/guix.git/log/
>
>> 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?
> Correct.
>
> `guix pull` is per-user. Every user can do their own `guix pull`, and it
> doesn't affect any other user. Root is just another user. There is
> nothing special about root from this perspective.
>
>> 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?
> Correct.
>
>> What should be the procedure?
> As each user that you wish to update, do `guix pull` to update Guix and
> the list of available packages and services, and then do `guix upgrade`
> to actually upgrade your packages. If you use Guix System, you upgrade
> the system with `guix system reconfigure`.
next prev parent reply other threads:[~2022-02-16 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:28 guix pull Gottfried
2022-02-16 17:19 ` Leo Famulari
2022-02-16 17:55 ` pelzflorian (Florian Pelz)
2022-02-16 19:22 ` Gottfried
2022-02-16 19:28 ` Gottfried [this message]
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=2b539a93-d9e8-a561-2bf4-15b62717965a@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).