GNU bug report logs - #66981
Request for merging "rust-team" branch

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 66981 in the body.
You can then email your comments to 66981 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: guix-patches <at> gnu.org
Subject: Request for merging "rust-team" branch
Date: Tue, 7 Nov 2023 10:37:38 +0200

[Message part 1 (text/plain, inline)]

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.

-- 
Efraim Flashner   <efraim <at> 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

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 66981 <at> debbugs.gnu.org (full text, mbox):

From: John Kehayias <john.kehayias <at> protonmail.com>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 66981 <at> debbugs.gnu.org
Subject: Re: bug#66981: Request for merging "rust-team" branch
Date: Wed, 15 Nov 2023 05:45:20 +0000

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!
John

Message #11 received at 66981 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: John Kehayias <john.kehayias <at> protonmail.com>
Cc: 66981 <at> debbugs.gnu.org
Subject: Re: bug#66981: Request for merging "rust-team" branch
Date: Wed, 15 Nov 2023 08:33:13 +0200

[Message part 1 (text/plain, inline)]

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 <at> 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

[signature.asc (application/pgp-signature, inline)]

Message #16 received at 66981-done <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: 66981-done <at> debbugs.gnu.org
Subject: Re: bug#66981: Acknowledgement (Request for merging "rust-team"
 branch)
Date: Wed, 13 Dec 2023 09:51:51 +0200

[Message part 1 (text/plain, inline)]

rust-team branch merged!

-- 
Efraim Flashner   <efraim <at> 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

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.