From: Efraim Flashner <efraim@flashner.co.il>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 66981@debbugs.gnu.org
Subject: [bug#66981] Request for merging "rust-team" branch
Date: Wed, 15 Nov 2023 08:33:13 +0200 [thread overview]
Message-ID: <ZVRmKbV1FSBtfafk@3900XT> (raw)
In-Reply-To: <87jzqjtvrm.fsf@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
On Wed, Nov 15, 2023 at 05:45:20AM +0000, John Kehayias wrote:
> Hi Efraim,
>
> On Tue, Nov 07, 2023 at 10:37 AM, Efraim Flashner wrote:
>
> > This patch set includes bumping rust up to 1.73.0, the current release.
> > Also rust-analyzer is absorbed into the rust package and there are many
> > updates and new crates. All of the rust packages which build and run
> > their test suites should now pass.
> >
> > I personally haven't noticed any changes in broken packages on x86_64,
> > and I made sure (locally) that rust-1.73 builds on aarch64, so I'm
> > pretty sure it's more or less ready.
>
> Just a heads up that on mesa-updates the ungrafting of libx11 (at least)
> caused a near world rebuild including rust land. I believe the link is
> python being rebuilt.
>
> So, we may want to coordinate before merging to master to make sure
> substitutes are available, especially considering the long rust compile
> chain.
>
> I just sent a message to guix-devel on the latest status, where I think
> that branch is ready to merge. But maybe we should merge either
> rust-team or mesa-updates into the other? Or just merge one to master
> and then master into the other branch with time to build?
Thanks. I replied to the thread on guix-devel.
I think we merge mesa-updates when it's ready and then I'll rebase
rust-team and merge that in shortly after, after double checking that it
still builds nicely.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-15 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 8:37 [bug#66981] Request for merging "rust-team" branch Efraim Flashner
2023-11-15 5:45 ` John Kehayias via Guix-patches via
2023-11-15 6:33 ` Efraim Flashner [this message]
[not found] ` <handler.66981.B.16993463117571.ack@debbugs.gnu.org>
2023-12-13 7:51 ` bug#66981: Acknowledgement (Request for merging "rust-team" branch) Efraim Flashner
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=ZVRmKbV1FSBtfafk@3900XT \
--to=efraim@flashner.co.il \
--cc=66981@debbugs.gnu.org \
--cc=john.kehayias@protonmail.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).