[jitsi-users] install attempt on 2017-01-17


#1

Hi,

This a report about an attempt to install Jitsi.

It describes what happened to this new comer to Jitsi. Please read it
with "What could the Jitsi project do better?" in mind.

Visiting https://jitsi.org/Main/Download says there is a Debian package.

At https://download.jitsi.org/stable/ are _several_ packages.

There was no 'jitsi', "jitsi_VERSION_ARCH.deb" package.

I picked 'jitsi-meet_1.0.1622-1_all.deb' because it was closest
to a "toplevel jitsi package" I was looking for.

$ sudo dpkg --install jitsi-meet_1.0.1622-1_all.deb
(Reading database ... 139646 files and directories currently installed.)
Preparing to unpack jitsi-meet_1.0.1622-1_all.deb ...
Unpacking jitsi-meet (1.0.1622-1) over (1.0.1622-1) ...
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-videobridge (= 879-1); however:
  Package jitsi-videobridge is not installed.
jitsi-meet depends on jicofo (= 1.0-320-1); however:
  Package jicofo is not installed.
jitsi-meet depends on jitsi-meet-web (= 1.0.1592-1); however:
  Package jitsi-meet-web is not installed.
jitsi-meet depends on jitsi-meet-web-config (= 1.0.1592-1); however:
  Package jitsi-meet-web-config is not installed.
jitsi-meet depends on jitsi-meet-prosody (= 1.0.1592-1); however:
  Package jitsi-meet-prosody is not installed.

dpkg: error processing package jitsi-meet (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
jitsi-meet

All those dependencies pushed me to what I wanted
to avoid: adding a none Debian repository

At https://jitsi.org/Main/DebianRepository is this text:

To use our debian/ubuntu repository (deb http://download.jitsi.org/deb
unstable/) just download and install Jitsi's deb package. It will
automatically add our repository to your system so that it will keep
Jitsi up to date. Next time you upgrade your system, Jitsi will be
automatically updated to its latest version.

Note that you SHOULD NOT manually add Jitsi to your sources list
because that would cause GPG Error Warnings! The Jitsi installation
would automatically update your repositories.

The "just download and install Jitsi's deb package" was allready tried.

So adding manually jitsi to my sources list

$ cat /etc/apt/sources.list.d/jitsi.list

deb http://download.jitsi.org/deb unstable/

#

GPG key stuff

$ wget -qO jitsi.key https://download.jitsi.org/jitsi-key.gpg.key
$ gpg --import jitsi.key
gpg: key EF8B479E2DC1389C: public key "Jitsi <dev@jitsi.org>" imported
gpg: Total number processed: 1
gpg: imported: 1
$ gpg --import jitsi.key
gpg: key EF8B479E2DC1389C: "Jitsi <dev@jitsi.org>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
$ gpg --list-sigs EF8B479E2DC1389C
pub rsa4096 2016-06-23 [SC]
      66A9CD0595D6AFA247290D3BEF8B479E2DC1389C
uid [ unknown] Jitsi <dev@jitsi.org>
sub rsa4096 2016-06-23 [E]

$

I would expect more signatures on that key.

But hey, I was willing to take the risk and did

$ cat jitsi.key | sudo apt-key add -
OK

My `sudo apt update` got me a "NO_PUBKEY C697D823EB0AB654"

So I did

$ gpg --recv-key C697D823EB0AB654
gpg: key C697D823EB0AB654: "SIP Communicator (Debian package) <deb-pkg@sip-communicator.org>" 1 new signature
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2017-07-08
gpg: Total number processed: 1
gpg: new signatures: 1

Then I was unhappy surprised by:

$ gpg --list-key C697D823EB0AB654
pub dsa1024 2008-06-20 [SC]
      040F57608F84BAF1BF844A62C697D823EB0AB654
uid [ unknown] SIP Communicator (Debian package) <deb-pkg@sip-communicator.org>
sub elg2048 2008-06-20 [E]

Yes, a 1024-bit key is being used.
But I imported it.

Then another `apt update` that did bring me

W: http://download.jitsi.org/deb/unstable/Release.gpg: Signature by key 040F57608F84BAF1BF844A62C697D823EB0AB654 uses weak digest algorithm (SHA1)

That "weak digest algorithm" was the point where I stopped installing Jitsi,
infact stopped _trying_ to install Jitsi.

I hope that this posting results in a better install exprience for new users.

Groeten
Geert Stappers

···

sig 3 EF8B479E2DC1389C 2016-06-23 Jitsi <dev@jitsi.org>
sig EF8B479E2DC1389C 2016-06-23 Jitsi <dev@jitsi.org>

--
Leven en laten leven


#2

Hi,

Looking at your mail I assume you want to install jitsi-meet, so going
to https://jitsi.org/Main/Download there is a section about installing
jitsi-meet and unsing the debian/ubuntu repo which leads you to a
page: https://jitsi.org/Main/InstallJitsiMeetDebianStableRepository.
Which has 3 steps:
- downloading the key https://download.jitsi.org/jitsi-key.gpg.key
(which is by the way 4096-bit key).
- add the repo which is: deb https://download.jitsi.org stable/
- and installing the package

You were using the old repo and old key, which we are migrating and is
only currently used for the desktop client, which will no longer be
the case soon. And that repo and instructions will disappear.

Hope this clears the things a bit and helps.

Regards
damencho

···

On Fri, Jan 20, 2017 at 4:49 PM, Geert Stappers <stappers@stappers.nl> wrote:

Hi,

This a report about an attempt to install Jitsi.

It describes what happened to this new comer to Jitsi. Please read it
with "What could the Jitsi project do better?" in mind.

Visiting https://jitsi.org/Main/Download says there is a Debian package.

At https://download.jitsi.org/stable/ are _several_ packages.

There was no 'jitsi', "jitsi_VERSION_ARCH.deb" package.

I picked 'jitsi-meet_1.0.1622-1_all.deb' because it was closest
to a "toplevel jitsi package" I was looking for.

> $ sudo dpkg --install jitsi-meet_1.0.1622-1_all.deb
> (Reading database ... 139646 files and directories currently installed.)
> Preparing to unpack jitsi-meet_1.0.1622-1_all.deb ...
> Unpacking jitsi-meet (1.0.1622-1) over (1.0.1622-1) ...
> dpkg: dependency problems prevent configuration of jitsi-meet:
> jitsi-meet depends on jitsi-videobridge (= 879-1); however:
> Package jitsi-videobridge is not installed.
> jitsi-meet depends on jicofo (= 1.0-320-1); however:
> Package jicofo is not installed.
> jitsi-meet depends on jitsi-meet-web (= 1.0.1592-1); however:
> Package jitsi-meet-web is not installed.
> jitsi-meet depends on jitsi-meet-web-config (= 1.0.1592-1); however:
> Package jitsi-meet-web-config is not installed.
> jitsi-meet depends on jitsi-meet-prosody (= 1.0.1592-1); however:
> Package jitsi-meet-prosody is not installed.
>
> dpkg: error processing package jitsi-meet (--install):
> dependency problems - leaving unconfigured
> Errors were encountered while processing:
> jitsi-meet

All those dependencies pushed me to what I wanted
to avoid: adding a none Debian repository

At https://jitsi.org/Main/DebianRepository is this text:

> To use our debian/ubuntu repository (deb http://download.jitsi.org/deb
> unstable/) just download and install Jitsi's deb package. It will
> automatically add our repository to your system so that it will keep
> Jitsi up to date. Next time you upgrade your system, Jitsi will be
> automatically updated to its latest version.
>
> Note that you SHOULD NOT manually add Jitsi to your sources list
> because that would cause GPG Error Warnings! The Jitsi installation
> would automatically update your repositories.

The "just download and install Jitsi's deb package" was allready tried.

So adding manually jitsi to my sources list

>$ cat /etc/apt/sources.list.d/jitsi.list
>
>deb http://download.jitsi.org/deb unstable/
>
>#

GPG key stuff
> $ wget -qO jitsi.key https://download.jitsi.org/jitsi-key.gpg.key
> $ gpg --import jitsi.key
> gpg: key EF8B479E2DC1389C: public key "Jitsi <dev@jitsi.org>" imported
> gpg: Total number processed: 1
> gpg: imported: 1
> $ gpg --import jitsi.key
> gpg: key EF8B479E2DC1389C: "Jitsi <dev@jitsi.org>" not changed
> gpg: Total number processed: 1
> gpg: unchanged: 1
> $ gpg --list-sigs EF8B479E2DC1389C
> pub rsa4096 2016-06-23 [SC]
> 66A9CD0595D6AFA247290D3BEF8B479E2DC1389C
> uid [ unknown] Jitsi <dev@jitsi.org>
> sig 3 EF8B479E2DC1389C 2016-06-23 Jitsi <dev@jitsi.org>
> sub rsa4096 2016-06-23 [E]
> sig EF8B479E2DC1389C 2016-06-23 Jitsi <dev@jitsi.org>
>
> $

I would expect more signatures on that key.

But hey, I was willing to take the risk and did

>$ cat jitsi.key | sudo apt-key add -
>OK

My `sudo apt update` got me a "NO_PUBKEY C697D823EB0AB654"

So I did
> $ gpg --recv-key C697D823EB0AB654
> gpg: key C697D823EB0AB654: "SIP Communicator (Debian package) <deb-pkg@sip-communicator.org>" 1 new signature
> gpg: marginals needed: 3 completes needed: 1 trust model: pgp
> gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
> gpg: next trustdb check due at 2017-07-08
> gpg: Total number processed: 1
> gpg: new signatures: 1

Then I was unhappy surprised by:
> $ gpg --list-key C697D823EB0AB654
> pub dsa1024 2008-06-20 [SC]
> 040F57608F84BAF1BF844A62C697D823EB0AB654
> uid [ unknown] SIP Communicator (Debian package) <deb-pkg@sip-communicator.org>
> sub elg2048 2008-06-20 [E]

Yes, a 1024-bit key is being used.
But I imported it.

Then another `apt update` that did bring me

W: http://download.jitsi.org/deb/unstable/Release.gpg: Signature by key 040F57608F84BAF1BF844A62C697D823EB0AB654 uses weak digest algorithm (SHA1)

That "weak digest algorithm" was the point where I stopped installing Jitsi,
infact stopped _trying_ to install Jitsi.

I hope that this posting results in a better install exprience for new users.

Groeten
Geert Stappers
--
Leven en laten leven

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

>
> Hi,
>
> This a report about an attempt to install Jitsi.
>
> It describes what happened to this new comer to Jitsi. Please read it
> with "What could the Jitsi project do better?" in mind.
>
>
> Visiting https://jitsi.org/Main/Download says there is a Debian package.
>
> At https://download.jitsi.org/stable/ are _several_ packages.
>
> There was no 'jitsi', "jitsi_VERSION_ARCH.deb" package.
>
> I picked 'jitsi-meet_1.0.1622-1_all.deb' because it was closest
> to a "toplevel jitsi package" I was looking for.
>

Hi,

Looking at your mail I assume you want to install jitsi-meet,

AFAIK is 'jitsi-meet' a "chat server".

What I'm looking for is a SIP client.

At https://jitsi.org there four "buttons"
* Jitsi-meet
* Jitsi
* Jitsi-videobridge
* Libjitsi

That is why I'm reporting

> There was no 'jitsi', "jitsi_VERSION_ARCH.deb" package.

so going to https://jitsi.org/Main/Download there is a section about
installing jitsi-meet and unsing the debian/ubuntu repo which leads
you to a page:
https://jitsi.org/Main/InstallJitsiMeetDebianStableRepository.
Which has 3 steps:
- downloading the key https://download.jitsi.org/jitsi-key.gpg.key
- add the repo which is: deb https://download.jitsi.org stable/
- and installing the package

root@june:~# apt-get install jitsi
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package jitsi
root@june:~# aptitude install jitsi
Couldn't find package "jitsi". However, the following
packages contain "jitsi" in their name:
  jitsi-meet-web jitsi-meet jitsi-videobridge jitsi-videobridge:i386 jitsi-meet-web-config
  jitsi-meet-tokens jitsi-archive-keyring jitsi-meet-prosody
Couldn't find package "jitsi". However, the following
packages contain "jitsi" in their name:
  jitsi-meet-web jitsi-meet jitsi-videobridge jitsi-videobridge:i386 jitsi-meet-web-config
  jitsi-meet-tokens jitsi-archive-keyring jitsi-meet-prosody
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1135 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
root@june:~#

Where to find a jitsi package that has a SIP client?

Groeten
Geert Stappers

···

On Fri, Jan 20, 2017 at 11:23:15PM -0600, Damian Minkov wrote:

On Fri, Jan 20, 2017 at 4:49 PM, Geert Stappers <stappers@stappers.nl> wrote:

--
Leven en laten leven


#4

Hi,

The jitsi desktop is a sip client and its stable packages are still
using the old repo with the old key so we do not break current
deployments, so they can update to the new version once it is
released:
https://jitsi.org/Main/DebianRepository

The nightly builds are using the new repo and the new key:
https://jitsi.org/Main/DebianNightlyRepository

Once we update the stable desktop client it will move to the new repo
and key and the old repo will be removed, in other words we are
currently in transition period there and it will soon end.

Regards
damencho

···

On Tue, Jan 24, 2017 at 10:08 AM, Geert Stappers <stappers@stappers.nl> wrote:

On Fri, Jan 20, 2017 at 11:23:15PM -0600, Damian Minkov wrote:

On Fri, Jan 20, 2017 at 4:49 PM, Geert Stappers <stappers@stappers.nl> wrote:
>
> Hi,
>
> This a report about an attempt to install Jitsi.
>
> It describes what happened to this new comer to Jitsi. Please read it
> with "What could the Jitsi project do better?" in mind.
>
>
> Visiting https://jitsi.org/Main/Download says there is a Debian package.
>
> At https://download.jitsi.org/stable/ are _several_ packages.
>
> There was no 'jitsi', "jitsi_VERSION_ARCH.deb" package.
>
> I picked 'jitsi-meet_1.0.1622-1_all.deb' because it was closest
> to a "toplevel jitsi package" I was looking for.
>

Hi,

Looking at your mail I assume you want to install jitsi-meet,

AFAIK is 'jitsi-meet' a "chat server".

What I'm looking for is a SIP client.

At https://jitsi.org there four "buttons"
* Jitsi-meet
* Jitsi
* Jitsi-videobridge
* Libjitsi

That is why I'm reporting

> There was no 'jitsi', "jitsi_VERSION_ARCH.deb" package.

so going to https://jitsi.org/Main/Download there is a section about
installing jitsi-meet and unsing the debian/ubuntu repo which leads
you to a page:
https://jitsi.org/Main/InstallJitsiMeetDebianStableRepository.
Which has 3 steps:
- downloading the key https://download.jitsi.org/jitsi-key.gpg.key
- add the repo which is: deb https://download.jitsi.org stable/
- and installing the package

root@june:~# apt-get install jitsi
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package jitsi
root@june:~# aptitude install jitsi
Couldn't find package "jitsi". However, the following
packages contain "jitsi" in their name:
  jitsi-meet-web jitsi-meet jitsi-videobridge jitsi-videobridge:i386 jitsi-meet-web-config
  jitsi-meet-tokens jitsi-archive-keyring jitsi-meet-prosody
Couldn't find package "jitsi". However, the following
packages contain "jitsi" in their name:
  jitsi-meet-web jitsi-meet jitsi-videobridge jitsi-videobridge:i386 jitsi-meet-web-config
  jitsi-meet-tokens jitsi-archive-keyring jitsi-meet-prosody
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1135 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
root@june:~#

Where to find a jitsi package that has a SIP client?

Groeten
Geert Stappers
--
Leven en laten leven

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#5

>
> root@june:~# apt-get install jitsi
> E: Unable to locate package jitsi
>
> Where to find a jitsi package that has a SIP client?
>

Hi,

Hello Damian, (Hello Mailinglist,)

In "Packages" file I found

Package: jitsi
Priority: optional
Section: net
Installed-Size: 64910
Maintainer: Damian Minkov <damencho@jitsi.org>

that is nice to see.

The jitsi desktop is a sip client and its stable packages are still
using the old repo with the old key so we do not break current
deployments, so they can update to the new version once it is
released:
https://jitsi.org/Main/DebianRepository

The nightly builds are using the new repo and the new key:
https://jitsi.org/Main/DebianNightlyRepository

Once we update the stable desktop client it will move to the new repo
and key and the old repo will be removed, in other words we are
currently in transition period there and it will soon end.

I don't about "old" and "new", it is all new to me.

I did follow the instructions from https://jitsi.org/Main/DebianNightlyRepository
So I have 'deb https://download.jitsi.org unstable/' in apt sources. Key is inplace
and `apt-get update` is done.

After `apt-get install jitsi`,`apt-get install -f` another `apt-get install jitsi`
did I get jitsi installed. \o/

So now my screen:

root@june:~# apt-get install jitsi
Reading package lists... Done
Building dependency tree
Reading state information... Done
jitsi is already the newest version (2.9.5544-1).
0 upgraded, 0 newly installed, 0 to remove and 143 not upgraded.
root@june:~#

Thanks

Now up to actual using Jitsi.

Groeten
Geert Stappers

···

On Tue, Jan 24, 2017 at 10:38:39AM -0600, Damian Minkov wrote:

On Tue, Jan 24, 2017 at 10:08 AM, Geert Stappers <stappers@stappers.nl> wrote:

--
Leven en laten leven