From: Vagrant Cascadian <vagrant@debian.org>
To: "Leo Famulari" <leo@famulari.name>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 53214@debbugs.gnu.org
Subject: bug#53214: Release 1.4.0 progress
Date: Sat, 29 Jan 2022 16:22:21 -0800 [thread overview]
Message-ID: <87y22yqdhe.fsf@ponder> (raw)
In-Reply-To: <YfWtfbOcLXrPBhRe@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On 2022-01-29, Leo Famulari wrote:
> The build farm is having trouble building Guix for i686-linux. In fact,
> it hasn't successfully completed the 'guix' job in weeks:
>
> https://issues.guix.gnu.org/53463
>
> And building the guix package does not work on aarch64, also for weeks:
>
> https://issues.guix.gnu.org/52943
It does work on my aarch64 machine as of
1ef7a03a148cf5f83ab1820444f6bd50d8e732d1 and more recently
f8bfb2d85682dcabe56a4b1b0f25d566a0abbd2b, but not sure why it's not
building on the build farm...
> Finally, should we consider retiring the armhf port in 1.4.0? It seems
> that we have stopped trying to build for it:
>
> https://ci.guix.gnu.org/search?query=guix+spec%3Amaster+system%3Aarmhf-linux
In a similar vein, aarch64 substitutes are in pretty bad shape... and
the architecture as a whole is a bit hard to keep up with; there are
some pretty obscure and difficult to triage bugs here and there.
I'm not sure what the qualities of a release-worthy architecture are,
but aarch64 is definitely suffering badly ever since the core-updates
merge and the merge of the 1.4 branch into master, which required a lot
of rebuilds...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-01-30 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 17:32 bug#53214: Release 1.4.0 progress Ludovic Courtès
2022-01-26 4:20 ` Leo Famulari
2022-01-29 21:11 ` Leo Famulari
2022-01-30 0:22 ` Vagrant Cascadian [this message]
2022-01-30 1:00 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2022-02-01 8:34 ` Ludovic Courtès
2022-02-03 17:46 ` 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=87y22yqdhe.fsf@ponder \
--to=vagrant@debian.org \
--cc=53214@debbugs.gnu.org \
--cc=leo@famulari.name \
--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).