unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 41409@debbugs.gnu.org
Subject: bug#41409: “guix pull” should show a progress bar for channel updates
Date: Fri, 22 May 2020 00:29:14 +0200	[thread overview]
Message-ID: <CAJ3okZ34VFPPw3dJ1dxNio20_FrM350XJf8Dw3wj4_PaoB9jDA@mail.gmail.com> (raw)
In-Reply-To: <87367tdp8u.fsf@elephly.net>

On Thu, 21 May 2020 at 22:09, Ricardo Wurmus <rekado@elephly.net> wrote:

> It can take several seconds or even over a few minutes when fetching
> from multiple channels.  For what it’s worth I got annoyed waiting for
> “guix pull” on ci.guix.gnu.org, which has a pretty decent network
> connection (even though users on the outside cannot see it this way due
> to the firewall).

Wow! Few minutes.  To me, each channel (Gitlab, GitHub, etc.)  takes a
couple of seconds -- even with a poor Wifi connection -- and the
longest is Guix from Savannah: and "slow" as everything under gnu.org.
I feel much more frustrated by "Computing Guix derivation" which takes
ages on my machine and I never know if the computations are at 20% or
80% or whatever.
And I never pull on my laptop the current HEAD of master otherwise I
am waiting between 10 and 30 minutes building all the derivations
because they are not substituable yet; well I pull 1 or 2 weeks
behind.

Well, a spinner for the Git updating part could improve use cases:
first pull, long period between 2 pulls, firewall, etc..
On the other hand, an European mirror of guix.git could help too, IMHO.

Cheers,
simon




  reply	other threads:[~2020-05-21 22:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 21:30 bug#41409: “guix pull” should show a progress bar for channel updates Ricardo Wurmus
2020-05-21 11:00 ` zimoun
2020-05-21 20:09   ` Ricardo Wurmus
2020-05-21 22:29     ` zimoun [this message]
2020-05-24 21:17 ` Ludovic Courtès
2020-10-05  7:45   ` bug#39260: " Ludovic Courtès
2020-10-12 21:30     ` Ludovic Courtès
2020-10-26 22:52       ` bug#39260: " 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=CAJ3okZ34VFPPw3dJ1dxNio20_FrM350XJf8Dw3wj4_PaoB9jDA@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=41409@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).