From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/python-google-api-core: bump to version 2.19.2
Date: Sun, 15 Sep 2024 10:12:15 +0200 [thread overview]
Message-ID: <20240915101215.044073fa@windsurf> (raw)
In-Reply-To: <20240915071447.1540596-2-james.hilliard1@gmail.com>
On Sun, 15 Sep 2024 01:14:47 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> diff --git a/package/python-google-api-core/Config.in b/package/python-google-api-core/Config.in
> index 689923a2f4..21fe361e07 100644
> --- a/package/python-google-api-core/Config.in
> +++ b/package/python-google-api-core/Config.in
> @@ -2,6 +2,7 @@ config BR2_PACKAGE_PYTHON_GOOGLE_API_CORE
> bool "python-google-api-core"
> select BR2_PACKAGE_PYTHON_GOOGLE_AUTH # runtime
> select BR2_PACKAGE_PYTHON_GOOGLEAPIS_COMMON_PROTOS # runtime
> + select BR2_PACKAGE_PYTHON_PROTO_PLUS # runtime
And now that BR2_PACKAGE_PYTHON_PROTO_PLUS has a depends on
BR2_PACKAGE_HOST_PROTOBUF_ARCH_SUPPORTS, it needs to be propagated here
as well, and also to the reverse dependencies, i.e
package/python-grpc-requests/Config.in. I fixed that.
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:[~2024-09-15 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 7:14 [Buildroot] [PATCH 1/2] package/python-proto-plus: new package James Hilliard
2024-09-15 7:14 ` [Buildroot] [PATCH 2/2] package/python-google-api-core: bump to version 2.19.2 James Hilliard
2024-09-15 8:12 ` Thomas Petazzoni via buildroot [this message]
2024-09-15 8:11 ` [Buildroot] [PATCH 1/2] package/python-proto-plus: new package 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=20240915101215.044073fa@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=james.hilliard1@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