unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Mohammad Akhlaghi <akhlaghi@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix pull failure for Python 2.7.11
Date: Tue, 13 Jun 2017 21:42:34 +0200	[thread overview]
Message-ID: <878tkvr7x1.fsf@elephly.net> (raw)
In-Reply-To: <39854d3a-e4e9-80cf-167d-7dd22951f222@gnu.org>


Hi Mohammad,

> Since the error is about connection, I should say that I was connected
> to the internet when I ran `guix pull'.

Inside of the build environment there is no network connection, so this
test would always fail.

> Because of this failure, I am unable to continue pulling the
> higher-level changes/packages. So, I wanted to see if there is anything
> particular I can do to fix this? Is this particular to my machine/system?

I’m confused about this because 2.7.11 is pretty old.  Latest in Guix
appears to be 2.7.13.  When you do “guix pull” it should fetch the
latest version of Guix first, so I don’t see why you would be building
2.7.11.

I also see this message:

> substitute: guix substitute: warning: ACL for archive imports seems to be uninitialized, substitutes may be unavailable

If you want to use binaries from our build farm you need to authorize
the build farm’s public key.  (This is no longer needed for later
releases of Guix.)

I’d first try to fix that and re-run “guix pull”.  Since you are on an
old version of Guix, however, it is likely that we no longer provided
binaries for the packages you need.  In that case I would consider
installing the latest version via the binary release or from git.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-06-13 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 10:14 Guix pull failure for Python 2.7.11 Mohammad Akhlaghi
2017-06-13 19:42 ` Ricardo Wurmus [this message]
2017-06-14  9:34   ` Mohammad Akhlaghi

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=878tkvr7x1.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=akhlaghi@gnu.org \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).