I know compat-openssl10-devel mentions: # The devel subpackage intentionally conflicts with main openssl-devel # as simultaneous use of both openssl package cannot be encouraged. # Making the packages non-conflicting would also require further # changes in the dependent packages. Conflicts: openssl-devel kde-sig currently have (almost) our entire software stack of blocking on this currently. Qt5 is (hopefully) fixed as of today, but much legacy software (including Qt4) still FTBFS against openssl-1.1. Couple this with a few -devel items in the software stack that currently: Requires: openssl-devel (like mariadb-devel), and we have a much bigger FTBFS problem Now, if this legacy compat package cannot or will not move headers, then maybe the newer openssl-1.1 one can and should.
See also related mariadb bug #1400233
I am sorry, but no, I am not going to move the openssl-1.1 headers and promote the use of compat-openssl10.
I'm sorry too, I didn't have to expect to raise this to FESCo
Unless, do you have some other reasonable compromise for fixing all the not-yet-ported-to-openssl-1.1 packages?
Can you please come up with a list of the packages where the conflicts prevents them from rebuilding?
Also btw - without full namespacing of the API symbols in includes the -devel packages really conflict and just moving the files around does not really fix this conflict. Yes, in practice it might sometimes work but there is no guarantee.
Currently the list includes only what BuildRequires: mariadb-devel (which includes qt and everything that depends on it), but that appears to be close to being resolved via bug #1400233