From: David Craven <david@craven.ch>
To: Dmitri Anikin <anarki@teknik.io>
Cc: help-guix@gnu.org
Subject: Re: Broken guix pull
Date: Sun, 18 Dec 2016 21:30:12 +0100 [thread overview]
Message-ID: <CAL1_imk=9D50Kwo8T-jNnPu2fOOKnsbE43oNkDtCrSJE1G+TLw@mail.gmail.com> (raw)
In-Reply-To: <765dd961b7110b356c83fe8c654c07b1@mail.teknik.io>
> When I try guix pull, it fails everytime on
Yep, this happens sometimes with *-module-import-compiled derivations.
Have you tried with the --fallback flag like it says in the error
message? That usually fixes it.
next prev parent reply other threads:[~2016-12-18 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 20:20 Broken guix pull Dmitri Anikin
2016-12-18 20:30 ` David Craven [this message]
2016-12-18 21:03 ` David Craven
2016-12-18 21:16 ` Leo Famulari
2016-12-19 11:34 ` Dmitri Anikin
2016-12-19 15:14 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2021-07-02 15:29 Broken Guix Pull Christopher Howard
2021-07-02 21:16 ` Maxim Cournoyer
2021-07-02 22:16 ` Tobias Geerinckx-Rice
2021-07-02 22:56 ` Christopher Howard
2021-07-03 5:17 ` Christopher Howard
2021-07-03 5:59 ` Christopher Howard
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='CAL1_imk=9D50Kwo8T-jNnPu2fOOKnsbE43oNkDtCrSJE1G+TLw@mail.gmail.com' \
--to=david@craven.ch \
--cc=anarki@teknik.io \
--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).