Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] runc: bump to version 1.0.0-rc6
Date: Sun, 30 Dec 2018 14:46:01 +0100	[thread overview]
Message-ID: <20181230144601.61d07fba@windsurf> (raw)
In-Reply-To: <20181229104217.13806-1-christian@paral.in>

Hello,

On Sat, 29 Dec 2018 02:42:16 -0800, Christian Stewart wrote:
> Previously, a specific commit hash from the Docker runc.installer was used to
> determine the required runc version for the Docker Engine. This old commit hash
> used was a untagged pre-1.0.0 release of runc, closer to an earlier release
> candidate.
> 
> The runc version used in the Debian distribution is not the pinned version
> previously used by Buildroot. It is the latest release candidate. The latest
> release candidate is known to be compatible with the Docker Engine, and there is
> no justification for pinning to an older RC anymore.
> 
> This commit bumps to the latest RC, 1.0.0-rc6. A v1.0.0 is expected soon.
> 
> Signed-off-by: Christian Stewart <christian@paral.in>
> ---
>  package/runc/runc.hash | 2 +-
>  package/runc/runc.mk   | 3 +--
>  2 files changed, 2 insertions(+), 3 deletions(-)

Both patches applied. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-12-30 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29 10:42 [Buildroot] [PATCH 1/2] runc: bump to version 1.0.0-rc6 Christian Stewart
2018-12-29 10:42 ` [Buildroot] [PATCH 2/2] docker-containerd: bump to version 1.2.1 Christian Stewart
2018-12-30 13:46 ` Thomas Petazzoni [this message]

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=20181230144601.61d07fba@windsurf \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox