From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: peter.marko@siemens.com
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH 2/2] grpc-go: Upgrade 1.41.0 -> 1.59.0
Date: Tue, 7 Nov 2023 01:49:09 +0000 [thread overview]
Message-ID: <ZUmXlRPppFM+YERB@gmail.com> (raw)
In-Reply-To: <20231105140429.1973258-2-peter.marko@siemens.com>
In message: [meta-virtualization][PATCH 2/2] grpc-go: Upgrade 1.41.0 -> 1.59.0
on 05/11/2023 Peter Marko via lists.yoctoproject.org wrote:
> From: Peter Marko <peter.marko@siemens.com>
>
> CVE: CVE-2023-44487
There should also be a list of shortlogs covered by the update
(as you can see in most other recipe updates here)
>
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> ---
> recipes-devtools/go/grpc-go_git.bb | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/recipes-devtools/go/grpc-go_git.bb b/recipes-devtools/go/grpc-go_git.bb
> index b3b58ed4..8fe0875d 100644
> --- a/recipes-devtools/go/grpc-go_git.bb
> +++ b/recipes-devtools/go/grpc-go_git.bb
> @@ -7,10 +7,11 @@ LIC_FILES_CHKSUM = "file://src/${PKG_NAME}/LICENSE;md5=3b83ef96387f14655fc854ddc
> SRCNAME = "grpc-go"
>
> PKG_NAME = "google.golang.org/grpc"
> -SRC_URI = "git://github.com/grpc/${SRCNAME}.git;destsuffix=git/src/${PKG_NAME};branch=master;protocol=https"
> +SRC_URI = "git://github.com/grpc/${SRCNAME}.git;destsuffix=git/src/${PKG_NAME};branch=${BRANCH};protocol=https"
>
> -SRCREV = "5d8e5aad40bedb696205b96b786f1d0e1326b3f8"
> -PV = "1.41.0+git"
> +SRCREV = "7765221f4bf6104973db7946d56936cf838cad46"
> +BRANCH = "v1.59.x"
> +PV = "1.59.0+git"
We don't need to make branch a variable, it doesn't really
add anything to the patch or recipe.
Bruce
>
> S = "${WORKDIR}/git"
>
> --
> 2.30.2
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#8423): https://lists.yoctoproject.org/g/meta-virtualization/message/8423
> Mute This Topic: https://lists.yoctoproject.org/mt/102400852/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:[~2023-11-07 1:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 14:04 [meta-virtualization][PATCH 1/2] grpc-go: add grpc to CVE_PRODUCT Peter Marko
2023-11-05 14:04 ` [meta-virtualization][PATCH 2/2] grpc-go: Upgrade 1.41.0 -> 1.59.0 Peter Marko
2023-11-07 1:49 ` Bruce Ashfield [this message]
2023-11-07 7:02 ` [meta-virtualization][PATCH v2] " Peter Marko
2023-11-07 1:50 ` [meta-virtualization][PATCH 1/2] grpc-go: add grpc to CVE_PRODUCT 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=ZUmXlRPppFM+YERB@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=peter.marko@siemens.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.