unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed

From: Gottfried <gottfried@posteo.de>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
	Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: guix pull
Date: Wed, 16 Feb 2022 19:22:57 +0000	[thread overview]
Message-ID: <9fdfbcab-5435-3914-4ccd-21b186fe5060@posteo.de> (raw)
In-Reply-To: <20220216175503.u6zitslgnloqq2w6@pelzflorian.localdomain>

thanks

is there a possibility to run a guix pull for root and for the user 
together, in order not to do it twice, because it needs quite a long 
time, compared to other Linux distros, where updating takes only some 
minutes. (Debian based distros, Manjaro, Endeavour OS and so on).

If you do a guix pull, in my case I can´t do it at the end of my work, 
because I would have to wait for finishing more than 30 minutes.

Is it not better to run a guix pull also regularly for root, in order 
that root has also updated versions...

In my understanding (as a layman) it would leave root behind and leads 
may be to inconsistency's in the guix system.


regards

Gottfried



Am 16.02.22 um 18:55 schrieb pelzflorian (Florian Pelz):
> On Wed, Feb 16, 2022 at 12:19:58PM -0500, Leo Famulari wrote:
>> On Wed, Feb 16, 2022 at 04:28:08PM +0000, Gottfried wrote:
>>> 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`.
>>
>
> Note however that
>
> sudo guix system reconfigure /etc/config.scm
>
> uses the guix of the user who is running sudo.
>
> Seehttps://guix.gnu.org/en/manual/devel/de/html_node/Nach-der-Systeminstallation.html
>
> It is therefore possible to never use root’s guix .
>
> Regards,
> Florian

next prev parent reply	other threads:[~2022-02-16 19:25 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 [this message]
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=9fdfbcab-5435-3914-4ccd-21b186fe5060@posteo.de \
    --to=gottfried@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    --cc=pelzflorian@pelzflorian.de \
    /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

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).