[hardy] psi ssl/tls plugin

[boskicinek]

When I try connect to my jabber server I get:
"Cannot login: SSL is enabled but no SSL/TLS (plugin) support is available."
$ dpkg-query -l|grep psi
ii psi 0.11-3 Jabber client using Qt
ii psi-translations 1.9 Translations for psi

$ dpkg-query -l|grep qca
ii libqca2 2.0.0-3 Qt Cryptographic Architecture - shared libra
ii qca-tls 1.0-4 TLS plugin for the Qt Cryptographic Architec

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

Installing libqca2-plugin-ossl fixes problem.
It should be dependency.

[boskicinek (boski-cinek)]

ok, it works now, when I installed "libqca2-plugin-ossl". Shouldn't this be a dependency for Psi?

[mitrandir77 (mitrandir77)]

installing "libqca2-plugin-ossl" fixed the problem for me. Should be dependency.

[Gleb Peregud (gleber-p)]

Since apt-get and aptitude installs recommendations by default, i suggest it should be a recommendation, not a depedency. It will make someone able to use Psi without SSL support (if it is not needed and someone cares about system being as small as possible)

[Benoit St-André (benoit-st-andre)]

I just did a dist-upgrade from gutsy to Hardy, and I cannot use psi at all since all my jabber accounts are using SSL.

I have the same SSL error then boskicinek.

As more and more people are going to be upgrading from Gutsy, this should be a dependancy (or there should be a way to tell the user that he needs the libqca2-plugin-ossl , which repairs this behaviour).

[Scott Kitterman (kitterman)]

This package is not in feisty-backports, so it's not a valid bug against feisty-backports.

[philipp kretzschmar (kopernikus)]

Psi 0.10 demands "qca-tls", and now 0.11 needs "libqca2-plugin-ossl" -- this is somewhat annoying.

[5tan (kamildor)]

Note: if you need ssl/tls support for psi, there's no need to install "qca-tls" anymore...
Title of this bug should be "..... tLs ..." - not "... tSl..."

[Ralph Janke (txwikinger)]

Package libqca2-plugin-ossl should be moved from recommends to depends

[Ralph Janke (txwikinger)]

Due to the Debian policies for dependencies, this should remain as it is:

Depends
 This declares an absolute dependency. A package will not be configured unless all of the packages listed in its Depends field have been correctly configured.
 The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality.
 The Depends field should also be used if the postinst, prerm or postrm scripts require the package to be present in order to run. Note, however, that the postrm cannot rely on any non-essential packages to be present during the purge phase.
Recommends
 This declares a strong, but not absolute, dependency.
 The Recommends field should list packages that would be found together with this one in all but unusual installations.

If the plugin would be moved to depends, users that for any reason (i.e. prohibition to use encryption in the country) would not be able to install psi. On the other hand it is easy to look in the recommendation when the tls is not working.