unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Nathan Dehnel <ncdehnel@gmail.com>
Cc: 47578-done@debbugs.gnu.org
Subject: bug#47578: bug found running guix pull
Date: Sat, 3 Apr 2021 19:15:52 -0400	[thread overview]
Message-ID: <YGj3KN6GrsLbdkSW@jasmine.lan> (raw)
In-Reply-To: <CAEEhgEs=a9CgMD291oR_YRESodnBV44QaY1=tVggpGbDNm4UNA@mail.gmail.com>

Okay, glad to hear it, and thank you for reporting it!  

I'm closing this bug now but please send another message if the problem
happens again while running the new guix-daemon.

On Sat, Apr 03, 2021 at 03:16:59PM -0500, Nathan Dehnel wrote:
> Yes, it worked after several tries.
> 
> On Sat, Apr 3, 2021, 12:19 PM Leo Famulari <leo@famulari.name> wrote:
> 
> > On Sat, Apr 03, 2021 at 12:41:10AM -0500, Nathan Dehnel wrote:
> > > ERROR:
> > >   1. &nar-error:
> > >       file: #f
> > >       port: #<input-output: file 10>
> > > guix pull: error: You found a bug: the program
> > > '/gnu/store/w6596kfg55g578dvwaayfj7alq7g88j0-compute-guix-derivation'
> > > failed to compute the derivation for Guix (version:
> > > "86c39376cc00ed19758a2861c11f85fa5b94cda4"; system: "x86_64-linux";
> > > host version: "d4987a50cef3983c4bd68c1c2c52270946c4f113"; pull-version:
> > 1).
> > > Please report it by email to <bug-guix@gnu.org>.
> >
> > I'm not sure, but I think it's a case of <https://bugs.gnu.org/47157>.
> >
> > If it is, it's a networking problem that occurs when updating Guix... so
> > the solution is to keep trying until `guix pull` and then restart
> > guix-daemon. Let us know how it goes!
> >




      reply	other threads:[~2021-04-03 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  5:41 bug#47578: bug found running guix pull Nathan Dehnel
2021-04-03 17:19 ` Leo Famulari
2021-04-03 20:16   ` Nathan Dehnel
2021-04-03 23:15     ` Leo Famulari [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=YGj3KN6GrsLbdkSW@jasmine.lan \
    --to=leo@famulari.name \
    --cc=47578-done@debbugs.gnu.org \
    --cc=ncdehnel@gmail.com \
    /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).