The reason for the requested upgrade is the following bugs which were affecting us were addressed in the 4.1 re;ease:

 * Fixed #1399 - assertion failure in tcp.cpp after network reconnect.          
 * Fixed #1661 - does not handle IPv6 link local addresses.                      
 * Fixed #1445 - zmq::socket_base_t::connect fails on tcp ipv6 address          
 * Fixed STDINT event interface macros to work with CZMQ 3.0.                    
 * Fixed #1224 - crash when processing empty unsubscribe message.                
 * Fixed #1273 - V3 protocol handler vulnerable to downgrade attacks.            
 * Fixed #1347 - lack way to get peer address.                                  
 * Fixed #1362 - SUB socket sometimes fails to resubscribe properly.            
 * Fixed #1389 - PUB, PUSH sockets had slow memory leak.                        
 * Improved client reconnection strategy on errors                              
 * GSSAPI security mechanism                                                    
 * Message metadata -- zmq_msg_gets ()

Hello, just a ping on this, as some of these bugs are affecting some of our production servers and we would appreciate it if the package could updated soon.

Thanks.

(In reply to Konstantinos Margaritis from comment #2)
> Hello, just a ping on this, as some of these bugs are affecting some of our
> production servers and we would appreciate it if the package could updated
> soon.
> 
> Thanks.

Build on EPEL7: http://koji.fedoraproject.org/koji/taskinfo?taskID=14460111

zeromq-4.1.4-5.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-9769421234

zeromq-4.1.4-5.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-9769421234

Because of SO version bump there are several other packages being broken by this update, please make sure you get those to same update.

Just a heads up that zeromq-4.1.5 may be released today or very soon.

0MQ version 4.1.5 stable, released on 2016/xx/xx
================================================

* Fixed #1673 - CMake on Windows put PDB in wrong directory.

* Fixed #1723 - Family is not set when resolving NIC on Android.

* Fixed #1608 - Windows 7 TCP slow start issue.

* Fixed #1806 - uninitialised read in curve getsockopt.

* Fixed #1807 - build broken with GCC 6.

* Fixed #1831 - potential assertion failure with latest libsodium.

* Fixed #1850 - detection issues with tweetnacl/libsodium.

* Fixed #1877 - Avoid terminating connections prematurely

* Fixed #1887 - zmq_bind IPv4 fallback still tries IPv6

* Fixed #1866 - fails to build on SunOS 5.10 / Solaris 10

* Fixed #919 - ZMQ_LINGER (related to #1877)

* Fixed #114 - cannot unbind with same endpoint with IPv6 enabled.

* Fixed #1952 - CMake scripts not part of release tarballs

* Fixed #1542 - Fix a crash on Windows when port 5905 is in use.

* Fixed #2021 - Fix building on sparc32.

That shouldn't happen befor following packages are build against new zeromq:

simcrs
czmq
airinv
pdns

airinv-1.00.1-2.el7 zeromq-4.1.4-5.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-9769421234

(In reply to Tuomo Soini from comment #8)
> That shouldn't happen befor following packages are build against new zeromq:
> 
> simcrs
> czmq
> airinv
> pdns


Those packages have been added to the update: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-9769421234
czmq was already submitted as an update last week

airinv-1.00.1-2.el7, pdns-3.4.8-2.el7, simcrs-1.01.1-2.el7, zeromq-4.1.4-5.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-9769421234

There is some argument against pushing that update to EPEL7:  https://bodhi.fedoraproject.org/updates/airinv-1.00.1-2.el7%20pdns-3.4.8-2.el7%20simcrs-1.01.1-2.el7%20zeromq-4.1.4-5.el7#comment-452073

What should we do?

I would say that our ABI guarantees do not extend to EPEL packages and the currently shipping version is so broken due to the many bugs in it that it is not usable. Therefore I would argue that rather than trying to protect hypothetical users (who likely don't exist due to aforementioned bugs) we address real user problems.

There are very good reasons for this update and everything required by epel policy for .so version bump has been done afaik. I'd go ahead with update.

airinv-1.00.1-2.el7, pdns-3.4.8-2.el7, simcrs-1.01.1-2.el7, zeromq-4.1.4-5.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.

This broke pdns. At the time of the build the new version of zeromq wasn't in the buildroot (https://kojipkgs.fedoraproject.org//packages/pdns/3.4.8/2.el7/data/logs/x86_64/root.log)

I'll rebuild pdns again but please be more carefull next time.

(In reply to Ruben Kerkhof from comment #16)
> I'll rebuild pdns again but please be more carefull next time.

Thanks Ruben! And sorry for the trouble

No problem!