How can I install Jami Beta on FreeBSD in Ubuntu 20.04 chroot?

Hey,

I just downloaded two files

  1. jami_20210914.1.140151b~dfsg1-1_amd64.deb
  2. jami-all_20210914.1.140151b~dfsg1-1_amd64.deb

I tried to install it via

sudo apt install ./<file>

But it gives me errors like

root@alef14:~# apt install ./jami-all_20210914.1.140151b~dfsg1-1_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'jami-all' instead of './jami-all_20210914.1.140151b~dfsg1-1_amd64.deb'
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:
 jami-all : Depends: libwebpmux3 (>= 0.6.1-2ubuntu0.20.04.1) but 0.6.1-2 is to be installed
E: Unable to correct problems, you have held broken packages.

Could anyone provide a step by step instruction how to install Beta on FreeBSD in Ubuntu 20.04 chroot?

First, purge jami with # apt purge jami* in terminal or the “fix broken packages” option in Synaptic.

Try to install jami with # gdebi jami-all_20210914.1.140151b~dfsg1-1_amd64.deb

You can also go to the page Download Jami for GNU/Linux

You’ve got two choices

  1. Download an updated jami-all.deb file here https://dl.jami.net/ring-manual/ubuntu_20.04/jami-all_amd64.deb and install it with Gdebi (Gnome users) or Discover (KDE Plasma users).

  2. Copy and paste command lines in your terminal and run it. You may have to paste some times to run all. For Ubuntu 20.04 it’s on this page Download Jami for GNU/Linux

Thanks for guide.

Now, I’m getting

root@alef14:~# gdebi jami-all_20210914.1.140151b~dfsg1-1_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading state information... Done
This package is uninstallable
Dependency is not satisfiable: libwebpmux3 (>= 0.6.1-2ubuntu0.20.04.1)
root@alef14:~# sudo apt-get update && sudo apt-get install jami
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Get:2 https://dl.jami.net/nightly/ubuntu_20.04 jami InRelease [3596 B]
Get:3 https://dl.jami.net/nightly/ubuntu_20.04 jami/main amd64 Packages [3480 B]
Fetched 7076 B in 1s (7641 B/s)
Reading package lists... Done
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:
 jami : Depends: jami-libclient (= 20210914.1.140151b~dfsg1-1) but it is not going to be installed
        Depends: libqt-jami but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Maybe I’ll wait until it gets released. :slight_smile:

Wich results get the command

# apt-get --fix-broken
or
# apt-get --fix-broken jami
or
# apt-get --fix-broken jami-all
?

root@alef14:~# apt-get --fix-broken
E: Command line option --fix-broken is not understood in combination with the other options
root@alef14:~# apt-get --fix-broken jami
E: Command line option --fix-broken is not understood in combination with the other options
root@alef14:~# apt-get --fix-broken jami-all
E: Command line option --fix-broken is not understood in combination with the other options
root@alef14:~# apt-get --help
apt 2.0.2 (amd64)
Usage: apt-get [options] command
       apt-get [options] install|remove pkg1 [pkg2 ...]
       apt-get [options] source pkg1 [pkg2 ...]

apt-get is a command line interface for retrieval of packages
and information about them from authenticated sources and
for installation, upgrade and removal of packages together
with their dependencies.

Most used commands:
  update - Retrieve new lists of packages
  upgrade - Perform an upgrade
  install - Install new packages (pkg is libc6 not libc6.deb)
  reinstall - Reinstall packages (pkg is libc6 not libc6.deb)
  remove - Remove packages
  purge - Remove packages and config files
  autoremove - Remove automatically all unused packages
  dist-upgrade - Distribution upgrade, see apt-get(8)
  dselect-upgrade - Follow dselect selections
  build-dep - Configure build-dependencies for source packages
  satisfy - Satisfy dependency strings
  clean - Erase downloaded archive files
  autoclean - Erase old downloaded archive files
  check - Verify that there are no broken dependencies
  source - Download source archives
  download - Download the binary package into the current directory
  changelog - Download and display the changelog for the given package

See apt-get(8) for more information about the available commands.
Configuration options and syntax is detailed in apt.conf(5).
Information about how to configure sources can be found in sources.list(5).
Package and version choices can be expressed via apt_preferences(5).
Security details are available in apt-secure(8).
                                        This APT has Super Cow Powers.
root@alef14:~# apt-get update --fix-missing
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 https://dl.jami.net/nightly/ubuntu_20.04 jami InRelease
Reading package lists... Done
root@alef14:~# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@alef14:~# apt-get clean
root@alef14:~# apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Update:
Just noticed that Jami repo. is now visible, but still no luck

