Description of problem:
Currently, zeromq is compiled such that the libzmq library version is 5 but previously was version 4 in epel7. This is causing dynamic linking issues for code compiled against version 4. According to the EPEL policies within a given major release or RHEL, the packages should maintain ABI compatibility otherwise a compat lib should be provided.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
See the SONAME for older version 4 packages in epel7 like zeromq-4.0.5-4.el7.x86_64 :
$ objdump -p /usr/lib64/libzmq.so.4 | grep SONAME
And from the latest package zeromq-4.1.4-5.el7.x86_64:
$ objdump -p /usr/lib64/libzmq.so.5 | grep SONAME
Both of these packages are minor versions of zeromq 4 so it doesn't make sense to bump the libzmq.so to version 5 unless there were ABI changes.
error: Failed dependencies:
libzmq.so.4()(64bit) is needed by (installed) lts-libs-3.3.0-1.wdas.el7.x86_64
The library should continue to be the same version libzmq.so.4 as prior zeromq releases unless there are incompatibilities in which case a compat-zeromq package should be released.
Dear Sven, do you still have an issue?
You are fully right, the SONAME bump should not have occurred during the lifetime of the package on EPEL. Nevertheless, it is too late now... then, you are right again, a compatibility package should be provided. But that consumes time (do not hesitate to contribute!), and I guess that the official maintainers of the ZeroMQ don't have much time these days to dedicate to such tasks.
A new version has been released (https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-cea8576f94), as there was another SONAME bump on libsodium, breaking some packages on EPEL 7 linking to both libsodium and zeromq (https://bugzilla.redhat.com/show_bug.cgi?id=1665630). With the new 4.1.4-6 release of the zeromq package, libsodium and zeromq are now aligned on EPEL 7, and the few packages depending on ZeroMQ will have to be rebuilt nevertheless.