From: elaexuotee--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41822@debbugs.gnu.org
Subject: bug#41822: Bug in compute-guix-derivation?
Date: Fri, 19 Jun 2020 13:14:52 +0900 [thread overview]
Message-ID: <24PIL3YFUQD7B.3L2Z9N4CFM4QB@wilsonb.com> (raw)
In-Reply-To: <87pn9xrj64.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1187 bytes --]
Thank you, Ludo.
I am having trouble reproducing the error for some reason now. For a few days
guix pull invariable died in this way, but now it's getting past that point and
failing in a completely new way on SIGPIPE.
I will try to come back with something more useful.
Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> elaexuotee@wilsonb.com skribis:
>
> > Not exactly sure what to report, but:
> >
> > $ guix pull
> > Building from this channel:
> > guix https://git.savannah.gnu.org/git/guix.git 9c6ea3c
> > Computing Guix derivation for 'x86_64-linux'... \guix pull: error: You found a bug: the program '/gnu/store/94yr3a44i33635b90lhbji5rixkyijvg-compute-guix-derivation'
> > failed to compute the derivation for Guix (version: "9c6ea3cb5617a1928073f41f174765ab14adbaa9"; system: "x86_64-linux";
> > host version: "2971ed57345ee4e00058efeaf27c6a0790fdc9dd"; pull-version: 1).
> > Please report it by email to <bug-guix@gnu.org>.
>
> Could you run “strace -f -o log guix pull” to see if it’s the same issue
> (SIGBUS) that was reported at <https://issues.guix.gnu.org/41715#9>?
>
> Thanks,
> Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2020-06-19 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 0:30 bug#41822: Bug in compute-guix-derivation? elaexuotee--- via Bug reports for GNU Guix
2020-06-17 12:06 ` Ludovic Courtès
2020-06-19 4:14 ` elaexuotee--- via Bug reports for GNU Guix [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=24PIL3YFUQD7B.3L2Z9N4CFM4QB@wilsonb.com \
--to=bug-guix@gnu.org \
--cc=41822@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.com \
--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).