From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 28756@debbugs.gnu.org
Subject: bug#28756: closed (Re: bug#28756: Substitute download progress bar doesn't reach 100%)
Date: Mon, 30 Oct 2017 17:37:57 +0100 [thread overview]
Message-ID: <87lgjs4mmy.fsf@gnu.org> (raw)
In-Reply-To: <20171030143013.GA9843@jasmine.lan> (Leo Famulari's message of "Mon, 30 Oct 2017 10:30:13 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Tue, Oct 17, 2017 at 11:12:04AM +0000, GNU bug Tracking System wrote:
>> Your bug report
>>
>> #28756: Substitute download progress bar doesn't reach 100%
>>
>> which was filed against the guix package, has been closed.
>>
>> The explanation is attached below, along with your original report.
>> If you require more details, please reply to 28756@debbugs.gnu.org.
>
> I noticed today that the progress bar does reach 100%, but then resets
> to 0% after the download is complete. For example:
>
> python-2.7.13 15.0MiB 0B/s 00:09 [ ] 0.0%
I think that’s because we haven’t updated our ‘guix’ package to include
that commit, though.
Did you try with guix-daemon from master, as in:
sudo -E ./pre-inst-env guix-daemon …
?
Ludo’.
prev parent reply other threads:[~2017-10-30 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 3:52 bug#28756: Substitute download progress bar doesn't reach 100% Leo Famulari
2017-10-09 7:41 ` Ludovic Courtès
2017-10-12 14:39 ` 宋文武
2017-10-14 15:05 ` 宋文武
2017-10-15 19:33 ` Ludovic Courtès
2017-10-16 13:06 ` 宋文武
2017-10-17 7:16 ` Ludovic Courtès
2017-10-17 11:10 ` 宋文武
2017-10-17 12:03 ` Ludovic Courtès
[not found] ` <handler.28756.D28756.150823866318807.notifdone@debbugs.gnu.org>
2017-10-30 14:30 ` bug#28756: closed (Re: bug#28756: Substitute download progress bar doesn't reach 100%) Leo Famulari
2017-10-30 16:37 ` Ludovic Courtès [this message]
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=87lgjs4mmy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28756@debbugs.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).