From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] rust-analyzer: update to 2023.12.04.
Date: Tue, 12 Dec 2023 08:01:37 +0100 [thread overview]
Message-ID: <20231212070137.aD5wBXVvNgWitsswgET6B_Lo7IDhfVsNtuVJIuh_t0g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47623@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
There is an updated pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages rust-analyzer
https://github.com/void-linux/void-packages/pull/47623
rust-analyzer: update to 2023.12.04.
#### 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**
A patch file from https://github.com/void-linux/void-packages/pull/47623.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rust-analyzer-47623.patch --]
[-- Type: text/x-diff, Size: 1073 bytes --]
From 59c969c1276691cee99ee0cf03cb766789b8841f Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Tue, 5 Dec 2023 20:58:04 +0530
Subject: [PATCH] rust-analyzer: update to 2023.12.11.
---
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 365521e0aa8a6..fbd3f7dc2c106 100644
--- a/srcpkgs/rust-analyzer/template
+++ b/srcpkgs/rust-analyzer/template
@@ -1,6 +1,6 @@
# Template file for 'rust-analyzer'
pkgname=rust-analyzer
-version=2023.11.27
+version=2023.12.11
revision=1
_ver=${version//./-}
build_style=cargo
@@ -10,7 +10,7 @@ maintainer="icp <pangolin@vivaldi.net>"
license="Apache-2.0, MIT"
homepage="https://rust-analyzer.github.io/"
distfiles="https://github.com/rust-lang/rust-analyzer/archive/refs/tags/${_ver}.tar.gz"
-checksum=7cd219a2830d22e15e43b7764352ab622960fe7450ebc84e8f6e250d324f268e
+checksum=1c7185c04da12c838198cd304e09cd0f2d9af85f973c1be2a8100c9042547c28
# tests require Rust source code
make_check=no
next prev parent reply other threads:[~2023-12-12 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 19:17 [PR PATCH] " icp1994
2023-12-12 7:01 ` icp1994 [this message]
2023-12-19 9:06 ` [PR PATCH] [Updated] rust-analyzer: update to 2023.12.11 icp1994
2023-12-22 23:30 ` [PR PATCH] [Merged]: rust-analyzer: update to 2023.12.18 Duncaen
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=20231212070137.aD5wBXVvNgWitsswgET6B_Lo7IDhfVsNtuVJIuh_t0g@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).