root@alef14:~# apt search jami|grep jami

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

jami/unknown 20210914.1.140151b~dfsg1-1 amd64
jami-all/unknown 20210914.1.140151b~dfsg1-1 amd64
jami-all-dbgsym/unknown 20210914.1.140151b~dfsg1-1 amd64
  debug symbols for jami-all
jami-daemon/unknown 20210914.1.140151b~dfsg1-1 amd64
jami-daemon-dbgsym/unknown 20210914.1.140151b~dfsg1-1 amd64
  debug symbols for jami-daemon
jami-dbgsym/unknown 20210914.1.140151b~dfsg1-1 amd64
  debug symbols for jami
jami-gnome/unknown 20210914.1.140151b~dfsg1-1 amd64
jami-gnome-dbgsym/unknown 20210914.1.140151b~dfsg1-1 amd64
  debug symbols for jami-gnome
jami-libclient/unknown 20210914.1.140151b~dfsg1-1 amd64
jami-libclient-dbgsym/unknown 20210914.1.140151b~dfsg1-1 amd64
  debug symbols for jami-libclient
jamin/focal 0.98.9~git20170111~199091~repack1-1 amd64
libqt-jami/unknown 5.15.2-1 amd64
  transitional package for jami
  transitional package for jami-daemon
root@alef14:~# apt install jami-all
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:
 jami-all : Depends: libwebpmux3 (>= 0.6.1-2ubuntu0.20.04.1) but 0.6.1-2 is to be installed
E: Unable to correct problems, you have held broken packages.

Hello,

Indeed, as @Firenze mentioned, you would either install jami-all which is an all-in-one package of several components of Jami and its Qt dependency, or install jami which will automatically pull in jami-daemon, jami-libclient, and libqt-jami as well.

I just tried on a fresh Ubuntu 20.04 setup and was able install both the jami-all deb or the jami packages separately without any issues. So I’m inclined to guess that either you may be holding some broken packages on your system, holding back the installation/upgrade of one of the packages Jami depends on, or added the repo for the wrong version of Ubuntu to your system (not the case if you indeed have Ubuntu 20.04, and the terminal output you showed indicates that you added the 20.04 repos). You could perhaps try following the guides online about fixing broken and/or missing packages using apt or apt-get.

If not that, based on this line in your output:

 jami-all : Depends: libwebpmux3 (>= 0.6.1-2ubuntu0.20.04.1) but 0.6.1-2 is to be installed

and a quick look at Ubuntu – Details of package libwebpmux3 in focal, my only other guess would be that you’re trying to install Jami on a non-amd64 architecture, however amd64 is currently the only architecture we provide packages for on dl.jami.net.

Ok, that makes sense, so let me recap it.

I have installed

root@alef14:/# apt show libwebpmux3/focal
Package: libwebpmux3
Version: 0.6.1-2

as you said, while I should have something more like

libwebpmux-3-0.6.1-2ubuntu0.20.04.1

Plus, again as you said, I use a different architecture (which I wasn’t aware before), this is

root@alef14:/# lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian

instead of

amd64

It’s because I run Ubuntu as Linux Compatibility Layer on FreeBSD, see

  1. https://wiki.freebsd.org/Linuxulator
  2. https://github.com/mrclksr/linux-browser-installer

This apparently makes difference.

I didn’t mention that earlier, because you can install Brave/Vivaldi browser or LBRY-Desktop app. as it’s regular Ubuntu (which I did).

The most important thing is we found the reason (thanks to @Firenze @bandali ).

I’ll update the title to reflect all the findings.

Thanks again!

UPDATE:
I can’t update the thread title. :frowning:

Hmm, actually it appears that your CPU architecture does match (that’s what I also get), but the issue may be nonstandard package versions because of the compatibility layer you mentioned. You should be able to rule out the architecture hypothesis using an Ubuntu VM or temporarily dual-booting it alongside your FreeBSD installation, if you’re interested in trying.

P.S. please see if you can edit the title now. :slightly_smiling_face:

I’ll check it with Ubuntu LiveUSB maybe, but I’m not sure if it’s necessary.
Because

  1. you checked it already
  2. working on LiveUSB preserves the installation broken on my regular OS :slight_smile:

Unfortunately, It still lacks.
Tho, I might see more options? Not sure if there were available before.

1 Like

Quite true :slight_smile:

Yeah it’s possible you may be seeing more options. I believe you should see the edit button now. I extended the period of time users can edit their post after sending it from one day to one week.

1 Like