From: Efraim Flashner <efraim@flashner.co.il>
To: Ian Eure <ian@retrospec.tv>
Cc: guix-devel@gnu.org
Subject: Re: Rust-team branch status?
Date: Fri, 21 Jun 2024 16:18:16 +0300 [thread overview]
Message-ID: <ZnV9mGtyPVAHG3jM@3900XT> (raw)
In-Reply-To: <A143F2A8-2769-4C9F-A401-41901F07FB3D@retrospec.tv>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
On Thu, Jun 20, 2024 at 05:10:11PM -0700, Ian Eure wrote:
> Hi Guixers,
>
> I want to update the Librewolf package, but it now depends on Rust >= 1.76, which is newer than what's in master. I see the rust-team branch has versions up to 1.77 — is there a timeline for merging that, or a TODO list of things that need to be done to merge it? I'm not sure if I can help there, but would rather direct efforts towards getting rust updated than patching Librewolf to build with older versions.
I managed to burn myself out on rust stuff a few months ago and I'm
finally coming back to the rust-team branch. There are still hundreds
of patches sent for the branch which I had hoped to catch-up on, but I'm
fairly certain that the branch is in a good state for merging even now.
Currently it has rust-1.77.1. There is a newer 1.77.2 available, and
the newest version is 1.79. After merging the current branch I hope to
be able to move the version of rust on the rust-team branch to whatever
the latest version is.
--
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:[~2024-06-21 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 0:10 Rust-team branch status? Ian Eure
2024-06-21 13:18 ` Efraim Flashner [this message]
2024-06-21 13:46 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-25 15:48 ` Ian Eure
2024-06-26 7:46 ` Efraim Flashner
2024-06-26 14:09 ` Efraim Flashner
2024-06-26 17:21 ` Ian Eure
2024-06-27 12:50 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-27 13:09 ` Tomas Volf
2024-06-27 13:47 ` 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=ZnV9mGtyPVAHG3jM@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
/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).