Bug#828363: kde4libs: FTBFS with openssl 1.1.0

On 11/24/2016 05:58 PM, Lisandro Damián Nicanor Pérez Meyer wrote: > According to what I've read in yesterday's RT's irc meeting switching to > libssl1.0-dev is the way to go. Good to know. Is there some official transcript which one could reference when proposing an NMU? There is, for example,

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

On martes, 22 de noviembre de 2016 11:43:23 ART Maximiliano Curia wrote: > Control: tag -1 + pending > > ¡Hola Scott! > > El 2016-11-18 a las 20:18 -0500, Scott Kitterman escribió: > > On November 18, 2016 7:37:31 PM EST, John Paul Adrian Glaubitz wrote: > >> Hi!

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

Control: tag -1 + pending ¡Hola Scott! El 2016-11-18 a las 20:18 -0500, Scott Kitterman escribió: On November 18, 2016 7:37:31 PM EST, John Paul Adrian Glaubitz wrote: Hi! Would it be possible to change the build dependency from libssl-dev to libssl1.0-dev

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

On November 18, 2016 7:37:31 PM EST, John Paul Adrian Glaubitz wrote: >Hi! > >Would it be possible to change the build dependency from libssl-dev to >libssl1.0-dev for the time being to temporarily resolve this issue? > >It's rather ugly to have a library as

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

Hi! Would it be possible to change the build dependency from libssl-dev to libssl1.0-dev for the time being to temporarily resolve this issue? It's rather ugly to have a library as central as kde4libs FTBFS because it blocks archive rebuilds or the bootstrapping of new architectures. Thanks,

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

Source: kde4libs Version: 4.14.20-2 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: