Description of problem:
Attempting to read a feed from an HTTPS URL logs an error message of "Error 500 while updating feed". A debugging print statement added to /usr/lib/python2.4/site_package/planet/__init__.py to see the actual exception being returned from the feed parser gave the error message:
ssl() argument 1 must be _socket.socket, not _socketobject
Googling for that exact phrase provided this link: http://mail.python.org/pipermail/python-list/2005-May/323170.html
The article at this link explains that the culprit is the timeoutsocket library. Removing the files matching /usr/lib/python2.4/site_package/planet/timeoutsocket.py* fixed the problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure planet to aggregate a feed from an HTTPS source.
Fails to connect with a type mismatch exception.
Reads the feed (or fails to connect for some other reason).
Looks like I relied on memory, when I should have relied on cut and paste. The path "/usr/lib/python2.4/site_package/planet" should be "/usr/lib/python2.4/site-packages/planet". I apologize for the confusion.
Thanks for reporting the bug.
Unfortunately I'm not going to be able to look at this bug for at least 2 weeks.
Blog page on this subject, with similar suggestions:
Please note that I've just orphaned this package. There's hopefully someone lined up who is interested in maintaining it, and fixing this issue.
Both links in this BZ are 404, can you still reproduce this?
HTTPS feeds are still broken with planet-2.0-19.fc21.noarch (fails on https://terminatorX.org/feed/ with our local installation). The problem is that 'timeoutsocket.py' is no longer compatible with current python sockets, however as the timeout feature is not even being used by planet it is safe to just remove timeoutsocket.py from the sources and HTTPS feeds work without problems again.
Please test the rawhide build. If it's good I'll build it everywhere.
Excellent, package installs without issues and planet handles http and https feeds without issues again (checked with cleared caches, too). Thanks!
Excellent, thanks! Updates on their way.
planet-2.0-20.el5 has been submitted as an update for Fedora EPEL 5.
planet-2.0-20.el6 has been submitted as an update for Fedora EPEL 6.
planet-2.0-20.fc20 has been submitted as an update for Fedora 20.
planet-2.0-20.el7 has been submitted as an update for Fedora EPEL 7.
planet-2.0-20.fc21 has been submitted as an update for Fedora 21.
* should fix your issue,
* was pushed to the Fedora EPEL 7 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing planet-2.0-20.el7'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
planet-2.0-20.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
planet-2.0-20.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
planet-2.0-20.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
planet-2.0-20.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
planet-2.0-20.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.