From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 39952@debbugs.gnu.org
Subject: bug#39952: Bug Report with Guix Pull on Ubuntu 18.04.3 LTS
Date: Fri, 06 Mar 2020 16:58:51 +0100 [thread overview]
Message-ID: <874kv18og4.fsf@nckx> (raw)
In-Reply-To: <SN6PR10MB25285E6F49AD7C574F5F7894AAE30@SN6PR10MB2528.namprd10.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
Hullo,
Thanks for submitting a bug report!
Lee Jia Hong 写道:
> […]
> In srfi/srfi-1.scm:
> 592:17 0 (map1 (("source" #<origin #<<git-reference> url:
> "https://notabug.org/cwebber/g
> uile-gcrypt.git" co?>) ?))
Guix was unable to check out this source repository, possibly
(likely) because of a network failure.
It's possible that today's scheduled ci.guix.gnu.org maintenance
made this problem worse. The main substitute server should be
back up now.
> srfi/srfi-1.scm:592:17: In procedure map1:
> Throw to key `srfi-34' with args `(#<condition
> &store-protocol-error [message: "some substit
> utes for the outputs of derivation
> `/gnu/store/v03jcr1nhdj2fw8813wli3zp4drsnzsd-bzip2-1.0.6.
> tar.gz.drv' failed (usually happens due to networking issues);
> try `--fallback' to build der
> ivation from source " status: 1] 7b927b0>)'.
Try running ‘guix pull’ again, it might simply have been a bad
connection. If that still fails with the same message and URL,
try ‘guix pull --fallback’. Let us know what happens.
> guix pull: error: You found a bug: […]
> Please report it by email to <bug-guix@gnu.org>.
This was probably not a bug in Guix. This message is a bit too
eager, but at least it gets bug reports :-)
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-03-06 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 15:17 bug#39952: Bug Report with Guix Pull on Ubuntu 18.04.3 LTS Lee Jia Hong
2020-03-06 15:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [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=874kv18og4.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=39952@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).