From: <pkill9@runbox.com>
To: 34402@debbugs.gnu.org
Subject: bug#34402: Inferior channel (I believe 'inferior-for-channels' function specifically) sometimes fails
Date: Sat, 09 Feb 2019 11:11:39 +0000 (GMT) [thread overview]
Message-ID: <E1gsQXs-0001oo-0Z@rmmprod07.runbox> (raw)
Often I'll get this output when building a manifest* with an inferior:
```
itsme@antelope /tmp$ guix package -n -m example-inferior.scm
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
guix package: error: failed to load 'example-inferior.scm':
```
I believe this is the 'inferior-for-channels' function that fails.
After investigating a while back, it seems removing the relevant checkout in ~/.cache/guix/checkouts temporarily fixes it, but the issue often comes back.
* The manifest used is the example from the Guix manual in the section on Inferiors, with the guix commit in the manifest replaced with my guix revision:
```
(use-modules (guix inferior) (guix channels)
(srfi srfi-1)) ;for 'first'
(define channels
;; This is the old revision from which we want to
;; extract guile-json.
(list (channel
(name 'guix)
(url "https://git.savannah.gnu.org/git/guix.git")
(commit
"722ac64cd7dc1f09fb77e2ae780427fa13c03110"))))
(define inferior
;; An inferior representing the above revision.
(inferior-for-channels channels))
;; Now create a manifest with the current "guile" package
;; and the old "guile-json" package.
(packages->manifest
(list (first (lookup-inferior-packages inferior "guile-json"))
(specification->package "guile")))
```
next reply other threads:[~2019-02-09 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1gssTo-0001GJ-El@rmmprod07.runbox>
2019-02-09 11:11 ` pkill9 [this message]
2019-02-09 14:12 ` bug#34402: Inferior channel (I believe 'inferior-for-channels' function specifically) sometimes fails Ludovic Courtès
2019-02-09 15:49 ` pkill9
2019-02-12 22:35 ` 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
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=E1gsQXs-0001oo-0Z@rmmprod07.runbox \
--to=pkill9@runbox.com \
--cc=34402@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 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).