All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7] Bump docker packages to v18.09.4
Date: Mon,  1 Apr 2019 20:23:44 +0200	[thread overview]
Message-ID: <20190401182352.26342-1-peter@korsgaard.com> (raw)

Bump the docker packages to the v18.09.4 release.

Unit test is still successful:
./support/testing/run-tests -o output-test tests.package.test_docker_compose
19:38:21 TestDockerCompose                        Starting
19:38:23 TestDockerCompose                        Building
20:14:18 TestDockerCompose                        Building done
20:15:03 TestDockerCompose                        Cleaning up
.
Ran 1 test in 2211.902s

OK

Peter Korsgaard (7):
  package/runc: bump to version 1.0.0-rc7
  Revert "package/runc: blacklist Codesourcery ARM toolchain"
  Revert "runc: depend on linux headers >= 3.11 for O_TMPFILE"
  package/docker-containerd: bump version to v1.2.5
  package/docker-containerd: refer to official website
  package/docker-engine: bump to version v18.09.4
  package/docker-cli: bump to version v18.09.4

 package/docker-cli/docker-cli.hash                 |   2 +-
 package/docker-cli/docker-cli.mk                   |   2 +-
 package/docker-containerd/Config.in                |   8 +-
 package/docker-containerd/docker-containerd.hash   |   2 +-
 package/docker-containerd/docker-containerd.mk     |   2 +-
 package/docker-engine/Config.in                    |   8 +-
 package/docker-engine/docker-engine.hash           |   2 +-
 package/docker-engine/docker-engine.mk             |   2 +-
 ...ne-proc-self-exe-to-avoid-exposing-host-b.patch | 338 ---------------------
 package/runc/Config.in                             |   8 +-
 package/runc/runc.hash                             |   2 +-
 package/runc/runc.mk                               |   2 +-
 12 files changed, 14 insertions(+), 364 deletions(-)
 delete mode 100644 package/runc/0001-nsenter-clone-proc-self-exe-to-avoid-exposing-host-b.patch

-- 
2.11.0

             reply	other threads:[~2019-04-01 18:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 18:23 Peter Korsgaard [this message]
2019-04-01 18:23 ` [Buildroot] [PATCH 1/7] package/runc: bump to version 1.0.0-rc7 Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 2/7] Revert "package/runc: blacklist Codesourcery ARM toolchain" Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 3/7] Revert "runc: depend on linux headers >= 3.11 for O_TMPFILE" Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 4/7] package/docker-containerd: bump version to v1.2.5 Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 5/7] package/docker-containerd: refer to official website Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 6/7] package/docker-engine: bump to version v18.09.4 Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 7/7] package/docker-cli: " Peter Korsgaard
     [not found] ` <87mul8vgj8.fsf@paral.in>
2019-04-02 15:24   ` [Buildroot] [PATCH 0/7] Bump docker packages to v18.09.4 Peter Korsgaard
2019-04-07  7:20   ` Peter Korsgaard
2019-04-07  8:56     ` Christian Stewart
2019-04-07  9:28       ` Peter Korsgaard
2019-04-08  4:35         ` Christian Stewart
2019-04-08  6:12           ` Peter Korsgaard
2019-04-14 21:15 ` 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=20190401182352.26342-1-peter@korsgaard.com \
    --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.