From: Leo Famulari <leo@famulari.name>
To: 53616@debbugs.gnu.org
Subject: bug#53616: build error k14i8vsbnihnghg9xhavs9p3yrxsa431-compute-guix-derivation
Date: Sat, 29 Jan 2022 13:36:23 -0500 [thread overview]
Message-ID: <YfWJJ3rjZ+RnYpgz@jasmine.lan> (raw)
In-Reply-To: <MuX2-_V--3-2@tuta.io>
On Fri, Jan 28, 2022 at 07:56:46PM +0100, liberty4us--- via Bug reports for GNU Guix wrote:
> Haven't pulled in almost a month. Tried and failed.
>
> Any idea what I can do besides start over?
>
> Guix told me to report it like this, so here goes:
>
> $ guix pull
[...]
> / 'build' phas-guix pull: error: You found a bug: the program '/gnu/store/k14i8vsbnihnghg9xhavs9p3yrxsa431-compute-guix-derivation'
> failed to compute the derivation for Guix (version: "a057d2acbf8d78afe474669fea29adef6aa949cc"; system: "aarch64-linux";
The log output was a bit scrambled but I see the aarch64 part.
Unfortunately, Guix hasn't built on aarch64 for a month or so:
https://ci.guix.gnu.org/search?query=spec%3Amaster+system%3Aaarch64-linux+guix-1.3.0
It would be great to get more detailed information about what goes wrong
on your system, if it's different than what we see on ci.guix.gnu.org,
for example from this build:
https://ci.guix.gnu.org/build/261637/details
Here is the bug report about Guix on aarch64:
https://issues.guix.gnu.org/52943
next prev parent reply other threads:[~2022-01-29 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 18:56 bug#53616: build error k14i8vsbnihnghg9xhavs9p3yrxsa431-compute-guix-derivation liberty4us--- via Bug reports for GNU Guix
2022-01-29 18:36 ` Leo Famulari [this message]
[not found] ` <handler.53616.B.164340037320655.ack@debbugs.gnu.org>
2022-01-30 16:15 ` bug#53616: Acknowledgement (build error k14i8vsbnihnghg9xhavs9p3yrxsa431-compute-guix-derivation) liberty4us--- via Bug reports for GNU Guix
2022-01-30 18:31 ` Leo Famulari
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=YfWJJ3rjZ+RnYpgz@jasmine.lan \
--to=leo@famulari.name \
--cc=53616@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).