Package: libolm3
Version: 3.2.1~dfsg-7
Severity: normal
Dear Maintainer,
there is an issue [1] with private symbols being exported which can
lead to
symbols conflicting with other libraries or applications.
There is a fix available upstream [2] and on salsa [3].
We've run into this issue with chatty[4], which leads to segmentation
faults.
Since the affected chatty version has not made it into bullseye and
no other user of libolm{3,-dev} seems to have run into this problem
I guess "normal" priority is appropriate (?)
[1] https://github.com/matrix-org/olm/issues/47
[2]
https://gitlab.matrix.org/matrix-org/olm/-/commit/1b7973626e27beb05a55df6085f643a1323db987
[3] https://salsa.debian.org/matrix-team/olm/-/merge_requests/1
[4] https://source.puri.sm/Librem5/chatty/-/issues/450
-- System Information:
Debian Release: 11.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500,
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-7-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libolm3 depends on:
ii libc6 2.31-12
ii libstdc++6 10.2.1-6
libolm3 recommends no packages.
libolm3 suggests no packages.
-- no debconf information
--
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19
