On 2017-08-26 16:44:34 [-0300], Lisandro Damián Nicanor Pérez Meyer wrote: > Hi! src:qt4-x11 is not listed in the transition but it's definitely using > libssl (although trough dllopen).
It is. The other qt-related bugs are: #828522 [i| |♔] [src:qt4-x11] qt4-x11: FTBFS with openssl 1.1.0 #859671 [i| |♔] [qtbase-opensource-src] qtbase-opensource-src: Please migrate to openssl1.1 in Buster #859673 [i| |♔] [qtwebsockets-opensource-src] qtwebsockets-opensource-src: Please migrate to openssl1.1 in Buster I see those bugs listed as blocker of this bug. > We have tried a patch proposed in #828522 but sadly whe where hit with: > > <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522#195> > > At this point we are back at stage 0, either: > > a) We remove SSL support letting lots of apps fail or silently use > unencrypted > connections. why silently? I would assume that if the SSL class is not availble that it won't compile or won't provide a connection at all (say khtml works only http then). > b) We remove Qt4 aling all their rdeps. > > Ideally (b) should happen before we release Buster, but I do realize it *will > be complicated*. (a) Would be a wonderful way towards achieving (a) actually. That qgis looks interresting. Do you want me to look at it or do prefer to use a) as motivation to get people to move to qt5? Sebastian
