From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [TRACKING] Updates blocked on Rust 1.65.0
Date: Sun, 27 Nov 2022 20:04:19 +0100 [thread overview]
Message-ID: <20221127190419.9622waI5-RZWKzAo2nkt5yQ_rrXNSRxdtU7BEYq0CSs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40805@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
New comment by icp1994 on void-packages repository
https://github.com/void-linux/void-packages/issues/40805#issuecomment-1328318246
Comment:
From the 1.64 [release blog](https://blog.rust-lang.org/2022/09/22/Rust-1.64.0.html#rust-analyzer-is-now-available-via-rustup)
> At this time, to run the rustup-installed version, you need to invoke it this way: `rustup run stable rust-analyzer`
The next release of rustup will provide a built-in proxy so that running the executable `rust-analyzer` will launch the appropriate version.
> Most users should continue to use the releases provided by the rust-analyzer team (available on the [rust-analyzer releases page](https://github.com/rust-lang/rust-analyzer/releases)), which are published more frequently
Not exactly sure what should be done regarding the RA package after the next rustup update but okay maybe it can left from the list for now.
next prev parent reply other threads:[~2022-11-27 19:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 16:57 [ISSUE] " jcgruenhage
2022-11-27 18:46 ` icp1994
2022-11-27 18:50 ` jcgruenhage
2022-11-27 19:04 ` icp1994 [this message]
2022-11-27 19:08 ` jcgruenhage
2022-11-27 19:11 ` 0x5c
2022-11-30 5:44 ` icp1994
2022-12-13 6:16 ` icp1994
2023-01-02 4:13 ` cinerea0
2023-01-02 15:55 ` leahneukirchen
2023-01-04 0:12 ` cinerea0
2023-01-08 0:06 ` tranzystorek-io
2023-01-15 3:28 ` cinerea0
2023-01-15 15:55 ` tranzystorek-io
2023-02-15 19:27 ` tranzystorek-io
2023-02-15 19:27 ` tranzystorek-io
2023-02-17 17:41 ` classabbyamp
2023-02-24 19:25 ` cinerea0
2023-02-26 21:46 ` tranzystorek-io
2023-02-26 21:50 ` tranzystorek-io
2023-02-26 21:50 ` tranzystorek-io
2023-02-28 15:06 ` cinerea0
2023-03-12 3:07 ` classabbyamp
2023-03-14 14:31 ` tranzystorek-io
2023-03-15 16:10 ` icp1994
2023-03-22 13:36 ` leahneukirchen
2023-03-26 20:11 ` TinfoilSubmarine
2023-03-30 14:25 ` lukas-jo
2023-03-30 14:26 ` lukas-jo
2023-03-31 9:14 ` tranzystorek-io
2023-04-02 8:39 ` classabbyamp
2023-04-16 16:42 ` [ISSUE] [CLOSED] " classabbyamp
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=20221127190419.9622waI5-RZWKzAo2nkt5yQ_rrXNSRxdtU7BEYq0CSs@z \
--to=icp1994@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).