From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: soumya.sambu@windriver.com
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][mickledore][PATCH 1/1] kubernetes: Upgrade v1.27.1 -> v1.27.5
Date: Fri, 20 Oct 2023 18:35:01 +0000 [thread overview]
Message-ID: <ZTLIVb+5KPDIjXnd@gmail.com> (raw)
In-Reply-To: <20231019095052.1389561-1-soumya.sambu@windriver.com>
In message: [meta-virtualization][mickledore][PATCH 1/1] kubernetes: Upgrade v1.27.1 -> v1.27.5
on 19/10/2023 Soumya via lists.yoctoproject.org wrote:
> From: Soumya Sambu <soumya.sambu@windriver.com>
>
> Addresses CVE-2023-2431, CVE-2023-2727, CVE-2023-2728,
> CVE-2023-3676, CVE-2023-3955 and few other bugs.
Whenever targeting a CVE fix for a release branch, commits should
state whether or not other branches are vulnerable, and at the same
time confirm that there's a newer release available in those other
branches (typically that is why they aren't vulnerable)
>
> Changelog:
> https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.27.md#v1275
As you can tell from the other commits in the layer, linking to a changelog
isn't the preferred way to document changes. They aren't searchable when
done in this manner.
I'll wait for a v2 with the changelog.
Bruce
>
> Signed-off-by: Soumya Sambu <soumya.sambu@windriver.com>
> ---
> recipes-containers/kubernetes/kubernetes_git.bb | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-containers/kubernetes/kubernetes_git.bb b/recipes-containers/kubernetes/kubernetes_git.bb
> index 3a6e7119..560fd8b7 100644
> --- a/recipes-containers/kubernetes/kubernetes_git.bb
> +++ b/recipes-containers/kubernetes/kubernetes_git.bb
> @@ -5,8 +5,8 @@ applications across multiple hosts, providing basic mechanisms for deployment, \
> maintenance, and scaling of applications. \
> "
>
> -PV = "v1.27.1+git${SRCREV_kubernetes}"
> -SRCREV_kubernetes = "2555e0f90e80a13628f47eca5cde34decc89babb"
> +PV = "v1.27.5+git${SRCREV_kubernetes}"
> +SRCREV_kubernetes = "93e0d7146fb9c3e9f68aa41b2b4265b2fcdb0a4c"
> SRCREV_kubernetes-release = "21382abdbfa8e6a43fd417306fa649cb651cc06e"
> PE = "1"
>
> --
> 2.40.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#8381): https://lists.yoctoproject.org/g/meta-virtualization/message/8381
> Mute This Topic: https://lists.yoctoproject.org/mt/102057034/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2023-10-20 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 9:50 [meta-virtualization][mickledore][PATCH 1/1] kubernetes: Upgrade v1.27.1 -> v1.27.5 ssambu
2023-10-20 18:35 ` Bruce Ashfield [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=ZTLIVb+5KPDIjXnd@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=soumya.sambu@windriver.com \
/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.