Latest upstream release: 1.9.0
Current version in Fedora Rawhide: 1.8.2
Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines
More information about the service that created this bug can be found at:
Updated to 1.9.0-rc1 in rawhide.
rc2 was released 3 days ago. While we're at it, is linking to openssl really necessary? Pidgin can't link to system libgadu as a result since this would cause GPL violation.
Since 0.6.5.2, kadu uses qca for encryption, so this is a non-issue here. I'm not sure about the other two deps, ekg2 and gg2. Both claim to be GPL, so this can be problematic as well. Adding FE-Legal.
Well, pidgin could add a link exception for SSL:
* In addition, as a special exception, the copyright holders give
* permission to link the code of portions of this program with the
* OpenSSL library under certain conditions as described in each
* individual source file, and distribute linked combinations
* including the two.
* You must obey the GNU General Public License in all respects
* for all of the code used other than OpenSSL. If you modify
* file(s) with this exception, you may extend this exception to your
* version of the file(s), but you are not obligated to do so. If you
* do not wish to do so, delete this exception statement from your
* version. If you delete this exception statement from all source
* files in the program, then also delete it here.
Alternately, libgadu could use gnutls instead of openssl.
Updated to 1.9.0-rc2 in rawhide, sent question about openssl upstream.
Upstream says using gnutls is on TODO list, but that SSL isn't used in practice yet, so I just disabled it. This should fix any licence trouble.
Closing this one out, please be aware of the licensing issue if/when you decide to renable SSL support.