From: Ricardo Wurmus <rekado@elephly.net>
To: Fredrik Salomonsson <plattfot@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Help to workaround #28144
Date: Mon, 28 Jan 2019 09:38:31 +0100 [thread overview]
Message-ID: <871s4xrxbs.fsf@elephly.net> (raw)
In-Reply-To: <87zhrlqkgw.fsf@gmail.com>
Fredrik Salomonsson <plattfot@gmail.com> writes:
> Hello guix,
>
> I'm hitting the issue described in
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28144
>
> This happens when I do "guix pull", "guix package -u" or "guix
> environment guix".
>
> guix --version
> guix (GNU Guix) 0.16.0-8.7ba2b27
>
> The comments mention deleting "guix/profiles.go" should work as a work
> around. But I'm not sure which one that is. Is there a more detail
> explination somewhere that I can follow?
This would only help if you were using Guix from a git checkout. If you
don’t do that, your only way around this is to use an older version of
Guix to run “guix pull”, e.g. ~/.config/guix/current-1-link/bin/guix.
--
Ricardo
next prev parent reply other threads:[~2019-01-28 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 8:01 Help to workaround #28144 Fredrik Salomonsson
2019-01-28 8:38 ` Ricardo Wurmus [this message]
2019-01-29 8:01 ` Fredrik Salomonsson
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=871s4xrxbs.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=plattfot@gmail.com \
/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).