>> It seems easier to just disable deprecation warnings if you don't >> want to see them. > > As far as my understanding goes, "just disable deprication warning" it > is what commit 4d3db13621be64fbac2faf does.
But as stated above, there is no set of supported versions defined so there is definitive value we can set for OPENSSL_API_COMPAT in the backbranches. > Real fix would be rewrite corresponding parts of code so they wouldn't > use deprecated API. (as it was done with sha2 code in PostgreSQL 14. > which doesn't use openssl version of sha2 at all). That wouldn't help for 10-13 since that's a change unlikely to be back ported into a stable release. -- Daniel Gustafsson https://vmware.com/
