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

CI: avoid bad combination of pyopenssl and cryptography versions #60462

Closed

Conversation

jorisvandenbossche
Copy link
Member

We are running into conda/conda#13619 (comment) in some of our envs, seeing what it gives to force a newer pyopenssl version.

@jorisvandenbossche jorisvandenbossche added this to the 2.3 milestone Dec 1, 2024
@jorisvandenbossche jorisvandenbossche marked this pull request as ready for review December 1, 2024 19:33
Copy link
Member

@mroeschke mroeschke left a comment

Choose a reason for hiding this comment

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

Thanks. I think we also need this in ci/deps/circle-311-arm64.yaml

@mroeschke mroeschke added the CI Continuous Integration label Dec 2, 2024
@@ -56,6 +56,8 @@ dependencies:
- xlrd>=2.0.1
- xlsxwriter>=3.0.5
- zstandard>=0.19.0
# TEMP to avoid error when the env gets cryptography >= 42 but older pyopenssl
Copy link

Choose a reason for hiding this comment

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

If that combination is wrong we should do a repo data patch to fix it. I'll investigate this on the conda-forge side.

Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link

Choose a reason for hiding this comment

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

Yep. In fact two! conda-forge/conda-forge-repodata-patches-feedstock#918 was just merged and hopefully you don't need this work around.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for merging that!

@mroeschke
Copy link
Member

I think we can close this PR since this error isn't showing up on main anymore

@mroeschke mroeschke closed this Dec 4, 2024
@jorisvandenbossche jorisvandenbossche deleted the ci-crypto branch December 4, 2024 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants