Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 07 Dec 2023 02:28:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        go@FreeBSD.org
Subject:   [Bug 274405] lang/go121 lang/go120: Update golang ports to 1.20.10 and 1.21.3
Message-ID:  <bug-274405-42334-n79GYBe51j@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-274405-42334@https.bugs.freebsd.org/bugzilla/>
References:  <bug-274405-42334@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274405

Ashish SHUKLA <ashish@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|go@FreeBSD.org              |ashish@FreeBSD.org

--- Comment #9 from Ashish SHUKLA <ashish@FreeBSD.org> ---
Hi Adam =E2=80=93

Since the lang/go* updates also contain security fixes, I think we should do
the cherry-pick of 0505b712df3ae2b4bcaba00aecc7c1e9100d8609 to the 2023Q4, =
but
apparently this doesn't cleanly apply to 2023Q4 branch (around ~140 merge
conflicts).

Should I just bump PORTREVISION similar to what is done in main branch, ins=
tead
of cherry-picking, so that lang/go* consumers get the security fixes, or th=
ere
is a better option ?

Thanks!

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274405-42334-n79GYBe51j>