From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Christian Stewart <christian@aperture.us>
Cc: Stefan Agner <stefan@agner.ch>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/2] package/docker-cli: bump version to v26.0.0
Date: Mon, 1 Apr 2024 14:21:47 +0200 [thread overview]
Message-ID: <Zgqm28arkssJGgzZ@landeda> (raw)
In-Reply-To: <20240331074614.17359-2-christian@aperture.us>
Christian, All,
On 2024-03-31 00:46 -0700, Christian Stewart via buildroot spake thusly:
> Update to the latest major release of docker-cli.
>
> https://github.com/moby/moby/releases/tag/v26.0.0
>
> Signed-off-by: Christian Stewart <christian@aperture.us>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/docker-cli/docker-cli.hash | 2 +-
> package/docker-cli/docker-cli.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/docker-cli/docker-cli.hash b/package/docker-cli/docker-cli.hash
> index 9c8d08bba5..26558814c1 100644
> --- a/package/docker-cli/docker-cli.hash
> +++ b/package/docker-cli/docker-cli.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 72a54d131c28938221c81bd08364459fed9c71c093d4d615d324aaf31de6db1d docker-cli-24.0.7.tar.gz
> +sha256 96ed5d7c33a12f505d13fa03fa48f94cb41cf871178df0df84aa0b76839ad321 docker-cli-26.0.0.tar.gz
> sha256 2d81ea060825006fc8f3fe28aa5dc0ffeb80faf325b612c955229157b8c10dc0 LICENSE
> diff --git a/package/docker-cli/docker-cli.mk b/package/docker-cli/docker-cli.mk
> index 95fce27ffb..5f9242329a 100644
> --- a/package/docker-cli/docker-cli.mk
> +++ b/package/docker-cli/docker-cli.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -DOCKER_CLI_VERSION = 24.0.7
> +DOCKER_CLI_VERSION = 26.0.0
> DOCKER_CLI_SITE = $(call github,docker,cli,v$(DOCKER_CLI_VERSION))
>
> DOCKER_CLI_LICENSE = Apache-2.0
> --
> 2.43.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-01 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 7:46 [Buildroot] [PATCH v1 1/2] package/docker-engine: security bump to version v26.0.0 Christian Stewart via buildroot
2024-03-31 7:46 ` [Buildroot] [PATCH v1 2/2] package/docker-cli: bump version to v26.0.0 Christian Stewart via buildroot
2024-04-01 12:21 ` Yann E. MORIN [this message]
2024-04-28 15:08 ` Peter Korsgaard
2024-04-01 12:21 ` [Buildroot] [PATCH v1 1/2] package/docker-engine: security bump to version v26.0.0 Yann E. MORIN
2024-04-28 15:08 ` Peter Korsgaard
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=Zgqm28arkssJGgzZ@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=stefan@agner.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.