jitsi-meet unmet package dependencies Ubuntu 18.04 LTS
See original GitHub issueThis Issue tracker is only for reporting bugs and tracking code related issues.
Before posting, please make sure you check community.jitsi.org to see if the same or similar bugs have already been discussed. General questions, installation help, and feature requests can also be posted to community.jitsi.org.
Description
apt on fresh ubuntu 18.04 cant install jitsi
Current behavior
When trying to install jitsi following the steps at https://jitsi.org/downloads/ using the repositories apt fails with this message:
root@ip-172-31-35-171:/home/ubuntu# sudo apt-get -y install jitsi-meet
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
jitsi-meet : PreDepends: jitsi-videobridge2 (= 2.1-169-ga28eb88e-1) but it is not going to be installed
Recommends: jitsi-meet-turnserver (= 1.0.3992-1) but it is not going to be installed or
apache2 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Expected Behavior
The same instructions worked a few days ago when I setup a test server. Same OS.
Possible Solution
Provide the required version of jitsi-videobridge2 over the package repository
Steps to reproduce
1 ) Setup a EC2 t2.small instance with Ubuntu 18.04 (Marketplace Version)
2) wget -qO - https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add -
3) sudo sh -c "echo 'deb https://download.jitsi.org stable/' > /etc/apt/sources.list.d/jitsi-stable.list"
4) sudo apt-get -y update
5) sudo apt-get -y install jitsi-meet
Environment details
OS: Ubuntu 18.04.3 LTS universe distribution component was activated
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (10 by maintainers)
Top GitHub Comments
Can someone do
Does it work now?
Just tried to do an install on the same version of Ubuntu server and got the same result. I can also confirm it did work a few days ago when I installed on another server.
To fix: