From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
Mathieu Othacehe <othacehe@gnu.org>,
guix-maintainers@gnu.org
Subject: Re: version-1.4.0 branch updated
Date: Tue, 18 Jan 2022 00:16:01 -0500 [thread overview]
Message-ID: <87lezdhbe6.fsf@gmail.com> (raw)
In-Reply-To: <8735ln9dlr.fsf@gmail.com> (Chris Marusich's message of "Sun, 16 Jan 2022 20:43:12 -0800")
Hello again!
Chris Marusich <cmmarusich@gmail.com> writes:
[...]
> On aarch64-linux, on master, bug 52943 prevents the "guix" package from
> building successfully. I've committed a fix for this on the master
> branch in commit 24c3485bb3ffc05e687ef6513ac287b8d3048bab. However, I
> haven't yet updated the "guix" package, since Ludo mentioned here that
> he wanted to update the "guix" package to include a different fix (for
> bug 52752), but I'm not sure that he's done that yet:
>
> https://issues.guix.gnu.org/52752#2
It seems there may be more to fix for Guix to build on i686, according
to the above (Denis reported 3 failures in their latest attempt).
> I figured we could coordinate and update the "guix" package at the right
> time, all at once.
Sounds like a good idea!
> It would be good to ensure that the "guix" package builds successfully
> on aarch64-linux for the 1.4.0 release. Therefore, I'd like to get the
> fix for 52943 included in the version-1.4.0 branch, but I don't want to
> step on anyone's toes. What can I do to get the fix included in the
> release?
There have been many smaller integration fixes coming after the
version-1.4.0 merge of today; I guess we should recreate the
version-1.4.0 when we deem we're ready for an RC or when the need
arises.
I've deleted it now to avoid confusion, and will diffuse a message about
it on guix-devel. We can work on stabilizing master some more while
also getting the dist machinery ready.
I guess when the times come ripe for the first RC we can recreate the
release branch.
Thanks,
Maxim
next prev parent reply other threads:[~2022-01-18 5:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 19:57 version-1.4.0 branch updated Maxim Cournoyer
2022-01-10 21:36 ` Ricardo Wurmus
2022-01-11 0:31 ` Maxim Cournoyer
2022-01-11 4:48 ` Leo Famulari
2022-01-11 9:05 ` Ricardo Wurmus
2022-01-11 10:39 ` Efraim Flashner
2022-01-11 10:50 ` Maxime Devos
2022-01-13 17:31 ` Maxim Cournoyer
2022-01-17 4:43 ` Chris Marusich
2022-01-18 5:16 ` Maxim Cournoyer [this message]
2022-01-18 14:52 ` Ludovic Courtès
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=87lezdhbe6.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=othacehe@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).