Rebuild for openssl3 #50
Conversation
…nda-forge-pinning 2022.09.21.18.22.03
regro-cf-autotick-bot
requested review from
Tobias-Fischer,
andfoy,
ccordoba12,
duncanmmacleod,
gillins,
jschueller,
matthiasdiener,
mingwandroid,
msarahan,
ocefpaf and
stuarteberg
as code owners
|
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 ( |
|
Hello @conda-forge/qt-main, there is anything I can do to help in getting this merged? My understanding is that probably this requires a manual build for aarch64, but perhaps I am wrong. |
|
I’m happy to do the aarch build if that is what is stopping this PR |
Thanks a lot! Both Travis jobs are failing with |
|
Just a heads up #41 (comment) |
|
I totally forgot that we discussed this before. Thanks for the reminder @andfoy. @traversaro it seems like we’ll need to build some packages to also have OpenSSL 1.1 builds - do you know which ones are the culprit at the moment? |
What is the blocking problem between qt5 and openssl 3 ? Ubuntu (https://packages.ubuntu.com/kinetic/libqt5network5), vcpkg and Debian (https://packages.debian.org/sid/libqt5network5) seem all to ship qt5 + openssl 3 . The debian related patch seem https://sources.debian.org/patches/qtbase-opensource-src/5.15.6%2Bdfsg-2/openssl3.diff/ .
This is a good question. I arrived here as the tests in conda-forge/staged-recipes#20432 (comment) are failing as openssl 3 is installed with some dependencies that required qt-main, but I am not sure why openssl 3 is installed in the first place, as openssl 1 is use without problems during the build step. |
|
@isuruf Aside from having to manually build for aarch/ppc, I think this should be fine? |
|
building with emulation on x86 is not "fast" but it does work. I can do it on the next run. I just didn't see this. |
Thanks a lot! One thing that's going to be painful about this is that it doubles our build matrix on certain CFEP03-affected feedstocks (mainly qt & tensorflow), and we'll have to keep building both for a while yet. I'm trying to see that we can get through the migration ASAP, but I'm not optimistic we won't hit another snag (e.g. packages that aren't ready; also, when this last came up in the core call, the anaconda folks mentioned they hadn't started OpenSSL 3 builds at all yet, so dropping 1.1.1 would have some cf-external impact - not that we need to care, but I think we probably do care anyway) |
|
Due to the |
This PR has been triggered in an effort to update openssl3.
Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
If this PR was opened in error or needs to be updated please add the
bot-rerunlabel to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun botin a PR comment to have theconda-forge-adminadd it for you.This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/3109580846, please use this URL for debugging.