Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update google-cloud-cpp to v2.11.0 #139

Closed
wants to merge 4 commits into from
Closed

Conversation

dbolduc
Copy link
Contributor

@dbolduc dbolduc commented Jun 2, 2023

I could not figure out how to add commits onto #138, so here is a new PR.

@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@h-vetinari
Copy link
Member

I could not figure out how to add commits onto #138, so here is a new PR.

That's because you're not a maintainer on this feedstock... yet? ;-)
I see you're an upstream maintainer, so I'd be happy to have you on board!

(to do so, add your GH handle in the appropriate section at the end of the meta.yaml)

@h-vetinari
Copy link
Member

Also, note that this PR doesn't automatically get the newest protobuf version pulled in (that takes extra steps which are currently waiting in a separate PR). So IIUC, we shouldn't yet remove the patch that disables some features, because this build is still against protobuf 3.21. Some short discussion on this with Carlos is in #136

@dbolduc
Copy link
Contributor Author

dbolduc commented Jun 2, 2023

add your GH handle in the appropriate section

Done.

this PR doesn't automatically get the newest protobuf version pulled in

Ah, ok. I now see how the "Rebuild for protobuf423" PRs update the protobuf version in the .ci_support/*.yaml files.

I rebased the patch. (Maybe I could have included the commits from #137 in this PR, but oh well).

@h-vetinari
Copy link
Member

Ah, ok. I now see how the "Rebuild for protobuf423" PRs update the protobuf version in the .ci_support/*.yaml files.

We don't have to do that manually, that's done by the bot (which can be invoked like [at]conda-forge-admin, please rerender, or if you have conda smithy installed locally, as conda smithy rerender in the feedstock base folder).

If you want we can already pick the relevant commit (6da07f4) into this PR and then rerender. Or we do it in separate PRs (which is perhaps cleaner), no strong feelings.

Happy to have you on board!

Comment on lines -1 to -9
From 20b43fdb677ea76cfcbdf0e4f000158fe99f615d Mon Sep 17 00:00:00 2001
From: Carlos O'Ryan <coryan@google.com>
Date: Tue, 7 Feb 2023 01:35:26 +0000
Subject: [PATCH] disable libraries

---
cmake/GoogleCloudCppFeatures.cmake | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We try to keep attribution on patches. Generally git format-patch tags/<x> --no-signature works best (in a branch based on the last release, which can be rebased when the next release comes around).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fixed this in #138, also reducing the churn of deleting-and-reinstating the patch.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fixed this in #138

Awesome, thanks! I will close this PR.

@dbolduc dbolduc closed this Jun 2, 2023
@dbolduc dbolduc deleted the pr-138 branch June 2, 2023 02:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants