unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 41409@debbugs.gnu.org, 39260@debbugs.gnu.org
Subject: bug#39260: bug#41409: “guix pull” should show a progress bar for channel updates
Date: Mon, 05 Oct 2020 09:45:40 +0200	[thread overview]
Message-ID: <874kn96rq3.fsf@gnu.org> (raw)
In-Reply-To: <875zclyqve.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 24 May 2020 23:17:41 +0200")

Hi,

Ludovic Courtès <ludo@gnu.org> skribis:

> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> When I run “guix pull” (or “guix time-machine”) I see this message
>>
>>    Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
>>
>> followed by disconcerting silence.  I can’t tell if it’s doing
>> something, nor can I see what the progress is.
>
> For the record, the main missing piece is in Guile-Git, which does not
> yet provide bindings to the progress-report thingie for fetch
> operations.

I’ve added support for the ‘transfer-progress’ callback in Guile-Git:

  https://gitlab.com/guile-git/guile-git/-/commit/7a3d97a72e7907213241f62d3bac926361f50f95

However, there’s an (unrelated) issue with libgit2 meaning that
Guile-Git is not in a releasable state yet:

  https://github.com/libgit2/libgit2/issues/5650

Ludo’.




  reply	other threads:[~2020-10-05  7:46 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
2020-05-24 21:17 ` Ludovic Courtès
2020-10-05  7:45   ` Ludovic Courtès [this message]
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=874kn96rq3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39260@debbugs.gnu.org \
    --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).