[debbugs-tracker] bug#19671: closed (Raw binary data in build log from substitute-binary)

[GNU bug Tracking System]

Your message dated Sun, 05 Apr 2015 00:01:56 +0200
with message-id <address@hidden>
and subject line Re: bug#19671: Raw binary data in build log from 
substitute-binary
has caused the debbugs.gnu.org bug report #19671,
regarding Raw binary data in build log from substitute-binary
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
19671: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19671
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: Raw binary data in build log from substitute-binary Date: Sat, 24 Jan 2015 04:03:04 -0500

While trying to install 'racket' using substitutes, several lines of the
form "substitute-binary: <binary garbage>" were output.  See the
attachment for the precise output, captured via Emacs' shell mode.

This was when running guix from git commit 2dfed64 on an i686 GSD
system.

Any ideas what would cause this?

      Mark

substitute-binary-spewage
Description: transcript of output

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#19671: Raw binary data in build log from substitute-binary
>
>
>
>
> Date: 
>
> Sun, 05 Apr 2015 00:01:56 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
>
>
>
>
> address@hidden (Ludovic Courtès) skribis:
>
> > This has just happened to me as well, and I think the reason is that,
> > when a download failure happens (500, 502, 504, etc.), the thread doing
> > the download directly writes to the current error port.
> >
> > And as we know, ports are not thread-safe in Guile 2.0 and we’re not
> > doing additional synchronization here, so everything wrecks havoc.
> >
> > This is another incentive to merge wip-http-pipelining.  I’ll give it
> > another try.
>
> This was done in d3a6520, so closing this bug.
>
> Ludo’.
>
>
> --- End Message ---