From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Chen Qi <Qi.Chen@windriver.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][master][kirkstone][PATCH] containerd: upgrade to 1.6.6
Date: Thu, 7 Jul 2022 10:57:25 -0400 [thread overview]
Message-ID: <20220707145724.GB40251@gmail.com> (raw)
In-Reply-To: <20220707062949.110913-1-Qi.Chen@windriver.com>
I have a batched set of package updates pending, I've pushed
them to master-next, with more to come in the next few days.
Once I merge them to master, I'll cherry-pick the equivalent
update to this to kirkstone.
Bruce
In message: [meta-virtualization][master][kirkstone][PATCH] containerd: upgrade to 1.6.6
on 06/07/2022 Chen Qi wrote:
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> .../containerd/containerd-opencontainers_git.bb | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/recipes-containers/containerd/containerd-opencontainers_git.bb b/recipes-containers/containerd/containerd-opencontainers_git.bb
> index b0f92b12..c28b1510 100644
> --- a/recipes-containers/containerd/containerd-opencontainers_git.bb
> +++ b/recipes-containers/containerd/containerd-opencontainers_git.bb
> @@ -5,7 +5,7 @@ DESCRIPTION = "containerd is a daemon to control runC, built for performance and
> support as well as checkpoint and restore for cloning and live migration of containers."
>
>
> -SRCREV = "d12516713c315ea9e651eb1df89cf32ff7c8137c"
> +SRCREV = "10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1"
> SRC_URI = "git://github.com/containerd/containerd;branch=release/1.6;protocol=https \
> file://0001-Add-build-option-GODEBUG-1.patch \
> file://0001-Makefile-allow-GO_BUILD_FLAGS-to-be-externally-speci.patch \
> @@ -15,8 +15,8 @@ SRC_URI = "git://github.com/containerd/containerd;branch=release/1.6;protocol=ht
> LICENSE = "Apache-2.0"
> LIC_FILES_CHKSUM = "file://src/import/LICENSE;md5=1269f40c0d099c21a871163984590d89"
>
> -CONTAINERD_VERSION = "v1.6.1"
> -CVE_VERSION = "1.6.1"
> +CONTAINERD_VERSION = "v1.6.6"
> +CVE_VERSION = "1.6.6"
>
> EXTRA_OEMAKE += "GODEBUG=1"
>
> @@ -56,7 +56,7 @@ do_compile() {
> metrics filters identifiers labels leases plugin server services \
> cmd cio containers namespaces oci events log reaper sys rootfs nvidia seed apparmor seccomp \
> cap cri userns atomic ioutil os registrar seutil runtimeoptions netns \
> - shutdown schedcore tracing; do
> + shutdown schedcore tracing kmutex; do
> if [ -d ${S}/src/import/${c} ]; then
> ln -sfn ${S}/src/import/${c} ${S}/src/import/vendor/github.com/containerd/containerd/${c}
> fi
> --
> 2.37.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#7414): https://lists.yoctoproject.org/g/meta-virtualization/message/7414
> Mute This Topic: https://lists.yoctoproject.org/mt/92223491/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2022-07-07 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 6:29 [meta-virtualization][master][kirkstone][PATCH] containerd: upgrade to 1.6.6 Chen Qi
2022-07-07 14:57 ` Bruce Ashfield [this message]
2022-07-20 1:52 ` Chen, Qi
2022-07-20 15:08 ` Bruce Ashfield
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=20220707145724.GB40251@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=Qi.Chen@windriver.com \
--cc=meta-virtualization@lists.yoctoproject.org \
/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.