Skip to contentSkip to conversation

package/docker-cli: bump to version 19.03.13

PATCH New Christian Stewart 3 participants 5 messages Oct 19, 2020 – Oct 29, 2020

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/2 package/docker-cli: bump to version 19.03.13

---

v1 -> v2:

- added updated hash for 19.03.13

---
 package/docker-cli/docker-cli.hash | 2 +-
 package/docker-cli/docker-cli.mk   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
package/docker-cli/docker-cli.hash +1 -1
index 8f9e69e593..66abfe5224 100644
@@ -1,3 +1,3 @@
 # Locally calculated
-sha256	00801d6b7e9777cf2cf54255ca5afb7b58b3d35c14bb0f60bb9f07d031883223  docker-cli-19.03.12.tar.gz
+sha256	21b88a00e8f7a3194c0ae1de5a31e3e1728ef6aa2804158dcb502a8b5fd6ae2b  docker-cli-19.03.13.tar.gz
 sha256	2d81ea060825006fc8f3fe28aa5dc0ffeb80faf325b612c955229157b8c10dc0  LICENSE
package/docker-cli/docker-cli.mk +1 -1
index c6448ca660..86fffafdb8 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-DOCKER_CLI_VERSION = 19.03.12
+DOCKER_CLI_VERSION = 19.03.13
 DOCKER_CLI_SITE = $(call github,docker,cli,v$(DOCKER_CLI_VERSION))
 
 DOCKER_CLI_LICENSE = Apache-2.0
Signature · 1 line
2.28.0
#1 lore raw

PATCH v2 2/2 package/docker-engine: bump to version 19.03.13

The Docker developers appear to no longer be tagging releases on the docker/engine repository on GitHub, but are tagging releases on the main moby/moby repository, which still is the true home of "dockerd."

This commit changes the upstream repo to moby/moby with no changes required.

v1 -> v2:

- updated hash
- changed upstream to moby/moby

---
 package/docker-engine/docker-engine.hash | 2 +-
 package/docker-engine/docker-engine.mk   | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)
package/docker-engine/docker-engine.hash +1 -1
index 3283e4eb48..e7d5932687 100644
@@ -1,3 +1,3 @@
 # Locally calculated
-sha256	858e4e74ee0097bcbdb71d737e268dfcfd1970efa4a1600354253b02fd403e39  docker-engine-19.03.12.tar.gz
+sha256	f43331fef1d24e31f43392fc1fed72b48fc17fd432d341d6eb1f68ca11383406  docker-engine-19.03.13.tar.gz
 sha256	7c87873291f289713ac5df48b1f2010eb6963752bbd6b530416ab99fc37914a8  LICENSE
package/docker-engine/docker-engine.mk +2 -2
index 2d92570b94..8cedf307ba 100644
@@ -4,8 +4,8 @@
 #
 ################################################################################
 
-DOCKER_ENGINE_VERSION = 19.03.12
-DOCKER_ENGINE_SITE = $(call github,docker,engine,v$(DOCKER_ENGINE_VERSION))
+DOCKER_ENGINE_VERSION = 19.03.13
+DOCKER_ENGINE_SITE = $(call github,moby,moby,v$(DOCKER_ENGINE_VERSION))
 
 DOCKER_ENGINE_LICENSE = Apache-2.0
 DOCKER_ENGINE_LICENSE_FILES = LICENSE
Signature · 1 line
2.28.0
#2 lore raw

PATCH v2 2/2 package/docker-engine: bump to version 19.03.13

Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Christian" == Christian Stewart <[email protected]> writes:

The Docker developers appear to no longer be tagging releases on the docker/engine repository on GitHub, but are tagging releases on the main moby/moby repository, which still is the true home of "dockerd."

This commit changes the upstream repo to moby/moby with no changes required.

Quoted 8 lines

v1 -> v2:

- updated hash
- changed upstream to moby/moby

Committed to 2020.02.x and 2020.08.x, thanks.

Signature · 1 line
Bye, Peter Korsgaard
#4 lore raw

PATCH v2 1/2 package/docker-cli: bump to version 19.03.13

In reply to Christian Stewart
Quoted 10 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Christian" == Christian Stewart <[email protected]> writes:

---

v1 -> v2:

- added updated hash for 19.03.13

Committed to 2020.02.x and 2020.08.x, thanks.

Signature · 1 line
Bye, Peter Korsgaard