public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Peter Marko <peter.marko@siemens.com>
To: openembedded-core@lists.openembedded.org
Cc: Peter Marko <peter.marko@siemens.com>
Subject: [meta-python][PATCH v2 2/3] python3-protobuf: upgrade 6.33.5 -> 6.33.6
Date: Mon, 23 Mar 2026 21:07:14 +0100	[thread overview]
Message-ID: <20260323200715.11652-2-peter.marko@siemens.com> (raw)
In-Reply-To: <20260323200715.11652-1-peter.marko@siemens.com>

From: Peter Marko <peter.marko@siemens.com>

Release information [1] does not list python changes, but we should
match protobuf (C++) recipe version.

[1] https://github.com/protocolbuffers/protobuf/releases/tag/v33.6

Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
 .../{python3-protobuf_6.33.5.bb => python3-protobuf_6.33.6.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-python/recipes-devtools/python/{python3-protobuf_6.33.5.bb => python3-protobuf_6.33.6.bb} (95%)

diff --git a/meta-python/recipes-devtools/python/python3-protobuf_6.33.5.bb b/meta-python/recipes-devtools/python/python3-protobuf_6.33.6.bb
similarity index 95%
rename from meta-python/recipes-devtools/python/python3-protobuf_6.33.5.bb
rename to meta-python/recipes-devtools/python/python3-protobuf_6.33.6.bb
index af9ff85f20..bbc713442b 100644
--- a/meta-python/recipes-devtools/python/python3-protobuf_6.33.5.bb
+++ b/meta-python/recipes-devtools/python/python3-protobuf_6.33.6.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = " \
 "
 
 inherit pypi setuptools3
-SRC_URI[sha256sum] = "6ddcac2a081f8b7b9642c09406bc6a4290128fce5f471cddd165960bb9119e5c"
+SRC_URI[sha256sum] = "a6768d25248312c297558af96a9f9c929e8c4cee0659cb07e780731095f38135"
 
 CVE_PRODUCT += "google:protobuf protobuf:protobuf google-protobuf protobuf-python"
 CVE_STATUS[CVE-2026-0994] = "fixed-version: it is fixed in 6.33.5"


  reply	other threads:[~2026-03-23 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 20:07 [meta-oe][PATCH v2 1/3] lvm2: upgrade 2.03.38 -> 2.03.39 Peter Marko
2026-03-23 20:07 ` Peter Marko [this message]
2026-03-23 20:15   ` Patchtest results for [meta-python][PATCH v2 2/3] python3-protobuf: upgrade 6.33.5 -> 6.33.6 patchtest
2026-03-23 20:07 ` [meta-oe][PATCH v2 3/3] jsoncpp: upgrade 1.9.6 -> 1.9.7 Peter Marko
2026-03-23 20:15   ` Patchtest results for " patchtest
2026-03-23 20:15 ` Patchtest results for [meta-oe][PATCH v2 1/3] lvm2: upgrade 2.03.38 -> 2.03.39 patchtest

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=20260323200715.11652-2-peter.marko@siemens.com \
    --to=peter.marko@siemens.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox