From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Michael Nosthoff <buildroot@heine.tech>
Cc: buildroot@buildroot.org, Robert Rose <robertroyrose@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 3/3] package/grpc: bump to version 1.76.0
Date: Mon, 2 Feb 2026 23:16:45 +0100 [thread overview]
Message-ID: <aYEiG9RbjhMkBQ8y@windsurf> (raw)
In-Reply-To: <20260107140858.129302-3-buildroot@heine.tech>
Hello,
On Wed, Jan 07, 2026 at 03:08:47PM +0100, Michael Nosthoff via buildroot wrote:
> - use new flag gRPC_DOWNLOAD_ARCHIVES=OFF which removed the need for patch 003
> - re-allign patches
> - update 0002 to properly apply and re-enable utf8_range_lib as its linked
> against grpc_plugin_support
>
> Release Notes since 1.66:
> https://github.com/grpc/grpc/releases/tag/v1.67.0
> https://github.com/grpc/grpc/releases/tag/v1.68.0
> https://github.com/grpc/grpc/releases/tag/v1.69.0
> https://github.com/grpc/grpc/releases/tag/v1.70.0
> https://github.com/grpc/grpc/releases/tag/v1.71.0
> https://github.com/grpc/grpc/releases/tag/v1.72.0
> https://github.com/grpc/grpc/releases/tag/v1.73.0
> https://github.com/grpc/grpc/releases/tag/v1.74.0
> https://github.com/grpc/grpc/releases/tag/v1.75.0
> https://github.com/grpc/grpc/releases/tag/v1.76.0
>
> Fixes: 2d19a0b332dc17c18533b "package/{python-}protobuf: bump to version 33.2"
>
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
>
> --
>
> V2: added "Fixes" part
>
> The protobuf bump to 33.2 was initially contained in this series. Another
> standalone patch was then applied in commit 2d19a0b332dc17c18533b instead.
> Which broke the build of grpc 1.66.1 which relies on an older protobuf
> version.
> This can be observed with this defconfig:
>
> BR2_arm=y
> BR2_cortex_a53=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
> BR2_PACKAGE_COLLECTD=y
> BR2_PACKAGE_COLLECTD_GRPC=y
I moved a bunch of this explanation in the commit message itself, as
it was useful. Also, I've added a reference to the autobuilder failure
that this bump is fixing. And of course, I applied to master.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-02 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:08 [Buildroot] [PATCH v2 1/3] package/collectd: enforce c++17 Michael Nosthoff via buildroot
2026-01-07 14:08 ` [Buildroot] [PATCH v2 2/3] package/libabseil-cpp: bump to version 20250814.1 Michael Nosthoff via buildroot
2026-02-02 22:15 ` Thomas Petazzoni via buildroot
2026-01-07 14:08 ` [Buildroot] [PATCH v2 3/3] package/grpc: bump to version 1.76.0 Michael Nosthoff via buildroot
2026-02-02 22:16 ` Thomas Petazzoni via buildroot [this message]
2026-02-02 22:15 ` [Buildroot] [PATCH v2 1/3] package/collectd: enforce c++17 Thomas Petazzoni via buildroot
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=aYEiG9RbjhMkBQ8y@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@heine.tech \
--cc=robertroyrose@gmail.com \
--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