> I think it's fine to reintroduce SSL, as it was never meant to be dropped. This will also introduce a new dependency (libssl1.1), but one that is basically impossible to be without on a system.
Ack; nice catch; I missed that one.
> I don't think this fix is working, has anybody tried a focal build? The configure script is not being regenerated from configure.in and it still checks for the old function:
Yes, I've tested the changes in comment #14.
During that process I too noticed that _one_ of the configure checks uses the old function, but _another one_ uses the new; and the binary worked in the end, so it seemed OK.
That can be observed in the build log above as well:
Hi Andreas,
Thanks for checking and reviewing this!
> I think it's fine to reintroduce SSL, as it was never meant to be dropped. This will also introduce a new dependency (libssl1.1), but one that is basically impossible to be without on a system.
Ack; nice catch; I missed that one.
> I don't think this fix is working, has anybody tried a focal build? The configure script is not being regenerated from configure.in and it still checks for the old function:
Yes, I've tested the changes in comment #14.
During that process I too noticed that _one_ of the configure checks uses the old function, but _another one_ uses the new; and the binary worked in the end, so it seemed OK.
That can be observed in the build log above as well:
$ curl -s https:/ /launchpadlibra rian.net/ 708828003/ focal_build. log | grep -n 'checking for .* in -lssl'
565:checking for SSL_library_init in -lssl... no
789:checking for OPENSSL_init_ssl in -lssl... yes
The first one is in dh_auto_configure, and the second one in dh_auto_build, which runs autoconf.