On jueves, 21 de septiembre de 2017 21:32:34 -03 Sebastian Andrzej Siewior wrote: > 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
Just this one, the others are Qt5 and should be sorted out hopefully in Qt 5.10. [snip] > > 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). Because developers. Yes, the API will certainly complain, but one can not assume that every developer will take that complain seriously. > > 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? It really depends on when the OpenSSL 1.0 removal will really take place. If it's by january 2018 then we are fine because: - Maintainers will be forced to move or remove packages, with enough time to make their packages re enter the archive is possible. - Users will still be able to use the needed apps through stable (even if they use testing). -- En los momentos de crisis, la imaginación es mas importante que el conocimiento. Albert Einstein Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
