FYI:
> % pacman -Ss jami
> galaxy/jami-daemon 20220722-5 (jami) [installed: 20220722-6]
> Free and universal communication platform which preserves the users’ privacy and freedoms (daemon component)
> community/jami-daemon 20220722-6 (jami) [installed]
> Free and universal communication platform which preserves the users’ privacy and freedoms (daemon component)
> community/jami-qt 20220726-1 (jami) [installed]
> Free and universal communication platform which preserves the users’ privacy and freedoms (Qt client)
You can see how, for some reason jami-daemon is included in "galaxy" repo, but jami-qt (or any other jami client) is not. This allows high chances that jami-qt from "arch/community" gets out of sync with jami-daemon, which provides "libjami.so*".
Currently, jami/jami-qt just fails, if one doesn't install "jami-daemon" from community:
> % jami
> jami-qt: symbol lookup error: /usr/lib/libjami.so.13: undefined symbol: _ZN3dht4http10Connection7timeoutENSt6chrono8durationIlSt5ratioILl1ELl1EEEESt8functionIFvRKSt10error_codeEE
I'm wondering why "galaxy" includes jami-daemon, but not jami-qt. It seems both have to be supported and have to be in sync, if to be included.
Current WA, while "jami-daemon" gets rebuilt, is to use the "arch/community" package:
> pacman -S jami-daemon=20220722-6
So, not a big issue, but I'm wondering what the intention is, to just include jami-daemon in "galaxy".
Regards !
--
Javier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.artixlinux.org/archives/artix-general/attachments/20221115/6356fbf8/attachment.sig>
More information about the artix-general
mailing list