Seemingly hard dependency on pycrypto prevents recommended operation #56551
Labels
Pending-Discussion
The issue or pull request needs more discussion before it can be closed or merged
Milestone
Description of Issue
Failure to run saltstack due to a collection of issues.
I run salt in a test config with:
salt-ssh '*' test.ping --roster-file=./roster
First it depends on pycrypto. This is because in my system in
/usr/lib/python3.8/site-packages/salt-3000.1-py3.8.egg-info/requires.txt
I can seepycrypto
outright called out.Then I tried removing that line. After all, I do have
M2Crypto
version0.35.2
installed, and as I understand it, salt will try it.Then it failed again because
The 'msgpack!=0.5.5,<1.0.0,>=0.5' distribution was not found and is required by salt
which is in fact true: on the change to python3, my distribution changed from msgpack0.6.2
to msgpack1.0.0
.Is there a reason to max-version-lock msgpack below 1.0.0? Is there a reason the egg seems to now (since the previous version on py2:
2019.2.0
) depend on pycrypto?Is there some workaround, something obvious I am missing?
Steps to Reproduce Issue
From Void Linux,
xbps-install salt
and try any command.Versions Report
(Provided by running
salt --versions-report
. Please also mention any differences in master/minion versions.)Yes, the following, after I remove
pycrypto
andmsgpack
lines from/usr/lib/python3.8/site-packages/salt-3000.1-py3.8.egg-info/requires.txt
does in fact list pycrypto. This confuses me too.The text was updated successfully, but these errors were encountered: