Bug#828252: qtcreator is marked for autoremoval from testing

[Ondřej Surý]

In the end it was very easy (hopefully) - the OpenSSL module is optional
and hopefully this won't break anything :). Ccing other botan1.10 users.

Please test with botan1.10 - 1.10.13-1 that just got uploaded to
unstable.

Cheers,
-- 
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Thu, Oct 27, 2016, at 21:20, Adam Majer wrote:
> On 27/10/16 09:59 AM, Ondřej Surý wrote:
> > I can probably generate two sets of packages with versioned symbols
> > if I have some help with that.
> >
> > Cheers,
> >
> 
> Yes, but this will not help and I'm not sure it is required since 
> OpenSSL is versioned already.
> 
> The problem is that Qt5 is using dlopen for OpenSSL. Versioned symbols 
> are not used with dlopen as is so we are SOL. Either Qt5 needs to be 
> linked directly against OpenSSL, or Qt5 needs to use symbols from old 
> OpenSSL library.
> 
> And now I'm looking at Qt source, and it looks like for Qt5 it is 
> possible to specify SHLIB version number for OpenSSL. see
> 
>     qtbase/src/network/ssl/qsslsocket_openssl_symbols.cpp line 653
> 
> which means it *may be* possible to have multiple OpenSSL versions 
> installed and have Qt use only the old version. But this needs to be 
> tested with some test application to make sure correct functions are 
> actually called.
> 
> SHLIB_VERSION_NUMBER = 1.0.2
> 
> during compilation of Qt maybe all that is required to keep Qt crypto 
> support working in a mixed environment.
> 
> - Adam