Description of problem: Gajim (starting from 0.15?) uses python-pyasn1 to verify SSL/TLS certificates. It should be added as install time dependency (Required). Version-Release number of selected component (if applicable): gajim-0.15-2.fc17 How reproducible: Always Steps to Reproduce: 1. Start Gajim from a console without python-pyasn1 installed Actual results: Warning on a console: (W) gajim.c.check_X509 Import of PyOpenSSL or pyasn1 failed. Cannot correctly check SSL certificate And not checked as available "SSL certificate validation" in Help->Features. Expected results: No warning and available "SSL certificate validation" Additional info: python-pyasn1 is mentioned in README as "Optional Runtime Requirements" used "to check SSL/TLS certificate".
gajim-0.15.3-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gajim-0.15.3-1.fc18
gajim-0.15.3-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/gajim-0.15.3-1.fc17
Package gajim-0.15.3-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gajim-0.15.3-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4205/gajim-0.15.3-1.fc18 then log in and leave karma (feedback).
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.