Hi, On Tue, 06 Apr 2010, Jeremy T. Bouse wrote: > Yes, according to Python Crypto's upstream changelog [1] which the > Debian changelog [1] makes no mention of, there were API changes to > Crypto.Util.randpool.RandomPool so this will wait until upstream > paramiko releases a new version that is compatible with the new version. > If I rebuild and simply state it requires python-crypto < 2.1.0 it will > simply make the package completely uninstallable. > [1] > http://gitweb.pycrypto.org/?p=crypto/pycrypto-2.x.git;a=blob;f=ChangeLog;h=9325e0d5592f075065b1cd86d27dc7dceda93c6b;hb=033fc936155115b3a541387804e0a94820978498 > [2] > http://packages.debian.org/changelogs/pool/main/p/python-crypto/python-crypto_2.1.0-1/changelog
You could at least ask upstream for a patch and/or a timeline for a new version that fixes this issue ? I put Robey on copy, hopefully he can comment on the issue. I saw nothing about this incompatibility on https://bugs.launchpad.net/paramiko and no recent & relevant commits on http://github.com/robey/paramiko/. Robey, see http://bugs.debian.org/576697 for the full bug report. Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
