-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Make libprotobuf
a build
only dependency
#74
Conversation
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 ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.10.12.13.22.36
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally. This message was generated by GitHub actions workflow run https://github.com/conda-forge/dask-sql-feedstock/actions/runs/6497409473. |
If the re-render didn't do anything, this change isn't working. Would suggesting taking a closer look |
@conda-forge-admin, please rerender |
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/dask-sql-feedstock/actions/runs/6497631962. |
Might want to look at |
…nda-forge-pinning 2023.10.12.13.22.36
@jakirkham I looked over |
… conda-smithy 3.27.1, and conda-forge-pinning 2023.10.12.13.22.36
@conda-forge-admin, please rerender |
fdd85d2
to
de9f921
Compare
recipe/conda_build_config.yaml
Outdated
- 1.56 | ||
libprotobuf: | ||
- 4.24.3 | ||
- 4.23.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we keep the global pinning for libprotobuf
if we are overriding libprotobuf
here?
- 4.23.3 | |
- 4.23.4 | |
- 4.23.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The entries in this matrix are:
- Global pinning (4.23.4) plus migrations (which make it 4.24.3)
- Older libprotobuf pinning that we need (4.23.3)
recipe/conda_build_config.yaml
Outdated
# replace migrators for libprotobuf 1.57 / 1.58. | ||
libgrpc: | ||
- 1.58 | ||
- 1.56 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also libgrpc
is pinned globally at 1.57
. Do we want to include this as well?
- 1.56 | |
- 1.57 | |
- 1.56 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The entries in this matrix are:
- Global pinning (1.57) plus migrations (which make it 1.58)
- libgrpc matching the older libprotobuf pinning that we need
- libgrpc 1.56 was originally pinned with libprotobuf 4.23.3, from what I see here: conda-forge/conda-forge-pinning-feedstock@621d4a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll need to zip and match libprotobuf with libgrpc and also libabseil; they're not interrelated on source-level, but since we now need to migrate even for protobuf patch versions, we cannot feasibly build all combinations, and so we coupled them 1:1 as follows:
abseil | grpc | protobuf |
---|---|---|
20230125 | 1.54 | 3.21 |
20230125 | 1.56 | 4.23.3 |
20230802 | 1.57 | 4.23.4 |
20230802 | 1.58 | 4.24.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though I guess it would be conceivable to rebuild grpc 1.56 & protobuf 4.23.3 with newer abseil.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More details here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Axel! 🙏
Currently we are hoping none of this is needed and that it was an oversight libprotobuf
was in host
. So are now trying to add it to build
only
Though it is possible that won't work, in which case we will go back to adding in another set of versions. We had a working solution later in the commits based on a custom migrator, which was more ergonomic. This is probably what we would go back to if we need to add these in version pinnings in
Am worried that what we are doing here is a bit fragile since we are overriding global pinnings and manually adding values from migrators Think it would be better if we used some method to append our values to the keys (instead of overriding them). Either using something from |
In terms of a migrator (which may wind up being the best/simplest solution), would try...
This should add new builds with the expected versions (if not repeat 3-4) |
This is a good idea. I like it! |
…nda-forge-pinning 2023.10.12.13.22.36
…nda-forge-pinning 2023.10.12.13.22.36
May also need to make this change (in - - libprotobuf # [build_platform != target_platform]
+ - libprotobuf |
…nda-forge-pinning 2023.10.12.13.22.36
@conda-forge-admin , please re-render |
…nda-forge-pinning 2023.10.12.13.22.36
libprotobuf
a build
only dependency
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)