unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 33030@debbugs.gnu.org
Subject: bug#33030: Crash in progress-bar
Date: Mon, 15 Oct 2018 11:20:42 +0200	[thread overview]
Message-ID: <87in23k1lh.fsf@gnu.org> (raw)
In-Reply-To: <20181013025308.GA22913@jasmine.lan> (Leo Famulari's message of "Fri, 12 Oct 2018 22:53:08 -0400")

Hi Leo,

Leo Famulari <leo@famulari.name> skribis:

> $ guix --version
> guix (GNU Guix) aa227b3be3d7728331a08dbd139c47c9b271dc23
> Copyright (C) 2018 the Guix authors
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> $ ./pre-inst-env guix package -u .
> [...]
> downloading from https://private.mirror/guix/nar/gzip/iql35g1g5q9dkap5splc7f9ggskr31vl-NamesList.txt...
> Backtrace:.txt  347KiB                               1.4MiB/s 00:00 [################  ]  92.3%

[...]

>    208:33  2 (display-download-progress _ _ #:start-time _ # _ # _)
>    183:12  1 (progress-bar _ _)
> In unknown file:
>            0 (make-string -51 #\space)

Could you run:

  guix build --log-file \
    /gnu/store/iql35g1g5q9dkap5splc7f9ggskr31vl-NamesList.txt

and post the contents of the file?

This should allow us to bridge the gap with Mark’s analysis.

Thanks in advance,
Ludo’.

  parent reply	other threads:[~2018-10-15  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-13  2:53 bug#33030: Crash in progress-bar Leo Famulari
2018-10-13 22:39 ` Mark H Weaver
2018-10-15  9:20 ` Ludovic Courtès [this message]
2018-10-16  4:57   ` Leo Famulari
2018-10-16 11:32     ` Ludovic Courtès
2018-11-11 20:55 ` Ricardo Wurmus
2018-11-16 18:04   ` Ludovic Courtès
2018-11-19  9:48     ` Clément Lassieur

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=87in23k1lh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33030@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).