From: Leo Famulari <leo@famulari.name>
To: Aiko Kyle <aikokyle@gmail.com>
Cc: 52943@debbugs.gnu.org
Subject: bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64
Date: Sat, 1 Jan 2022 21:13:54 -0500 [thread overview]
Message-ID: <YdEKYg2eDo2b7b6h@jasmine.lan> (raw)
In-Reply-To: <CAPWcbYHjBoqd0vsLOknF7Yk86wUiC5P_ppTguv8G=fziJ=FJeQ@mail.gmail.com>
On Sat, Jan 01, 2022 at 04:54:51PM -0700, Aiko Kyle wrote:
> I'm new to guix so I'm really struggling to debug this strange issue.
> On the latest master I can run 'guix pull', and the latest guix seems
> to build just fine, however when I go to do 'guix system reconfigure',
> building guix fails the check phase. I've attached the log file. After
> some help on IRC, I understand that during 'guix system reconfigure'
> ends up building a previous version of itself via the "boot-stripping"
> process in gnu/packages/package-management.scm. I followed this linked
> list of commits backwards and found that commits prior to commit
> 224d437fb4 which updates this guix package definition to version 14
> which is commit 2a621f1 build just fine, however all the versions of
> that package afterwards fail at the same place during 'guix system
> reconfigure', in the check phase, with the same tests failing. At this
> point, I think I lack sufficient knowledge of guix to debug this issue
> further and it looks like cuirass is so backlogged on aarch64 that is
> still hasn't gotten to building these guix versions so I can't compare
> with it's build attempts. Any help would be greatly appreciated as I'd
> really like to be running the latest guix from master.
Thanks, this has already been reported as
<https://issues.guix.gnu.org/52908>
next prev parent reply other threads:[~2022-01-02 2:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 23:54 bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64 Aiko Kyle
2022-01-02 2:13 ` Leo Famulari [this message]
2022-01-02 4:11 ` Aiko Kyle
2022-01-02 4:51 ` Leo Famulari
2022-01-02 6:36 ` Aiko Kyle
2022-01-03 21:38 ` Akira Kyle
2022-01-04 1:13 ` Akira Kyle
2022-01-04 1:16 ` Akira Kyle
2022-01-09 4:39 ` Chris Marusich
2022-01-15 13:27 ` Pierre Langlois
2022-01-16 1:00 ` Chris Marusich
2022-01-17 4:46 ` Chris Marusich
2022-01-17 18:51 ` Pierre Langlois
2022-01-18 5:33 ` Vagrant Cascadian
2022-01-19 19:28 ` Vagrant Cascadian
2022-01-29 18:33 ` Leo Famulari
2022-01-29 20:54 ` Pierre Langlois
2022-01-29 21:06 ` Leo Famulari
2022-01-29 21:35 ` Pierre Langlois
2022-10-07 8:48 ` Christopher Baines
2022-10-20 14:57 ` Mathieu Othacehe
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=YdEKYg2eDo2b7b6h@jasmine.lan \
--to=leo@famulari.name \
--cc=52943@debbugs.gnu.org \
--cc=aikokyle@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).