-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
OpenSSL 1 build? #194
Comments
For our education, what is your usecase? @conda-forge-admin please rerender |
Hi! This is the friendly automated conda-forge-webservice. I just wanted to let you know that I rerendered the recipe in #195. |
I'm going to warn you that we recently closed the openssl 1 builds. So this will become increasingly harder. I typically ask that people help maintain for these special requests, but given that you helped get down to the bottom of the ROS3 issue, i'll oblige since it is rather "easy" to do now. |
and if you had any input conda-forge/libnetcdf-feedstock#161 that would be greatly appreciated! |
Julia upstream uses OpenSSL 1.1.1 (as a dependency of libcurl and maybe libgit2) Julia binary packaging repackages the conda-forge package: This is because Julia binary packaging normally relies on cross compilation, but HDF5 cross compilation requires configuration settings from the actual hardware. This probably could be extracted from the compiler toolchain, but no one has finished this work yet. Julia will eventually have to resolve this when OpenSSL 1.1.1 support ends. |
Understood. i mean, we have "officially" ended support for openssl 1.1.1 by removing it from the build matrix conda-forge/conda-forge-pinning-feedstock#3838 (comment) |
cc @conda-forge/core (because of OpenSSL 1.1.1 & Julia support) |
Feedstock maintainers are free to add local pins in their own conda_build_config.yaml if they want to maintain those pins. In this case, I'd ask that those who need those pins (i.e. the Julia Binary repackaging team) take responsibility for the additional maintenance. I'd also ask that the openssl 3 pin not be removed in order to minimize the effects on other users. |
Comment:
Would it possible to get a build that links against openssl 1 rather than openssl 3?
The text was updated successfully, but these errors were encountered: