l...@gnu.org (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
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 synchronizatio
Mark H Weaver skribis:
> Mark H Weaver writes:
>
>> While trying to install 'racket' using substitutes, several lines of the
>> form "substitute-binary: " were output. See the
>> attachment for the precise output, captured via Emacs' shell mode.
>>
>> This was when running guix from git commit
Mark H Weaver writes:
> While trying to install 'racket' using substitutes, several lines of the
> form "substitute-binary: " 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.
While trying to install 'racket' using substitutes, several lines of the
form "substitute-binary: " 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?
