unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: <pkill9@runbox.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34402 <34402@debbugs.gnu.org>
Subject: bug#34402: Inferior channel (I believe 'inferior-for-channels' function specifically) sometimes fails
Date: Sat, 09 Feb 2019 15:49:09 +0000 (GMT)	[thread overview]
Message-ID: <E1gsUsP-0002Sk-JN@rmmprod07.runbox> (raw)
In-Reply-To: <87pns1t5iv.fsf@gnu.org>

Nope, there is nothing after the colon in the output when this error shows up.

Ok, I will run that next time I get this error.

On Sat, 09 Feb 2019 15:12:24 +0100, Ludovic Courtès <ludo@gnu.org> wrote:

> Hello,
> 
> <pkill9@runbox.com> skribis:
> 
> > 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':
> > ```
> 
> There’s nothing following the colon above?
> 
> > 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.
> 
> I wonder if it could be <https://issues.guix.info/issue/34016>, though
> I’ve never experienced it in ~/.cache/guix, despite using ‘guix pull’ &
> co. a lot.
> 
> Next time this happens, could you run:
> 
>   strace -s 100 -o log guix package -n -m example-inferior.scm
> 
> and post the last few hundred lines of ‘log’?
> 
> Thanks,
> Ludo’.

  reply	other threads:[~2019-02-09 15:50 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 ` bug#34402: Inferior channel (I believe 'inferior-for-channels' function specifically) sometimes fails pkill9
2019-02-09 14:12   ` Ludovic Courtès
2019-02-09 15:49     ` pkill9 [this message]
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=E1gsUsP-0002Sk-JN@rmmprod07.runbox \
    --to=pkill9@runbox.com \
    --cc=34402@debbugs.gnu.org \
    --cc=ludo@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).