Latest upstream release: 2.2.0.1 Current version in Fedora Rawhide: 2.2.0 URL: https://github.com/zeromq/pyzmq/downloads Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Chiming in that this update will be useful for Fedora Infrastructure and the fedmsg project. The TCP_KEEPALIVE option that I think will fix some bugs we are seeing was added to python-zmq in commit 6a53412 and became available in v2.2.0.1. https://github.com/zeromq/pyzmq/commit/6a534121f76aedd613a793eeed7a2c7fe9cf9b89 If I can do anything to help make this happen, please let me know.
(In reply to comment #1) > If I can do anything to help make this happen, please let me know. What problems did you have, when we moved to zeromq3 on el6? It's perfectly fine to do that change for fc19, but I'm unsure, if we should do the same change on other releases too. I'd nevertheless prefer to update all releases to 2.2.0.1 and zeromq3... rawhide already has 2.2.0.1 and I'll now switch to zeromq3 there too.
Ah, no rawhide also had BR zeromq3 already, so it's all set. Let me know of your troubles with python-zmq BR on zeromq3, so we can avoid the same problems on other fedora releases. Will do the 2.2.0.1 update on el6 now,
python-zmq-2.2.0.1-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/python-zmq-2.2.0.1-1.el6
Ah, I commented on the bodhi update and not here. That was a mistake on my part: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-13177/python-zmq-2.2.0-4.el6,zeromq3-3.2.0-0.3.20121009git1ef63bc.el6?_csrf_token=c509469764bee33af0852bbfcafcd4876c7fce71 The issue stemmed from php-zmq (built against zeromq2) and python-zmq (built against zeromq3) both being loaded by the same apache process. The symptom I saw was an error message about "Socket operation on a non-socket" in application logs. The error disappeared when I installed an updated version of php-zmq (now built against zeromq3).
It seems you are the owner of php-zmq, so we can handle that directly. Please build updates for the other branches built against zeromq3 and let me know. I'll do the same for python-zmq. I can then push out {php,python}-zmq directly in one update.
python-zmq-2.2.0.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/python-zmq-2.2.0.1-1.fc18
python-zmq-2.2.0.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/python-zmq-2.2.0.1-1.fc17
Package python-zmq-2.2.0.1-1.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-zmq-2.2.0.1-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-13779/python-zmq-2.2.0.1-1.el6 then log in and leave karma (feedback).
python-zmq-2.2.0.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
python-zmq-2.2.0.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
python-zmq-2.2.0.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.