Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org, Thomas Perale <thomas.perale@mind.be>,
	Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH] package/go: security bump to version 1.23.6
Date: Wed, 5 Feb 2025 12:50:06 +0100	[thread overview]
Message-ID: <20250205125006.7622ba97@windsurf> (raw)
In-Reply-To: <20250205101246.8430-1-peter@korsgaard.com>

On Wed,  5 Feb 2025 11:12:45 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:

> go1.23.6 (released 2025-02-04) includes security fixes to the
> crypto/elliptic package, as well as bug fixes to the compiler and the go
> command.
> 
> https://go.dev/doc/devel/release#go1.23.6
> https://github.com/golang/go/issues?q=milestone%3AGo1.23.6+label%3ACherryPickApproved
> 
> While we are at it, drop the unused source tarball hash from the go-bin
> package.
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  package/go/go-bin/go-bin.hash | 13 ++++++-------
>  package/go/go-src/go-src.hash |  2 +-
>  package/go/go.mk              |  2 +-
>  3 files changed, 8 insertions(+), 9 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-02-05 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 10:12 [Buildroot] [PATCH] package/go: security bump to version 1.23.6 Peter Korsgaard
2025-02-05 11:50 ` Thomas Petazzoni via buildroot [this message]

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=20250205125006.7622ba97@windsurf \
    --to=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=peter@korsgaard.com \
    --cc=thomas.perale@mind.be \
    --cc=thomas.petazzoni@bootlin.com \
    /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