From: Vagrant Cascadian <vagrant@debian.org>
To: Pierre Langlois <pierre.langlois@gmx.com>,
Chris Marusich <cmmarusich@gmail.com>
Cc: Aiko Kyle <aikokyle@gmail.com>, 52943@debbugs.gnu.org
Subject: bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64
Date: Mon, 17 Jan 2022 21:33:01 -0800 [thread overview]
Message-ID: <87bl09d2wi.fsf@yucca> (raw)
In-Reply-To: <878rvefb54.fsf@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
On 2022-01-17, Pierre Langlois wrote:
> Chris Marusich <cmmarusich@gmail.com> writes:
>> Chris Marusich <cmmarusich@gmail.com> writes:
>>> If nobody has further comments, I will commit the attached version to
>>> master in about 24 hours.
>>
>> I've committed this in 24c3485bb3ffc05e687ef6513ac287b8d3048bab. We
>> still need to update the "guix" package, so even if you run "guix pull"
>> right now, you won't be able to successfully build "guix" after pulling
>> on aarch64-linux yet.
>>
>> I will coordinate with the other people who are helping to make the
>> 1.4.0 release to ensure that this fix makes it into the 1.4.0 release.
>> See this guix-devel email thread for details:
>>
>> https://lists.gnu.org/archive/html/guix-devel/2022-01/msg00296.html
>
> That's awesome, thank you!
FWIW, I can also confirm that updating the "guix" package to a version
that contains 24c3485bb3ffc05e687ef6513ac287b8d3048bab allows the "guix"
package (which contains the fairly important "guix-daemon"), to build
again. Thanks for getting it that far!
Haven't been able to upgrade my aarch64 systems without local patches
for over a month now... glad to see a fix is *almost* ready!
Is there anything in particular holding back upating the guix package
(other than the huge amount of big merges in progress, release
preparation, etc. and etc.)?
Thanks everyone!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-01-18 5:34 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
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 [this message]
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=87bl09d2wi.fsf@yucca \
--to=vagrant@debian.org \
--cc=52943@debbugs.gnu.org \
--cc=aikokyle@gmail.com \
--cc=cmmarusich@gmail.com \
--cc=pierre.langlois@gmx.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).