Summary: | dev-python/fabric-1.12: should depend on <dev-python/paramiko-2.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Capricelli <orzel> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | adam.grigolato, alicef, gentoo-bugs, rjozwik |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Thomas Capricelli
2016-09-28 09:53:35 UTC
This is quite an obvious change to the ebuild, isn't it ?
meanwhile, a workaround is to add this to /etc/package.mask/*
# fix bad dep in fabric ebuild
>=dev-python/paramiko-2.0.0
https://github.com/fabric/fabric/issues/1461 kinda indicates the paramiko<2.0 restriction is pointless and the result of confusion about how pip works. Perhaps just sed-ing it out would be better. (In reply to eroen from comment #2) > https://github.com/fabric/fabric/issues/1461 kinda indicates the > paramiko<2.0 restriction is pointless and the result of confusion about how > pip works. Perhaps just sed-ing it out would be better. I think that this seems the way to go: As of today's update to =dev-python/pycrypto-2.6.1-r2 all paramiko-based packages such as fabric or duplicity failed with errors like this on my systems: ValueError: CTR mode needs counter parameter, not IV This seems to be known and deliberately, see e. g. here: https://github.com/dlitz/pycrypto/issues/149 So forcing a mask like >=dev-python/paramiko-2.0.0 no longer works for me, but letting paramiko be updated to version >2.0.0 and just dropping "<2.0" from /usr/lib64/python2.7/site-packages/Fabric-1.12.0-py2.7.egg-info/requires.txt restores working fabric (and duplicity, etc.) for me. OTOH, maybe <paramiko-2.0.0 would need a fix for the aforementioned pycrypto issue anyways. (In reply to eroen from comment #2) > https://github.com/fabric/fabric/issues/1461 kinda indicates the > paramiko<2.0 restriction is pointless and the result of confusion about how > pip works. Perhaps just sed-ing it out would be better. I agree with all of that ! (In reply to Martin Wegner from comment #3) > I think that this seems the way to go: As of today's update to > =dev-python/pycrypto-2.6.1-r2 all paramiko-based packages such as fabric or > duplicity failed with errors like this on my systems: Yeps, everything is broken again now, and even masking paramiko >=2.0 doesn't help, you need to mask pycrypto as well.. Please do something, it's getting out of control The diff between r1 and r2 for pycrypto-2.6.1 is really big. Not what i would expect for r1->r2... And it breaks a lot. Fabric issue #1461 from Github is now closed and bumping Fabric ebuild to 1.13.1 resolved problem with Paramiko 2 for me. (In reply to Radoslaw Jozwik from comment #6) > Fabric issue #1461 from Github is now closed and bumping Fabric ebuild to > 1.13.1 resolved problem with Paramiko 2 for me. Great, can someone bumps fabric then ????? Fabric 1.13 is still not in tree... is there any chance we got a fix for this bug meanwhile ? 1.14.0 is in tree now |