[jitsi-users] Jitsi Desktop 2.10 released


#1

Hello everyone

Over the last weekend at FOSDEM we prepared the last bits for the release of
Jitsi Desktop 2.10. It is now available for download at
https://download.jitsi.org. Existing Mac and Windows users should receive an
upgrade notification, Linux users should update using their package manager.

The following release notes lists the most important changes, but the list
is by no means complete.

Release Notes 2.10

···

==================
General:
- Log DNS queries in packet log
- Option to disable popups
- Updated translations
- Database based configuration service enabled by default (switch back to
properties file based configuration by creating ~/.jitsi/.usepropfileconfig)
- Binaries signed with SHA256 by Ingo Bauersachs reflecting the community
maintenance
- Improved add contact dialog
- DNSSEC validation based on dnssecjava
- Improved IPv6 handling
- Draggable call window
- Fix treating a new ZRTP ID as a mismatch
- Show SHA256 fingerprint when encoutering untrusted certificates
- Update embedded JRE to 1.8.121

Operating Systems
-----------------
Windows:
- Support for Office 2016
- Removed support for Office 2003/2007
- Support for Windows 10 default application list
- Support for more webcams, e.g. ManyCam virtual camera
- Sanitize filename in incoming file transfers

Linux:
- Tray icon disabled by default, support for AppIndicator if enabled in
options
- Fixed crash when switching consoles, enabling screensaver, etc.

Mac:
- Support for tel: and callto: URIs

Protocols
---------
Removed:
- Yahoo!, the network doesn't exist anymore
- Facebook, doesn't allow XMPP connections anymore
- MSN, the network doesn't exist anymore

IRC:
- Realtime contact updates
- Some support for IRC v3.1
- SASL authentication
- Proxy support

XMPP:
- Improved handling of xmpp: URIs
- Querying of Google Contacts with OAuth2
- Fix CVE-2017-5603

SIP:
- New Busy Lamp Field plugin to monitor lines on a PBX
- Fix display name field in SIP account wizard
- Option to disable proxy filter for HA environments
- New SDES ciphers
- Allow to add SIP contacts with spaces in their phone number
- Support for domains that have NAPTR records for other protocols than SIP

ICQ:
- Remove 8-character password limitation

Best regards,
Ingo


#2

Hi,
how do i verify my download?
The signing is different this time. It's not "blueJimp" anymore.
maybe you could announce that it's signed from now and on by Ingo (is it?)
on the jitsi website.
verifying the download is crucial for some folks...you know.


#3

The following release notes lists the most important changes, but the list
is by no means complete.

This software evolution sounds promising. I would like to try it also out
on my openSUSE Tumbleweed system.

Sonne:~ # zypper install https://download.jitsi.org/jitsi/rpm/jitsi-2.10-5550.x86_64.rpm

Problem: nothing provides libXScrnSaver needed by jitsi-2.10-5550.x86_64

Does this software package refer to a library name which can only be resolved
for Fedora system variants so far?
How do you think about an alternative like “libXss1”?

Regards,
Markus


#4

Hi,
how do i verify my download?

Look at the certificate.

The signing is different this time. It's not "blueJimp" anymore.
maybe you could announce that it's signed from now and on by Ingo (is it?) on
the jitsi website.

Read the release notes. It's clearly stated there.

verifying the download is crucial for some folks...you know.

Ingo


#5

The following release notes lists the most important changes, but the list
is by no means complete.

This software evolution sounds promising. I would like to try it also out
on my openSUSE Tumbleweed system.

Sonne:~ # zypper install
https://download.jitsi.org/jitsi/rpm/jitsi-2.10- 5550.x86_64.rpm …
Problem: nothing provides libXScrnSaver needed by jitsi-2.10-5550.x86_64

https://software.opensuse.org/package/libXScrnSaver

Does this software package refer to a library name which can only be resolved
for Fedora system variants so far?

I don't know. As per the above link, it should be available on Tumbleweed.

How do you think about an alternative like “libXss1”?

I'm not sure if libXss1 provides the necessary entry points. If it is, sure, but I don't know to set an or-dependency in an RPM spec. AFAIK this has only been added very recently in Fedora.

I guess this particular library could be optional. If it is missing, the auto-away doesn't work.

Regards,
Markus

Ingo


