bug#62064: closed (Why is only rust-1.60 exported when 1.65 is defined?)

[GNU bug Tracking System]

Your message dated Mon, 22 Jan 2024 00:02:25 -0500
with message-id <87edea3qqm.fsf@gmail.com>
and subject line Re: bug#62064: Why is only rust-1.60 exported when 1.65 is 
defined?
has caused the debbugs.gnu.org bug report #62064,
regarding Why is only rust-1.60 exported when 1.65 is defined?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
62064: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62064
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: Why is only rust-1.60 exported when 1.65 is defined? Date: Wed, 08 Mar 2023 16:09:32 +0000

Hi Guix! The rust.scm file says

;;; Note: Only the latest versions of Rust are supported and tested.  The
;;; intermediate rusts are built for bootstrapping purposes and should not
;;; be relied upon.  This is to ease maintenance and reduce the time
;;; required to build the full Rust bootstrap chain.
;;;
;;; Here we take the latest included Rust, make it public, and re-enable tests
;;; and extra components such as rustfmt.

And then proceeds to define-public rust as rust-1.60, and I was wondering if there's any particular reason why a year-old version is used rather than the 1.65 version. This seems like a mistake, given that the comment claims that the "latest included Rust" should be made public.

This is especially troublesome for Rust on Guix because of both how fast its ecosystem moves onto new language/tooling features, and because using rustup (the solution for this on other slow-moving distros) relies on pre-built executables that don't work out-of-the-box on Guix.

— Mvh Jonas Møller

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#62064: Why is only rust-1.60 exported when 1.65 is defined?
>
>
>
>
> Date: 
>
> Mon, 22 Jan 2024 00:02:25 -0500
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13)
>
>
>
>
> 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
>
>
> --- End Message ---