From: Giovanni Biscuolo <g@xelera.eu>
To: Danny Milosavljevic <dannym@scratchpost.org>, 36325@debbugs.gnu.org
Subject: bug#36325: In procedure put-string: Wrong type argument in position 1 (expecting open output port): #<closed: string 13c6cb0>
Date: Sat, 22 Jun 2019 09:02:09 +0200 [thread overview]
Message-ID: <87o92q6r2m.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <20190621201826.3ce6e0a8@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
Hello Danny,
Danny Milosavljevic <dannym@scratchpost.org> writes:
[...]
> guix environment: error: some substitutes for the outputs of
> derivation
> `/gnu/store/zxxw95x9ivw1a10v6nk1ls6d9i1csh3y-gcc-toolchain-5.5.0.drv'
> failed (usually happens due to networking issues); try `--fallback' to
> build derivation from source
I was not able to reproduce this on a Guix System machine I have: are
you sure it's not a networking issue?
This is what I did:
--8<---------------cut here---------------start------------->8---
~$ guix pull --commit=e6049c84dab3031fb64defae2c45a20b512d4644
~$ guix describe
Generation 2 Jun 22 2019 08:54:10 (current)
guix e6049c8
repository URL: https://git.savannah.gnu.org/git/guix.git
commit: e6049c84dab3031fb64defae2c45a20b512d4644
~$ guix environment -s i686-linux --ad-hoc gcc-toolchain@5.5.0
--8<---------------cut here---------------end--------------->8---
And I got a new env without errors.
HTH! Gio'.
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-06-22 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 18:18 bug#36325: In procedure put-string: Wrong type argument in position 1 (expecting open output port): #<closed: string 13c6cb0> Danny Milosavljevic
2019-06-22 7:02 ` Giovanni Biscuolo [this message]
2019-06-24 19:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o92q6r2m.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=36325@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.