It is funny (not so) that after updating alidist some packages depending on OpenSSL1.1.0m are failing to build due to following problem:
2022-05-12@08:22:54:DEBUG:QualityControl:sqlite:0: + git clone -n --filter=blob:none --reference /home/evdokimov/alice/sw/MIRROR/sqlite https://github.com/alisw/sqlite /home/evdokimov/alice/sw/SOURCES/sqlite/v3.15.0/v3.15.0 2022-05-12@08:22:54:DEBUG:QualityControl:sqlite:0: Cloning into '/home/evdokimov/alice/sw/SOURCES/sqlite/v3.15.0/v3.15.0'... 2022-05-12@08:22:54:DEBUG:QualityControl:sqlite:0: /usr/lib/git-core/git-remote-https: symbol lookup error: /lib/x86_64-linux-gnu/libssh.so.4: undefined symbol: EC_KEY_free, version OPENSSL_1_1_0 2022-05-12@08:22:54:ERROR:QualityControl:sqlite:0: Error while executing /home/evdokimov/alice/sw/SPECS/ubuntu2004_x86-64/sqlite/v3.15.0-local1/build.sh on `hp-laptop-sevdokim'.
It seems that system git is somehow picking up version of OpenSSL build by aliBuild. I found temporary solution to execute git commands myself with native bash shell where git picks up system OpenSSL files. Then run aliBuild again and wait for fail in next package. However it is pretty annoying. Maybe you know a better solution for that?
Thanks & cheers,