Bug 1079681

Summary: update python-recaptcha-client in EPEL to 1.0.6
Product: [Fedora] Fedora EPEL Reporter: Ian Weller <ian>
Component: python-recaptcha-clientAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: sgallagh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-recaptcha-client-1.0.6-4.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-08 22:02:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ian Weller 2014-03-23 02:20:51 UTC
1.0.6 fixes the URLs in python-recaptcha-client to ones supported by Google.

The current SSL URLs are not valid because the certificate on that server is only valid for www.google.com.

http://code.google.com/p/recaptcha/source/detail?spec=svn131&r=131

Comment 1 Fedora Update System 2014-03-24 18:36:34 UTC
python-recaptcha-client-1.0.6-4.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/python-recaptcha-client-1.0.6-4.el6

Comment 2 Fedora Update System 2014-03-25 22:40:02 UTC
Package python-recaptcha-client-1.0.6-4.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing python-recaptcha-client-1.0.6-4.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0948/python-recaptcha-client-1.0.6-4.el6
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2014-05-08 22:02:45 UTC
python-recaptcha-client-1.0.6-4.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.