From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/docker-proxy: bump to feeff4
Date: Fri, 10 Jan 2020 09:40:53 +0100 [thread overview]
Message-ID: <87lfqfg0ve.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200110045033.1920685-2-christian@paral.in> (Christian Stewart's message of "Thu, 9 Jan 2020 20:50:33 -0800")
>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:
> docker-proxy (libnetwork) has not added a release tag for a long time. Use the
> latest master commit hash from 09 Jan 2020 instead.
> Signed-off-by: Christian Stewart <christian@paral.in>
Same comment as for docker-containerd.
I was of the understanding that docker-proxy isn't really needed any
more. Can you clarify?
> ---
> package/docker-proxy/docker-proxy.hash | 2 +-
> package/docker-proxy/docker-proxy.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> diff --git a/package/docker-proxy/docker-proxy.hash b/package/docker-proxy/docker-proxy.hash
> index 58de697929..4fa9541bed 100644
> --- a/package/docker-proxy/docker-proxy.hash
> +++ b/package/docker-proxy/docker-proxy.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 866c8d196b9396a383b437b0d775476459ed7c11f527c4f6bbf1fd08524b461d docker-proxy-55685ba49593e67f5e1c8180539379b16736c25e.tar.gz
> +sha256 0fffcd438b9a87a7ff8315364ff4631d2241ac0cf9f9f83871aeafcb2a383fd1 docker-proxy-feeff4f0a3fd2a2bb19cf67c826082c66ffaaed9.tar.gz
> sha256 cb5e8e7e5f4a3988e1063c142c60dc2df75605f4c46515e776e3aca6df976e14 LICENSE
> diff --git a/package/docker-proxy/docker-proxy.mk b/package/docker-proxy/docker-proxy.mk
> index 8843266c30..67f1ae2a90 100644
> --- a/package/docker-proxy/docker-proxy.mk
> +++ b/package/docker-proxy/docker-proxy.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
> -DOCKER_PROXY_VERSION = 55685ba49593e67f5e1c8180539379b16736c25e
> +DOCKER_PROXY_VERSION = feeff4f0a3fd2a2bb19cf67c826082c66ffaaed9
> DOCKER_PROXY_SITE = $(call github,docker,libnetwork,$(DOCKER_PROXY_VERSION))
> DOCKER_PROXY_LICENSE = Apache-2.0
> --
> 2.24.1
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-01-10 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 4:50 [Buildroot] [PATCH 1/2] package/docker-containerd: bump to 1.3.2 Christian Stewart
2020-01-10 4:50 ` [Buildroot] [PATCH 2/2] package/docker-proxy: bump to feeff4 Christian Stewart
2020-01-10 8:40 ` Peter Korsgaard [this message]
2020-01-11 4:20 ` Christian Stewart
2020-01-11 8:31 ` Peter Korsgaard
2020-02-04 23:06 ` Christian Stewart
2020-01-10 8:39 ` [Buildroot] [PATCH 1/2] package/docker-containerd: bump to 1.3.2 Peter Korsgaard
2020-01-11 4:21 ` Christian Stewart
2020-02-04 23:02 ` Christian Stewart
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=87lfqfg0ve.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.