From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "(" <paren@disroot.org>,
62064-done@debbugs.gnu.org, "Jonas Møller" <jonas@moesys.no>
Subject: bug#62064: Why is only rust-1.60 exported when 1.65 is defined?
Date: Mon, 22 Jan 2024 00:02:25 -0500 [thread overview]
Message-ID: <87edea3qqm.fsf@gmail.com> (raw)
In-Reply-To: <86ilecvvsi.fsf@gmail.com> (Simon Tournier's message of "Tue, 04 Apr 2023 11:30:53 +0200")
tags 62064 + notabug
quit
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi,
>
> On Mon, 13 Mar 2023 at 21:11, paren--- via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
>
>> There's another important reason:
>>
>> rust != rust-1.60
>
> Well, as discussed in [1]
>
> [bug#62643] [PATCH] gnu: rust-1.65: Rename package to rust-next.
>
> this report #62064 is not a bug but instead a wish list: upgrade the
> Rust ecosystem. Therefore, I am in favor to close it. WDYT?
Done. We're currently at rust 1.73 on core-updates.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-01-22 5:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 16:09 bug#62064: Why is only rust-1.60 exported when 1.65 is defined? Jonas Møller via Bug reports for GNU Guix
2023-03-12 14:14 ` Matthew James Kraai
2023-03-13 13:36 ` Greg Hogan
2023-03-13 14:32 ` Simon Tournier
2023-03-13 20:59 ` Jonas Møller via Bug reports for GNU Guix
2023-03-14 8:32 ` Simon Tournier
2023-03-14 8:59 ` Jonas Møller via Bug reports for GNU Guix
2023-04-03 14:03 ` Simon Tournier
2023-04-04 11:53 ` Jonas Møller via Bug reports for GNU Guix
2023-03-13 21:11 ` paren--- via Bug reports for GNU Guix
2023-04-04 9:30 ` Simon Tournier
2024-01-22 5:02 ` Maxim Cournoyer [this message]
2023-03-24 15:41 ` ROCKTAKEY
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edea3qqm.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=62064-done@debbugs.gnu.org \
--cc=jonas@moesys.no \
--cc=paren@disroot.org \
--cc=zimon.toutoune@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.