From: ng0 <contact.ng0@cryptolab.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: guix pull takes forever
Date: Thu, 9 Mar 2017 00:10:18 +0000 [thread overview]
Message-ID: <20170309001018.76gxsnj4v22plf7b@abyayala> (raw)
In-Reply-To: <20170308223623.GA2762@jasmine>
Leo Famulari transcribed 0.9K bytes:
> On Wed, Mar 08, 2017 at 09:38:58AM +0000, ng0 wrote:
> > Hi,
> >
> > with current master and using 'guix pull' instead of a git checkout
> > update, the process takes more than 9 hours.
>
> Unfortunately, I can't reproduce this.
>
> > I restarted it this morning, it's the same. Basically what I see is
> > just:
> >
> > Starting download of /tmp/guix-file.foooo
> > From http://urllbla.tar.gz
> > [status line of 11.1MiB transfered]
> > substitute: updating list of substitutes from bayfront 100%
> > substitute: updating list of substitutes from bayfront 100%
> > unpacking '/gnu/store/aaaaaaaaaa-guix-latest.tar.gz'
> > substitute: updating list of substitutes from bayfront 100%
> > substitute: updating list of substitutes from bayfront 100%
> > substitute: updating list of substitutes from bayfront 100%
>
> What happens if you try using the mirror <https://mirror.hydra.gnu.org>
> instead? Bayfront is not online, as far as I know.
>
I have 3 mirrors in my list, and up until yesterday all were being
picked up (except for the onion, where I still need clearer advice on how
to configure this - my current advice is to replicate the hydra build
farm and provide an substitute server myself I can test with).
'guix pull' round 1: 8 hours, round 2: ~12 hours, round 3: ~4 hours.
None of them succeded.
next prev parent reply other threads:[~2017-03-08 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 9:38 guix pull takes forever ng0
2017-03-08 22:36 ` Leo Famulari
2017-03-09 0:10 ` ng0 [this message]
2017-03-09 1:18 ` ng0
2017-03-09 1:32 ` ng0
2017-03-09 12:38 ` Ludovic Courtès
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=20170309001018.76gxsnj4v22plf7b@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).