Feel free to close as not planned.
Les paquets suivants contiennent des dépendances non satisfaites :
jami-all : Dépend: libavcodec59 (>= 7:5.0) mais il n'est pas installable
Dépend: libavformat59 (>= 7:5.0) mais il n'est pas installable
E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
Directly from the official Release deb file:
sudo apt install ./jami-all_amd64.deb
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Vous pouvez lancer « apt --fix-broken install » pour corriger ces problèmes.
Les paquets suivants contiennent des dépendances non satisfaites :
jami-all : Dépend: libavcodec59 (>= 7:5.0) mais il n'est pas installable
Dépend: libavformat59 (>= 7:5.0) mais il n'est pas installable
E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
(ou indiquez une solution).
Install is OK and working but would need a updated machine (or via a single click), by default apt install ./foo.deb
will not update or try to fix dependencies.
For a one-click-install, you can rather:
apt --fix-broken install ./foo.bar
(because by default apt
will not try to update anything.gdebi ./foo.bar
because it will take care of the dependencies.Les paquets suivants contiennent des dépendances non satisfaites :
jami-all : Dépend: libavcodec59 (>= 7:5.0) mais il n'est pas installable
Dépend: libavformat59 (>= 7:5.0) mais il n'est pas installable
E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
Directly from the official Release deb file:
sudo apt install ./jami-all_amd64.deb
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Vous pouvez lancer « apt --fix-broken install » pour corriger ces problèmes.
Les paquets suivants contiennent des dépendances non satisfaites :
jami-all : Dépend: libavcodec59 (>= 7:5.0) mais il n'est pas installable
Dépend: libavformat59 (>= 7:5.0) mais il n'est pas installable
E: Dépendances non satisfaites. Essayez « apt --fix-broken install » sans paquet
(ou indiquez une solution).
Will be fixed for next nightly: https://review.jami.net/c/jami-daemon/+/26660
May I humbly request a new build for opensuse 15.5?
May I humbly request a new build for opensuse 15.5?
It would be great to see flatpak distribution to support more distros. While there seems to be a flatpak app on flathub, it doesn't seem to be verified with the developers of Jami & has not been listed on the site. Creating a flathub app would ensure reach in linux.
Jami (GNOME client)
at https://snapcraft.io/jami-gnome be removed?Snap for Jami (GNOME client) - managed by Savoir-faire Linux
snap install jami-gnome
Thank you
Still a project that can be updated by the community if wanted.
Jami (GNOME client)
at https://snapcraft.io/jami-gnome be removed?Snap for Jami (GNOME client) - managed by Savoir-faire Linux
snap install jami-gnome
Thank you
LMDE 6 “Faye” – BETA Release https://blog.linuxmint.com/?p=4562
Please add LMDE 6
“Faye” to https://jami.net/download-jami-linux/
LMDE 6 is based on Debian 12 Bookworm. https://linuxmint.com/rel_faye.php
Release edition status is shown at https://community.linuxmint.com/iso
Should LMDE 5 be removed when LMDE 6 is added?
Thank you
LMDE 6 “Faye” released! https://blog.linuxmint.com/?p=4570
LMDE 6 “Faye” – BETA Release https://blog.linuxmint.com/?p=4562
Please add LMDE 6
“Faye” to https://jami.net/download-jami-linux/
LMDE 6 is based on Debian 12 Bookworm. https://linuxmint.com/rel_faye.php
Release edition status is shown at https://community.linuxmint.com/iso
Should LMDE 5 be removed when LMDE 6 is added?
Thank you
Some customers have the requirement to use their own branding (white label).
This task is about to allow customizing the name (Jami) and icon logo.
Explore what is still missing.
Any help is appreciated
Note: not urgent
i see a document dated june '22. https://wiki.qt.io/Cross-Compile_Qt_6_for_Raspberry_Pi and Raspbian kernel moved from 5.15 to 6.1 https://9to5linux.com/latest-raspberry-pi-os-release-brings-linux-kernel-6-1-lts-chromium-113-and-more
Maybe crosscompiling improved in the meantime?
I'm trying to get Jami working on Arch Linux. I will explain the different scenarios I have tried below:
Installed the official jami-daemon
& jami-qt
packages using pacman. When I run Jami here, it starts up but then I get a Segmentation fault (core dumped)
when trying to create an account within the app.
Installed the Arch User Repo (AUR) package called jami-all-bin
. When I try to run Jami here, the system tells me I do not have a specific library available. I have looked around and the library provided by Arch is newer than what the pkg is asking for. I then changed that PKGBUILD and tried using different .deb files (Deb 11, Deb 10, Ubuntu 22.04, etc) and they all had different library requirements -- this AUR pkg is pulling the binary from the .deb file and then installing it on the system.
If I could better understand what needs to happen, then I believe I may be able to create a source based Arch package that work. Please help me out as I'd like to try out Jami and not being able to get it working is frustrating. Thanks.
Just published the jami-qt-wtf
package on AUR & can confirm that it is working!!! Thank you again @Vladimir for sharing those working commits.
Thanks for those working commits @Vladimir, as this will be helpful in getting Jami working for others on Arch. I started creating some unofficial packages on AUR with this info you've provided. I need to test these more and also create a replacement jami-qt
package as upstream's package doesn't work with my newly created packages called jami-daemon-wtf
and opendht-wtf
.