Hi Tobias, Thanks for tackling this. I'm a bit busy last week due to Linaro connect. And yes as you described, telegram-cli seems still needs the header of SSL to be compiled. I use wolfssl completely due to the license issue.
I've also tried to backport the patch for wolfssl but it seems to me that it is not a trivial one. We might need to bump the version of wolfssl. But since we are in freeze, so bumping the version seems not good. So maybe we need to remove telegram-cli from testing. I mean exclude telegram-cli in buster release. And include it back in buster+1. Yours, Paul On Sat, Apr 6, 2019 at 3:42 AM Tobias Frost <t...@debian.org> wrote: > On Wed, 3 Apr 2019 22:16:23 +0500 Andrey Rahmatullin <w...@debian.org> > wrote: > > libwolfssl was removed from testing due to #918952. > > The shared lib was removed but this package was not, because it > doesn't > > depend on the lib. Maybe the B-D can be safely removed. > > Checked, will FTBFS when done… > It will likely build with openssl (not tried), but the source code is > GPL2.0 without an OpenSSL license exception... > I asked upstream to add such an exception in > https://github.com/vysheng/tg/issues/1591 > > > > -- > > WBR, wRAR >
