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

Pin proj to 9.3.0 in cuproj #1307

Merged
merged 1 commit into from
Dec 7, 2023

Conversation

jakirkham
Copy link
Member

@jakirkham jakirkham commented Dec 6, 2023

Description

Currently pyproj is still pinned to proj 9.3.0 (for example). However proj recently released 9.3.1 ( conda-forge/proj.4-feedstock#140 ), which cuproj is pulling in at the moment. Since proj pins to the patch version in its run_exports, building against 9.3.1 means cuproj would need exactly 9.3.1 at runtime. This makes it incompatible with everything else, which is still pinned to proj 9.3.0. Embedded screenshot below to highlight this

Screenshot 2023-12-06 at 3 30 00 PM

So for now just manually pin proj to 9.3.0 to build cuproj with a consistent proj version to resolve conflicts

This issue should clear up once to proj 9.3.1 migration ( conda-forge/conda-forge-pinning-feedstock#5226 ) completes. Then we can bump this or drop it as we see fit then

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@jakirkham jakirkham changed the base branch from branch-24.02 to branch-23.12 December 6, 2023 23:12
@github-actions github-actions bot added the conda Related to conda and conda configuration label Dec 6, 2023
@jakirkham jakirkham added bug Something isn't working non-breaking Non-breaking change labels Dec 6, 2023
Copy link
Contributor

@bdice bdice left a comment

Choose a reason for hiding this comment

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

Approve. I think this will help fix the issue. We typically have been pinning with proj_version in conda_build_config.yaml and {{ proj_version }} in meta.yaml to make it clear that we have a pin for readers of meta.yaml -- but this PR's changes are functionally equivalent.

@jakirkham jakirkham marked this pull request as ready for review December 7, 2023 00:12
@jakirkham jakirkham requested a review from a team as a code owner December 7, 2023 00:12
@raydouglass raydouglass merged commit 7eb9d57 into rapidsai:branch-23.12 Dec 7, 2023
64 of 65 checks passed
@jakirkham jakirkham deleted the pin_proj_930 branch December 7, 2023 01:02
rapids-bot bot pushed a commit that referenced this pull request Aug 30, 2024
Proposes removing the `cuproj` conda package's pin on `proj`, so that it can build using the same version that `conda-forge` pins to in https://github.com/conda-forge/conda-forge-pinning-feedstock.

For context, see:

* why the `proj==9.3.0` pin was originally added: #1307
* `conda-forge` completied migrations:
  - `9.3.1`: conda-forge/conda-forge-pinning-feedstock#5401
  - `9.4.`: conda-forge/conda-forge-pinning-feedstock#6240

Authors:
  - James Lamb (https://github.com/jameslamb)

Approvers:
  - https://github.com/jakirkham

URL: #1449
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working conda Related to conda and conda configuration non-breaking Non-breaking change
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

4 participants