From: g4s8 <g4s8@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] go: update to 1.19.3.
Date: Wed, 02 Nov 2022 14:06:55 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40299@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
There is a new pull request by g4s8 against master on the void-packages repository
https://github.com/g4s8/void-packages go-1.19.3
https://github.com/void-linux/void-packages/pull/40299
go: update to 1.19.3.
#### 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)
Go 1.19.3 contains security fixes:
> go1.19.3 (released 2022-11-01) includes security fixes to the os/exec and syscall packages, as well as bug fixes to the compiler and the runtime. See the [Go 1.19.3 milestone](https://github.com/golang/go/issues?q=milestone%3AGo1.19.3+label%3ACherryPickApproved) on our issue tracker for details.
https://go.dev/doc/devel/release
A patch file from https://github.com/void-linux/void-packages/pull/40299.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-go-1.19.3-40299.patch --]
[-- Type: text/x-diff, Size: 909 bytes --]
From 56fbe0ae842b2de0f0f981298fa1667b544bd624 Mon Sep 17 00:00:00 2001
From: Kirill <g4s8.public@gmail.com>
Date: Wed, 2 Nov 2022 15:59:58 +0300
Subject: [PATCH] go: update to 1.19.3.
---
srcpkgs/go/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/go/template b/srcpkgs/go/template
index 4fa13d28f6d1..460bee0fcdea 100644
--- a/srcpkgs/go/template
+++ b/srcpkgs/go/template
@@ -1,6 +1,6 @@
# Template file for 'go'
pkgname=go
-version=1.19.2
+version=1.19.3
revision=1
create_wrksrc=yes
build_wrksrc=go
@@ -12,7 +12,7 @@ license="BSD-3-Clause"
homepage="https://go.dev/"
changelog="https://go.dev/doc/devel/release.html"
distfiles="https://go.dev/dl/go${version}.src.tar.gz"
-checksum=2ce930d70a931de660fdaf271d70192793b1b240272645bf0275779f6704df6b
+checksum=18ac263e39210bcf68d85f4370e97fb1734166995a1f63fb38b4f6e07d90d212
nostrip=yes
noverifyrdeps=yes
next reply other threads:[~2022-11-02 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 13:06 g4s8 [this message]
2023-02-01 2:07 ` github-actions
2023-02-01 7:26 ` paper42
2023-02-01 7:26 ` [PR PATCH] [Closed]: " paper42
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-40299@inbox.vuxu.org \
--to=g4s8@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).