Github messages for voidlinux
 help / color / mirror / Atom feed
From: g4s8 <g4s8@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] go: update to 1.20.4.
Date: Tue, 16 May 2023 09:05:25 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43895@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

There is a new pull request by g4s8 against master on the void-packages repository

https://github.com/g4s8/void-packages go-1.20.4
https://github.com/void-linux/void-packages/pull/43895

go: update to 1.20.4.
#### 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

This version update has 3 security fixes for go:
 - https://github.com/golang/go/issues/59720 - CVE-2023-24539
 - https://github.com/golang/go/issues/59721 - CVE-2023-24540
 - https://github.com/golang/go/issues/59722 - CVE-2023-29400

A patch file from https://github.com/void-linux/void-packages/pull/43895.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-go-1.20.4-43895.patch --]
[-- Type: text/x-diff, Size: 982 bytes --]

From e9b3c8095532405ce5f85c3d9e5059333ec08fc1 Mon Sep 17 00:00:00 2001
From: Kirill <g4s8.public@gmail.com>
Date: Tue, 16 May 2023 10:59:54 +0400
Subject: [PATCH] go: update to 1.20.4.

---
 srcpkgs/go/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/go/template b/srcpkgs/go/template
index df491a31e18d..18ee1751f2f9 100644
--- a/srcpkgs/go/template
+++ b/srcpkgs/go/template
@@ -1,6 +1,6 @@
 # Template file for 'go'
 pkgname=go
-version=1.20.3
+version=1.20.4
 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=e447b498cde50215c4f7619e5124b0fc4e25fb5d16ea47271c47f278e7aa763a
+checksum=9f34ace128764b7a3a4b238b805856cc1b2184304df9e5690825b0710f4202d6
 nostrip=yes
 noverifyrdeps=yes
 # on CI it tries to use `git submodule`, which is not part of chroot-git

             reply	other threads:[~2023-05-16  7:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  7:05 g4s8 [this message]
2023-05-16  7:30 ` g4s8
2023-06-04 10:38 ` [PR PATCH] [Merged]: " paper42
2023-06-04 10:39 ` paper42
2023-06-04 10:39 ` 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-43895@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).