From: tjkirch <tjkirch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rust-analyzer: update to 2022.01.03.
Date: Tue, 04 Jan 2022 23:31:29 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34856@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
There is a new pull request by tjkirch against master on the void-packages repository
https://github.com/tjkirch/void-packages rust-analyzer
https://github.com/void-linux/void-packages/pull/34856
rust-analyzer: update to 2022.01.03.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86-64 glibc
---
Now that Rust 1.57 is merged, we can update rust-analyzer, which since October 21 has required the 2021 edition (introduced in Rust 1.56).
A patch file from https://github.com/void-linux/void-packages/pull/34856.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rust-analyzer-34856.patch --]
[-- Type: text/x-diff, Size: 1082 bytes --]
From 4248586073152e00fcf7786890d99e5d9bd4f819 Mon Sep 17 00:00:00 2001
From: Tom Kirchner <git@halffull.org>
Date: Fri, 10 Dec 2021 21:17:45 -0800
Subject: [PATCH] rust-analyzer: update to 2022.01.03.
---
srcpkgs/rust-analyzer/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/rust-analyzer/template b/srcpkgs/rust-analyzer/template
index b41a84aab5ea..e099edbbec24 100644
--- a/srcpkgs/rust-analyzer/template
+++ b/srcpkgs/rust-analyzer/template
@@ -1,6 +1,6 @@
# Template file for 'rust-analyzer'
pkgname=rust-analyzer
-version=2021.08.30
+version=2022.01.03
revision=1
_ver=${version//./-}
wrksrc="${pkgname}-${_ver}"
@@ -11,7 +11,7 @@ maintainer="Gabriel Sanches <gabriel@gsr.dev>"
license="Apache-2.0, MIT"
homepage="https://rust-analyzer.github.io/"
distfiles="https://github.com/${pkgname}/${pkgname}/archive/${_ver}.tar.gz"
-checksum=a5c791cd660b46e8fc20c1b268cb25c33658fcd593d81b278c34c97efccddbde
+checksum=3595986c9a988c3eaaa303fdcea6b2100de8467e13863a725d8f9fd463534ce0
# tests require Rust source code
make_check=no
next reply other threads:[~2022-01-04 22:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 22:31 tjkirch [this message]
2022-01-05 18:40 ` tjkirch
2022-01-05 19:03 ` ericonr
2022-01-05 19:22 ` tjkirch
2022-01-05 19:23 ` ericonr
2022-01-05 19:23 ` ericonr
2022-01-17 19:42 ` tjkirch
2022-01-17 23:56 ` ericonr
2022-01-18 0:04 ` tjkirch
2022-02-27 12:13 ` tranzystorek-io
2022-02-27 19:01 ` tjkirch
2022-04-05 2:32 ` Goorzhel
2022-06-15 21:18 ` classabbyamp
2022-06-15 21:18 ` [PR PATCH] [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34856@inbox.vuxu.org \
--to=tjkirch@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).