Summary: | dev-python/paramiko-1.13.0 with net-misc/openssh-6.7_p1 - paramiko.transport: SSHException: Incompatible ssh peer (no acceptable kex algorithm) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eugene Cormier <eugenecormier> |
Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dschridde+gentoobugs, eugenecormier |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 531126 | ||
Bug Blocks: |
Description
Eugene Cormier
2014-12-10 04:37:26 UTC
paramiko >1.15 is known to work with openssh-6.7_p1 I fixed this by keywording: ~dev-python/paramiko-1.15.1 ~dev-python/ecdsa-0.11 Please expand on this. 1. net-misc/openssh/openssh-6.7_p1-r3.ebuild currently does NOT dep on paramiko at all. Are you suggesting it be made to do so? 2. net-misc/openssh/openssh-6.7_p1-r3.ebuild currently does inherit eutils user flag-o-matic multilib autotools pam systemd versionator missing any python eclass. Where does paramiko get pulled in??? This bug raises more questions than its current input answers. It also seems to me that it warrants assignment to <herd>base-system</herd> and >robbat2@gentoo.org We need a clear indication where python herd is involved here Paramiko doesn't get pulled in at all, I'm using it as an import in my python code to handle ssh connections.... so I emerge python, I emerge paramiko (both stable) and I get a non working setup (In reply to Ian Delaney from comment #1) dev-python/paramiko has an unstated optional runtime dependency on net-misc/openssh. The solution to this bug is to stabilize a newer version of paramiko. There are several bugs open to stabilize newer paramiko; apparently nobody searches for bugs these days. Current stable is 1.15.1. Does this issue still exist there? |