From: Michael Nosthoff via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: 2dad10f61914960b2bc05a650450d7fe2b8aa211@osuosl.org,
Sep@osuosl.org, 17@osuosl.org, Asaf Kahlon <asafka7@gmail.com>,
Mon@osuosl.org, rom@osuosl.org, 2001@osuosl.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Matt Weber <matthew.weber@collins.com>,
"00:00:00"@osuosl.org
Subject: [Buildroot] [PATCH 1/1] package/{python-}protobuf: bump to version 3.20.1
Date: Mon, 25 Apr 2022 10:05:03 +0200 [thread overview]
Message-ID: <20220425080503.769954-1-buildroot@heine.tech> (raw)
Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
---
package/protobuf/protobuf.hash | 2 +-
package/protobuf/protobuf.mk | 2 +-
package/python-protobuf/python-protobuf.hash | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/protobuf/protobuf.hash b/package/protobuf/protobuf.hash
index 60e64f54d4..f37b2dee40 100644
--- a/package/protobuf/protobuf.hash
+++ b/package/protobuf/protobuf.hash
@@ -1,3 +1,3 @@
# Locally calculated
sha256 6e5e117324afd944dcf67f36cf329843bc1a92229a8cd9bb573d7a83130fea7d LICENSE
-sha256 645192532f28254152b51c01868efdf9b766b1dbe49c77cccd6efcdb2d7c7bc2 protobuf-cpp-3.19.1.tar.gz
+sha256 dddd73664306d7d895a95e1cf18925b31b52785e468727e4635b45edae5166f9 protobuf-cpp-3.20.1.tar.gz
diff --git a/package/protobuf/protobuf.mk b/package/protobuf/protobuf.mk
index 80764f0216..c4c33ba7da 100644
--- a/package/protobuf/protobuf.mk
+++ b/package/protobuf/protobuf.mk
@@ -7,7 +7,7 @@
# When bumping this package, make sure to also verify if the
# python-protobuf package still works and to update its hash,
# as they share the same version/site variables.
-PROTOBUF_VERSION = 3.19.1
+PROTOBUF_VERSION = 3.20.1
PROTOBUF_SOURCE = protobuf-cpp-$(PROTOBUF_VERSION).tar.gz
PROTOBUF_SITE = https://github.com/protocolbuffers/protobuf/releases/download/v$(PROTOBUF_VERSION)
PROTOBUF_LICENSE = BSD-3-Clause
diff --git a/package/python-protobuf/python-protobuf.hash b/package/python-protobuf/python-protobuf.hash
index 2bfef96676..ddfa48b491 100644
--- a/package/python-protobuf/python-protobuf.hash
+++ b/package/python-protobuf/python-protobuf.hash
@@ -1,3 +1,3 @@
# Locally calculated
-sha256 2286615a3ae3e24c3524d171b6728b77b72cd2f3aab905f6a8d3fcaf6209dd00 protobuf-python-3.19.1.tar.gz
+sha256 d3449b4df32ca155f8cd71051db916b2bf74cc925760e269c0acf09b48ec1cb8 protobuf-python-3.20.1.tar.gz
sha256 6e5e117324afd944dcf67f36cf329843bc1a92229a8cd9bb573d7a83130fea7d LICENSE
--
2.25.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-04-25 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 8:05 Michael Nosthoff via buildroot [this message]
2022-04-25 8:14 ` [Buildroot] [PATCH 1/1] package/{python-}protobuf: bump to version 3.20.1 Baruch Siach via buildroot
2022-04-25 8:16 ` Baruch Siach via buildroot
2022-04-25 8:39 ` Michael Nosthoff via buildroot
2022-04-27 17:15 ` Arnout Vandecappelle
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=20220425080503.769954-1-buildroot@heine.tech \
--to=buildroot@buildroot.org \
--cc="00:00:00"@osuosl.org \
--cc=17@osuosl.org \
--cc=2001@osuosl.org \
--cc=2dad10f61914960b2bc05a650450d7fe2b8aa211@osuosl.org \
--cc=Mon@osuosl.org \
--cc=Sep@osuosl.org \
--cc=asafka7@gmail.com \
--cc=buildroot@heine.tech \
--cc=matthew.weber@collins.com \
--cc=rom@osuosl.org \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox