From: Vagrant Cascadian <vagrant@debian.org>
To: 29570@debbugs.gnu.org
Subject: bug#29570: challenge Backtraces
Date: Mon, 04 Dec 2017 15:16:35 -0800 [thread overview]
Message-ID: <87wp22w0bw.fsf@aikidev.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
After a recent guix pull, I'm getting tracebacks when attempting to run
guix challenge.
I tried switching subsititues to a local caching proxy, not sure if that
could possibly break anything. But after switching back to using the
substitutes directly, the problem still persists.
$ guix --version
guix (GNU guix) 1fa37d1b55b1d25a9d20c7b50a531b763e7a1398
$ guix challenge --substitute-urls="https://berlin.guixsd.org https://mirror.hydra.gnu.org" linux-libre
Backtrace:
12 (primitive-load "/gnu/store/sy84f3kbjj2f2nl1ljbdcmsqrz8…")
In guix/ui.scm:
1452:12 11 (run-guix-command _ . _)
In ice-9/boot-9.scm:
837:9 10 (catch _ _ #<procedure 7f185b219070 at guix/ui.scm:513…> …)
837:9 9 (catch _ _ #<procedure 7f185b219088 at guix/ui.scm:611…> …)
837:9 8 (catch _ _ #<procedure 7f1857f1bd70 at guix/scripts/ch…> …)
In guix/scripts/challenge.scm:
304:13 7 (_)
In guix/store.scm:
1444:24 6 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
In guix/scripts/challenge.scm:
305:15 5 (_ _)
149:34 4 (_ _)
In srfi/srfi-1.scm:
679:15 3 (append-map _ _ . _)
592:17 2 (map1 ("https://berlin.guixsd.org"; "https://mirror.hy…"))
In guix/scripts/substitute.scm:
725:23 1 (lookup-narinfos "https://berlin.guixsd.org"; _)
697:16 0 (fetch-narinfos "https://berlin.guixsd.org"; ("/gnu/sto…"))
guix/scripts/substitute.scm:697:16: In procedure fetch-narinfos:
guix/scripts/substitute.scm:697:16: Wrong type to apply: #<syntax-transformer uri?>
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2017-12-04 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 23:16 Vagrant Cascadian [this message]
2017-12-05 20:56 ` bug#29570: challenge Backtraces Ludovic Courtès
2017-12-07 16:18 ` 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=87wp22w0bw.fsf@aikidev.net \
--to=vagrant@debian.org \
--cc=29570@debbugs.gnu.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.