salt: zeromq 4.1.4-5.el7 from EPEL causes issues with python-zmq-14.7.0-1.el7.x86_64 from saltstack repo
Description of Issue/Question
Setup
CentOS 7 + EPEL repo Saltstack repo enabled and salt* related packages installed
Steps to Reproduce Issue
Try installing the latest zeromq from EPEL, that came out earlier today and you’ll get errors like so:
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
Resolving Dependencies
--> Running transaction check
---> Package zeromq.x86_64 0:4.0.5-4.el7 will be updated
--> Processing Dependency: libzmq.so.4()(64bit) for package: python-zmq-14.7.0-1.el7.x86_64
---> Package zeromq.x86_64 0:4.1.4-5.el7 will be an update
--> Finished Dependency Resolution
Error: Package: python-zmq-14.7.0-1.el7.x86_64 (@saltstack)
Requires: libzmq.so.4()(64bit)
Removing: zeromq-4.0.5-4.el7.x86_64 (@saltstack)
libzmq.so.4()(64bit)
Updated By: zeromq-4.1.4-5.el7.x86_64 (epel)
~libzmq.so.5()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Versions Report
Salt Version:
Salt: 2015.8.10
Dependency Versions:
Jinja2: 2.7.3
M2Crypto: 0.21.1
Mako: 0.8.1
PyYAML: 3.11
PyZMQ: 14.7.0
Python: 2.7.5 (default, Nov 20 2015, 02:00:19)
RAET: Not Installed
Tornado: 4.2.1
ZMQ: 4.0.5
cffi: 0.8.6
cherrypy: 3.2.2
dateutil: 1.5
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
libgit2: Not Installed
libnacl: 1.4.3
msgpack-pure: Not Installed
msgpack-python: 0.4.7
mysql-python: 1.2.3
pycparser: 2.14
pycrypto: 2.6.1
pygit2: Not Installed
python-gnupg: Not Installed
smmap: Not Installed
timelib: Not Installed
System Versions:
dist: centos 7.2.1511 Core
machine: x86_64
release: 4.4.14.bs.ufd
system: CentOS Linux 7.2.1511 Core
I get the same results with 2016.3.1 as it uses the same python-zmq.
Could you update/rebuilt python-zmq against the latest zeromq and provide that in your repos or if not, make the epoch on the one provided from saltstack higher than 0? For now, I’m excluding zeromq from EPEL to avoid issues.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 8
- Comments: 25 (14 by maintainers)
The fix for this shall appear in the next point release, which is soon.
I can confirm that 2016.3.2 resolves this issue under CentOS 7. Updating from 2016.3.1 works fine, with no RPM dependency errors.
Same issue