Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Christian Stewart <christian@aperture.us>
Cc: Tian Yuanhao <tianyuanhao3@163.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/2] package/docker-engine: bump version to v25.0.3
Date: Wed, 07 Feb 2024 09:58:20 +0100	[thread overview]
Message-ID: <87ttmk1wib.fsf@48ers.dk> (raw)
In-Reply-To: <20240207022157.2560531-1-christian@aperture.us> (Christian Stewart's message of "Tue, 6 Feb 2024 18:21:56 -0800")

>>>>> "Christian" == Christian Stewart <christian@aperture.us> writes:

 > https://github.com/moby/moby/releases/tag/v25.0.3

This is also a security bump. In fact, it would be nicer to first bump
to 24.0.9 which could then be backported to 2023.02.x and 2023.11.x and
then afterwards bump to 25.0.3.

I see the buildkit issues are not fixed in 24.0.9, but I guess it is
unlikely that we have Buildroot based systems BUILDING containers, so
that is probably less critical.

Care to rework it as two bumps?


> Signed-off-by: Christian Stewart <christian@aperture.us>
 > ---
 >  package/docker-engine/docker-engine.hash | 2 +-
 >  package/docker-engine/docker-engine.mk   | 2 +-
 >  2 files changed, 2 insertions(+), 2 deletions(-)

 > diff --git a/package/docker-engine/docker-engine.hash b/package/docker-engine/docker-engine.hash
 > index 931d6529e1..40293be7e0 100644
 > --- a/package/docker-engine/docker-engine.hash
 > +++ b/package/docker-engine/docker-engine.hash
 > @@ -1,3 +1,3 @@
 >  # Locally calculated
 > -sha256  16a2cb4cf4d314a070085e0df06e3a6bd9ec678d28715b64060af694fc9051d5  docker-engine-24.0.7.tar.gz
 > +sha256  4cdb516f5d6f5caf8b3bcf93c2962277ba727cfd2d1620176a3bb0cf153b3590  docker-engine-25.0.3.tar.gz
 >  sha256  7c87873291f289713ac5df48b1f2010eb6963752bbd6b530416ab99fc37914a8  LICENSE
 > diff --git a/package/docker-engine/docker-engine.mk b/package/docker-engine/docker-engine.mk
 > index 262be2df20..066959e0c0 100644
 > --- a/package/docker-engine/docker-engine.mk
 > +++ b/package/docker-engine/docker-engine.mk
 > @@ -4,7 +4,7 @@
 >  #
 >  ################################################################################
 
 > -DOCKER_ENGINE_VERSION = 24.0.7
 > +DOCKER_ENGINE_VERSION = 25.0.3
 >  DOCKER_ENGINE_SITE = $(call github,moby,moby,v$(DOCKER_ENGINE_VERSION))
 
 >  DOCKER_ENGINE_LICENSE = Apache-2.0
 > -- 

 > 2.43.0


-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-02-07  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  2:21 [Buildroot] [PATCH v1 1/2] package/docker-engine: bump version to v25.0.3 Christian Stewart via buildroot
2024-02-07  2:21 ` [Buildroot] [PATCH v1 2/2] package/docker-cli: " Christian Stewart via buildroot
2024-02-07  8:58 ` Peter Korsgaard [this message]
2024-07-19  3:37   ` [Buildroot] [PATCH v1 1/2] package/docker-engine: " Christian Stewart via buildroot

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=87ttmk1wib.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tianyuanhao3@163.com \
    --cc=yann.morin.1998@free.fr \
    /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