From: sirgazil <sirgazil@zoho.com>
To: "Efraim Flashner" <efraim@flashner.co.il>
Cc: "Guix Help" <help-guix@gnu.org>
Subject: Re: guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found
Date: Mon, 11 May 2020 09:03:45 -0500 [thread overview]
Message-ID: <172040c76e1.fee2567482159.8983597069257542014@zoho.com> (raw)
In-Reply-To: <20200510122643.GB1473@E5400>
---- On Sun, 10 May 2020 07:26:43 -0500 Efraim Flashner <efraim@flashner.co.il> wrote ----
>
> I recently upgraded my kids' computer post-core-update merge and I ran
> into the same issue. The trick was to make sure to use
> ~/.configure/guix/bin/guix for 'guix pull' and not
> '/run/current-system/profile/bin/guix'. For the new user I'd recommend
> running 'guix pull' for them once using another user's guix binary.
Thanks, Efraim. How would I do the latter, though. My user "sirgazil" has a working guix, my user "felipe" doesn't.
next prev parent reply other threads:[~2020-05-11 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 13:57 guix pull: error: glibc-bootstrap-system-2.2.5.patch: patch not found sirgazil
2020-05-10 12:26 ` Efraim Flashner
2020-05-11 14:03 ` sirgazil [this message]
2020-05-11 17:44 ` Efraim Flashner
2020-05-11 18:42 ` sirgazil
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=172040c76e1.fee2567482159.8983597069257542014@zoho.com \
--to=sirgazil@zoho.com \
--cc=efraim@flashner.co.il \
--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).