From: Chris Marusich <cmmarusich@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@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: Sun, 16 Jan 2022 20:43:12 -0800 [thread overview]
Message-ID: <8735ln9dlr.fsf@gmail.com> (raw)
In-Reply-To: <871r1b1r10.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 13 Jan 2022 12:31:23 -0500")
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
Hi Maxim,
I've CC'd Mathieu on this email because he sent an email recently asking
for help with the 1.4.0 release, and Ludo because he was working on bug
52752.
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hi Maxime,
>
> Maxime Devos <maximedevos@telenet.be> writes:
>
>> Efraim Flashner schreef op di 11-01-2022 om 12:39 [+0200]:
>>> On Mon, Jan 10, 2022 at 02:57:09PM -0500, Maxim Cournoyer wrote:
>>> > If nobody has another world rebuilding change deemed necessary in time
>>> > for the release, I suggest we enable substitutes on the branch soon, and
>>> > then get busy trying to get 'make dist' to succeed so that we can issue
>>> > a first RC.
>>
>> The fix for a non-deterministic test suite failure in Guile:
>> https://issues.guix.gnu.org/48389#11
>
> That one slipped :-/. Sorry! I should have checked my emails more
> carefully before turning on the switch in Cuirass yesterday.
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
I figured we could coordinate and update the "guix" package at the right
time, all at once.
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?
--
Chris
PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-01-17 4:43 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 [this message]
2022-01-18 5:16 ` Maxim Cournoyer
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=8735ln9dlr.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--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).