From: TeddyDD <TeddyDD@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gopls: update to 0.12.2.
Date: Sun, 04 Jun 2023 16:52:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44258@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
There is a new pull request by TeddyDD against master on the void-packages repository
https://github.com/TeddyDD/void-packages-1 update-gopls
https://github.com/void-linux/void-packages/pull/44258
gopls: update to 0.12.2.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/44258.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-gopls-44258.patch --]
[-- Type: text/x-diff, Size: 1068 bytes --]
From 423284c2195fd7548de3e9a2005adf326aa61d1f Mon Sep 17 00:00:00 2001
From: Daniel Lewan <vision360.daniel@gmail.com>
Date: Sun, 4 Jun 2023 16:52:22 +0200
Subject: [PATCH] gopls: update to 0.12.2.
---
srcpkgs/gopls/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/gopls/template b/srcpkgs/gopls/template
index 16491e5febc4..10c1c392aa97 100644
--- a/srcpkgs/gopls/template
+++ b/srcpkgs/gopls/template
@@ -1,7 +1,7 @@
# Template file for 'gopls'
pkgname=gopls
-version=0.11.0
-revision=2
+version=0.12.2
+revision=1
build_wrksrc=gopls
build_style=go
go_import_path=golang.org/x/tools/gopls
@@ -10,7 +10,7 @@ maintainer="Renato Aguiar <renato@renatoaguiar.net>"
license="MIT"
homepage="https://github.com/golang/tools/tree/master/gopls"
distfiles="https://github.com/golang/tools/archive/refs/tags/gopls/v${version}.tar.gz"
-checksum=b5dd0040bcc75b4760eb543826b6503a163c835c90f50843e626a112ca083931
+checksum=f185a44f46fe39688493008d47debfe63ea7cd26464f522df292c62539b8ca8d
post_install() {
vlicense ../LICENSE
next reply other threads:[~2023-06-04 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 14:52 TeddyDD [this message]
2023-06-04 16:56 ` [PR REVIEW] " mhmdanas
2023-06-04 19:55 ` [PR PATCH] [Updated] " TeddyDD
2023-06-04 19:56 ` [PR REVIEW] " TeddyDD
2023-06-05 17:27 ` mhmdanas
2023-06-08 23:00 ` [PR PATCH] [Merged]: " 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-44258@inbox.vuxu.org \
--to=teddydd@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).