(Replying from crappy web mail editor)
On 7 September 2017 at 13:25, Pino Toscano <p...@debian.org> wrote:
> (re-sending to the right ML)
> In data giovedì 7 settembre 2017 15:45:21 CEST, Maximiliano Curia ha scritto:
>> With the upload of qt4-x11 4:4.8.7+dfsg-12 (experimental) qt4 now builds
>> libssl-dev, instead of libssl1.0-dev. Lisandro pinged me by irc to upload a
>> newer kde4libs built against libssl-dev (and the newer qt4 version) in order
>> test this, but looking at the latests commits, it's clear that you have been
>> working in this package lately, and reading kdelibs4support thread you also
>> more aware of the issues that openssl 1.1 could produce. So it might be
>> if you could test this.
>> Please let me know if you prefer that I take care of this.
> I'm afraid neither kdelibs (4.x) nor kdelibs4support (5.x) nor
> khtml (5.x) were ported to OpenSSL >= 1.1, so not sure how switching
> build dependency would work.
I forgot to explicitly ping Maxy about this. The patch we had for Qt4
probed not to be enough. At this point whenever OpenSSL 1.0 gets
removed the only way forward we have is to remove SSL support from
qt4-x11. And yes, mayhem, because some packages will FTBFS, some other
will complain at run time and some other will probably even not
complain at all.
I asked Q about the removal timeframe and he said "sometime during the
Buster release cycle".
It is worth to note that Qt4-x11 is not tracked in the RT's tracker,
possibly because it's being DLLopened.
Lisandro Damián Nicanor Pérez Meyer