rebuild grpc 1.46.4 with abseil 20211102

[ngam]

Follows #222
Fixes #221

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

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

I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[conda-forge-linter]

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.

[ngam]

@conda-forge-admin, please rerender

[h-vetinari]

Forget the rerender, it's just useless churn

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/grpc-cpp-feedstock/actions/runs/2868526465.

[ngam]

My recommendation is to immediately revert this after merge. I can submit a follow up PR that essentially reverts this and bumps the build number. I think this is better for organization, but let me know what you prefer.

[h-vetinari]

Could it be that you confused yourself with the title and branch name? Because this is targetting 1.46.4 (which was also the point of #221), not 1.46.3

[ngam]

Could it be that you confused yourself with the title and branch name? Because this is targetting 1.46.4 (which was also the point of #221), not 1.46.3

Yes! LOL. Don't tell anyone, but I was in a virtual doctor's appointment while doing this, hence the confusions...

Let me run through everything again to ensure I am not losing my mind.

[h-vetinari]

Let me run through everything again to ensure I am not losing my mind.

I'm ready to merge this. Anything I should still be waiting for?

[ngam]

I believe we are good to go, but since I have you here: I want to point out that abseil and grpc didn't get unzipped entirely. I thought they were supposed to be unzipped. Maybe I was wrong or misunderstood the latest abseil migration...

xref:

• Rebuild for abseil_cpp202206230 jaxlib-feedstock#130
• conda-forge/jaxlib-feedstock@53827ef

[h-vetinari]

I thought they were supposed to be unzipped. Maybe I was wrong or misunderstood the latest abseil migration...

The plan is to unzip them after the 20220623 migration. @hmaarrfk was worried we'd run into more problems without the zip than with it.

[h-vetinari]

You can still override grpc on a per-feedstock level through the cbc; ping me in case of doubt.

[ngam]

I thought they were supposed to be unzipped. Maybe I was wrong or misunderstood the latest abseil migration...

The plan is to unzip them after the 20220623 migration. @hmaarrfk was worried we'd run into more problems without the zip than with it.

Okay, makes sense. Yes, it is safer this way. I also just read the migration file. Thanks!