In data martedì 17 aprile 2018 20:46:24 CEST, Emilio Pozuelo Monfort ha scritto: > ¡Hola Lisandro! > > On 25/02/18 17:40, Lisandro Damián Nicanor Pérez Meyer wrote: > > Hi Emilio! > > > > El 25 feb. 2018 7:00 a.m., "Emilio Pozuelo Monfort" <pochu@debian.org> > > escribió: > > > > Hi, > > > > On Thu, 12 Oct 2017 23:44:27 +0200 Sebastian Andrzej Siewior > > <sebastian@breakpoint.cc> wrote: > >> this is a remainder about the openssl transition [0]. We really want to > >> remove libssl1.0-dev from unstable for Buster. I will raise the severity > >> of this bug to serious in a month. Please react before that happens. > > It looks like kopete only wants openssl for jingle support in XMPP. Can you > > temporarily disable that, and forward this bug upstream so they add support > > for > > openssl 1.1? > > > > > > I haven't checked, but maybe it depends on qt itself. If that's the case > > then waiting upon qt 5.10 might be the best thing here. We are not that far > > from asking a transition for it. > > > > Of course If that's not the case then it's a possibility. > > Now that we have Qt 5.10 in sid, can you check if kopete can be built with > OpenSSL 1.1? Otherwise, disabling jingle could solve this for the time being. The version of openssl used to build Qt is irrelevant for the jingle code that uses openssl directly; nobody did anything about that, so the status is the same as before. If the openssl maintainers want to get rid of openssl 1.0, why don't they *cooperate* with *upstream* communities on the migration to the newer version of openssl? That would certainly help, and surely way more than useless "please migrate, ktnxbye" nagging. -- Pino Toscano
Attachment:
signature.asc
Description: This is a digitally signed message part.