From: Joshua Branson <jbranso@fastmail.com>
To: help-guix@gnu.org
Subject: Re: Could not find bootstrap binary 'guile-2.0.9.tar.xz'
Date: Thu, 19 Apr 2018 17:26:05 -0400 [thread overview]
Message-ID: <ygfh8o6evma.fsf@fastmail.com> (raw)
In-Reply-To: <87bmeficks.fsf@netris.org> (Mark H. Weaver's message of "Thu, 19 Apr 2018 08:51:31 -0400")
thanks for the clarification!
Mark H Weaver <mhw@netris.org> writes:
> Joshua Branson <jbranso@fastmail.com> writes:
>
>> I guess I'm still a little confused. Suppose that I want to update all
>> packages, on my system. The ones owned by root, and the ones owned by
>> all other users. Then I'd do this?
>>
>> $ guix pull && guix package -u
>>
>> $ logout
>>
>> $ login DifferentUser
>>
>> $ guix pull && guix package -u
>>
>> ...repeat for all other users...
>>
>> $ su
>>
>> # guix pull && guix package -u && guix system reconfigure /etc/config.scm
>>
>> Does that look right?
>
> Yes, exactly.
>
> I should also mention that if you'd like to avoid some or all of these
> 'guix pull's, you can arrange for user B to always track user A's copy
> of Guix like this:
>
> ln -sf {~A,~B}/.config/guix/latest
>
> However, manually fiddling with these symlinks is not officially
> supported and might stop working in a future version of Guix. Also,
> beware that if you accidentally run "guix pull" as user B, it will
> overwrite the symlink, and henceforth user B will no longer track user A
> until you re-run the above command.
>
> Alternatively, if you don't want user B to _track_ user A, but you just
> ran "guix pull" as user A and now you want to quickly update user B to
> the same copy of Guix, you can do this:
>
> cp -a {~A,~B}/.config/guix/latest
>
> Mark
next prev parent reply other threads:[~2018-04-19 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87604s12j9.fsf@shack@muto.ca>
2018-04-17 20:50 ` Could not find bootstrap binary 'guile-2.0.9.tar.xz' Joshua Branson
2018-04-18 19:56 ` Mark H Weaver
2018-04-18 21:53 ` Clément Lassieur
2018-04-19 0:03 ` Joshua Branson
2018-04-19 12:51 ` Mark H Weaver
2018-04-19 21:26 ` Joshua Branson [this message]
[not found] <5ad3ddfd.471ac80a.eed6.d70eSMTPIN_ADDED_BROKEN@mx.google.com>
2018-04-27 14:48 ` Catonano
2018-04-27 16:32 ` Catonano
2018-04-27 17:16 ` Melon
[not found] ` <5ae35b00.1c69fb81.a62b3.f49dSMTPIN_ADDED_BROKEN@mx.google.com>
2018-04-27 17:52 ` Catonano
2018-04-15 23:19 Muto
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=ygfh8o6evma.fsf@fastmail.com \
--to=jbranso@fastmail.com \
--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).