unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: 范啟能 <fankainang@gmail.com>
Cc: 59072@debbugs.gnu.org
Subject: bug#59072: guix pull bug report
Date: Fri, 09 Dec 2022 19:56:19 +0100	[thread overview]
Message-ID: <87h6y4pfsc.fsf@gmail.com> (raw)
In-Reply-To: <CAFQ48hSuvQuUBBo+a_0Kr359pkasa=qe=9peQ-ioZ=JK89ArSw@mail.gmail.com> ("范啟能"'s message of "Sun, 6 Nov 2022 12:30:38 +0800")

Hi,

On Sun, 06 Nov 2022 at 12:30, 范啟能 <fankainang@gmail.com> wrote:

>  -Backtrace:
>            18 (primitive-load "/gnu/store/izm5wcncfddbm2a7a05jj50jn43wrfnp-compute-guix-derivation")
>  In ice-9/eval.scm:
>      155:9 17 (_ _)
>      159:9 16 (_ #(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#<directory (guile-u?> ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
>  In ice-9/boot-9.scm:
>      152:2 15 (with-fluid* _ _ _)
>      152:2 14 (with-fluid* _ _ _)
>  In ./guix/store.scm:
>    2170:24 13 (run-with-store #<store-connection 256.99 7f0e35469140> #<procedure 7f0e1e4da050 at ./guix/self.scm:12?>
>     1998:8 12 (_ #<store-connection 256.99 7f0e35469140>)
>  In ./guix/gexp.scm:
>     299:22 11 (_ #<store-connection 256.99 7f0e35469140>)
>     1180:2 10 (_ #<store-connection 256.99 7f0e1cd088c0>)
>     1046:2  9 (_ #<store-connection 256.99 7f0e1cd088c0>)
>      892:4  8 (_ #<store-connection 256.99 7f0e1cd088c0>)
>  In ./guix/store.scm:
>    2055:12  7 (_ #<store-connection 256.99 7f0e1cd088c0>)
>    1407:13  6 (map/accumulate-builds #<store-connection 256.99 7f0e1cd088c0> #<procedure 7f0e29febd80 at ./guix/stor?>
>     1403:5  5 (map/accumulate-builds #<store-connection 256.99 7f0e1cd088c0> #<procedure 7f0e1a24b1e0 at ./guix/stor?>
>    1419:15  4 (_ #<store-connection 256.99 7f0e1cd088c0> ("/gnu/store/j48v18vdw9zmgp2grdk5xdkylh8zzy2l-guile-ssh-?" ?) ?)
>    1419:15  3 (loop #f)
>     713:11  2 (process-stderr #<store-connection 256.99 7f0e1cd088c0> _)
>  In ./guix/serialization.scm:
>     102:11  1 (read-int #<input-output: file 10>)
>       80:6  0 (get-bytevector-n* #<input-output: file 10> 8)
>  ./guix/serialization.scm:80:6: In procedure get-bytevector-n*:
>  ERROR:
>    1. &nar-error:
>        file: #f
>        port: #<input-output: file 10>
>  guix pull: error: You found a bug: the program '/gnu/store/izm5wcncfddbm2a7a05jj50jn43wrfnp-compute-guix-derivation'
>  failed to compute the derivation for Guix (version: "a6c90c293d5b0c77d3e1e967546fe0aadc53a102"; system: "x86_64-linux";
>  host version: "92769ab2828b53ce41200e8beb8789a12863ee53"; pull-version: 1).
>  Please report the COMPLETE output above by email to <bug-guix@gnu.org>.

Do you still have the issue?

Cheers,
simon




      reply	other threads:[~2022-12-09 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06  4:30 bug#59072: guix pull bug report 范啟能
2022-12-09 18:56 ` zimoun [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=87h6y4pfsc.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=59072@debbugs.gnu.org \
    --cc=fankainang@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).