Hi,
according to https://tracker.debian.org/pkg/telegram-cli, telegram-cli
is threatened to be removed from testing due to an RC bug in the
wolfssl source package. But at least in the resulting binary package,
I see no relation to wolfssl, not even indirectly via libtgl.
The only occurrences of wolfssl in the telegram-cli source package
seem in the Debian packaging:
[…]it20160323.6547c0b21 → fgrep -r wolf
debian/rules: dh_auto_configure -- --disable-openssl
OPENSSL_INCLUDES="-I/usr/include/wolfssl -DWC_NO_HARDEN"
debian/control: libwolfssl-dev,
But the resulting package does not have any dependency on wolfssl:
$ apt-cache show telegram-cli | fgrep wolf
$ apt-cache show telegram-cli | fgrep ssl
$
Neither does so libtgl — in contrary, it depends on OpenSSL libraries:
$ apt-cache show libtgl-0.0.0.20160623-0 | fgrep wolf
$ apt-cache show libtgl-0.0.0.20160623-0 | fgrep ssl
Depends: libc6 (>= 2.17), libevent-2.1-7 (>= 2.1.8-stable), libssl1.1 (>=
1.1.0), zlib1g (>= 1:1.1.4)
same time - your messages sync seamlessly across any number of your phones,
$
So IMHO the wolfssl configure options and the build-dependency on
wolfssl actually _must_ be removed as the configure option seems to
have no effect and the build-dependency is not used and hence
unnecessary and (at least with regards to potential testing removal)
even harmful.
I actually wonder if this build-dependency stems from a time before
telegram-cli was build without libtgl and was just forgotten to be
removed.
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