#6

As per the above link, it should be available on Tumbleweed.

This identifier refers to data of the type “srcpackage”.

https://build.opensuse.org/package/view_file/openSUSE:Factory/libXScrnSaver/libXScrnSaver.spec?expand=1

I'm not sure if libXss1 provides the necessary entry points.

I hope so as the summary is the same: X11 Screen Saver extension client library.

If it is, sure, but I don't know to set an or-dependency in an RPM spec.

Is it possible to work with an alias there?

Regards,
Markus


#7

As per the above link, it should be available on Tumbleweed.

This identifier refers to data of the type “srcpackage”.

https://build.opensuse.org/package/view_file/openSUSE:Factory/libXScrnSav
er/l ibXScrnSaver.spec?expand=1

Argh. What kind of crap is that? One distro has the same source/binary package names, the other doesn't!?

I'm not sure if libXss1 provides the necessary entry points.

I hope so as the summary is the same: X11 Screen Saver extension client
library.

If it is, sure, but I don't know to set an or-dependency in an RPM spec.

Is it possible to work with an alias there?

I'm really far away from being an expert with .spec files. If you are, could you please suggest the required changes to our source spec?

https://github.com/jitsi/jitsi/blob/master/resources/install/rpm/SPECS/jitsi.spec

Regards,
Markus

Thanks,
Ingo


#8

One distro has the same source/binary package names, the other doesn't!?

Have you got any helpful contacts to packagers for further clarification
of the corresponding name selection?

Regards,
Markus


#9

One distro has the same source/binary package names, the other doesn't!?

How do you think about to work with additional checks and package name substitutions
also in your RPM specification?
https://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto#Handling_dependencies

I'm really far away from being an expert with .spec files.

Would you dare to build RPM files for any other software distributions besides Fedora?

Regards,
Markus


#10

Have you got any helpful contacts to packagers for further clarification
of the corresponding name selection?

Only to Debian people, nothing for RPM.

Regards,
Markus

Ingo


#11

One distro has the same source/binary package names, the other doesn't!?

How do you think about to work with additional checks and package name
substitutions also in your RPM specification?
https://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto#H
andl ing_dependencies

I'll try if that works on our build machine, hoping this is part of the "standard" RPM specs. Can you please open an issue in the tracker on Github? I'm unable to keep up with the backlog of e-mails on the list.

I'm really far away from being an expert with .spec files.

Would you dare to build RPM files for any other software distributions
besides Fedora?

So far, the build wasn't Fedora specific and I'd very much like to keep it that way.

Regards,
Markus

Ingo


#12

Have you got any helpful contacts to packagers for further clarification
of the corresponding name selection?

Only to Debian people, nothing for RPM.

Do you get further ideas if you would look at another package specification?

https://build.opensuse.org/package/view_file/openSUSE:Factory/libXScrnSaver/libXScrnSaver.spec?expand=1

Regards,
Markus


#13

Can you please open an issue in the tracker on Github?

Yes. :wink:

Adjust dependencies for “libXScrnSaver” in RPM specification
https://github.com/jitsi/jitsi/issues/336

I am curious on how the software development will be continued.

So far, the build wasn't Fedora specific and I'd very much like to keep it that way.

How challenging can the corresponding package management become?

Regards,
Markus


#14

You can use a meta rpm package, that does not contain anything else than
those dependencies.

You only have to build those once for your plattform.

jitsi-main-for-opensuse.rpm -> jitsi-common + libXss1
jitsi-main-for-redhat.rpm -> jitsi-common + libXScrnSaver

IF you plan this... you could have a repository config included in your
main rpm, specific for the plattform.
That would make updates easier.

Marius

···

Am 01.03.2017 um 09:43 schrieb Markus Elfring:

So far, the build wasn't Fedora specific and I'd very much like to keep it that way.

How challenging can the corresponding package management become?


#15

You can use a meta rpm package, that does not contain anything else than
those dependencies.

You only have to build those once for your plattform.

jitsi-main-for-opensuse.rpm -> jitsi-common + libXss1
jitsi-main-for-redhat.rpm -> jitsi-common + libXScrnSaver

* Which dependencies would you specify for the common part in such a software
  build variant?

* Do you expect that the base component should also work and be installable
  on its own?

Regards,
Markus