Description of problem:
Tracking ticket for the the update of ZeroMQ to version 4.
* new package zeromq4 that obsoletes the package zeromq3
* ZeroMQ v4 new requirement:
libsodium (review ticket: bug #990423)
* ZeroMQ v4.0.3 download link:
* API compatibility report for the libzmq library
between 3.2.4 and 4.0.3 versions on x86_64:
* ZeroMQ 3.2.4 dynamic library:
* ZeroMQ 4.0.3 dynamic library:
* SONAME bump between 3.2.4 and 4.0.3 versions:
from 3.0.0 to 3.1.0
zeromq 4.0.3 specfile and SRPM (work in progress):
* builds successfully in mock for Fedora 19, Fedora 20 and EPEL 6
* zeromq4 should obsolete the zeromq3 package
* file '/usr/bin/curve_keygen' contains a standard rpath '/usr/lib64' in [/usr/lib64]
* The test suite starts to fail if I try to handle the rpath problem in curve_keygen (http://fedoraproject.org/wiki/RPath_Packaging_Draft)
- disable silent rules in configure
- delete rpath with chrpath
This method of deleting rpath works with the test suite and we are now down to one last failing test:
../config/test-driver: line 95: 9265 Aborted (core dumped) "$@" > $log_file 2>&1
make: Entering directory `/home/tomspur/rpmbuild/BUILD/zeromq-4.0.3/tests'
make: Nothing to be done for `all'.
make: Leaving directory `/home/tomspur/rpmbuild/BUILD/zeromq-4.0.3/tests'
Testsuite summary for zeromq 4.0.3
# TOTAL: 43
# PASS: 42
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
- I added provides/requires for zeromq3, but with the version of zeromq4 as I think that's appropriate. What do you think?
The spec can be found here: http://tomspur.fedorapeople.org/review/zeromq4.spec
Do you want to open a review request for zeromq4 or should I do it?
(In reply to Thomas Spura from comment #2)
> Do you want to open a review request for zeromq4 or should I do it?
The review request can be found at bug #1069556.
zeromq2 just hit rawhide:
I'll update the zeromq package to version 4 next week. If packages cannot be (easily) rebuild with it, they can then BR zeromq2 instead.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here: