From: Gary Johnson <lambdatronic@disroot.org>
To: Joshua Branson <jbranso@dismail.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Errors with guix pull
Date: Mon, 17 Aug 2020 16:09:27 -0400 [thread overview]
Message-ID: <87y2md591k.fsf@disroot.org> (raw)
In-Reply-To: <87wo29m6iy.fsf@dismail.de>
Hi Joshua,
No, I was just building guix using the standard "guix pull" command.
After quite a lot of experimenting, I was able to solve my own problem a
few weeks ago by uninstalling guile from my user profile. I'm not sure
why that messed up "guix pull", but at least with guile uninstalled, I
was able to upgrade guix successfully.
Lessons learned, I guess.
~Gary
Joshua Branson <jbranso@dismail.de> writes:
> Are you building guix from git by chance?
--
GPG Key ID: 7BC158ED
Use `gpg --search-keys lambdatronic' to find me
Protect yourself from surveillance: https://emailselfdefense.fsf.org
=======================================================================
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Please avoid sending me MS-Office attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
prev parent reply other threads:[~2020-08-17 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 23:48 Errors with guix pull Gary Johnson
2020-08-08 16:44 ` Joshua Branson
2020-08-17 20:09 ` Gary Johnson [this message]
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=87y2md591k.fsf@disroot.org \
--to=lambdatronic@disroot.org \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.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
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).