too high version dependency on pycryptopp
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pycryptopp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
tahoe-lafs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: tahoe-lafs
when then executing tahoe in a clean natty chroot with python-mock (bug 782455) and a fixed python-foolscap (bug 782414 see below) installed:
$ apt-get install python-mock
$ tahoe
Traceback (most recent call last):
File "/usr/bin/tahoe", line 9, in <module>
load_
File "/usr/lib/
return get_distributio
File "/usr/lib/
return ep.load()
File "/usr/lib/
entry = __import_
File "/usr/lib/
check_
File "/usr/lib/
raise PackagingError(
allmydata.
PackagingError: We require pycryptopp >= 0.5.20, but could only find version 0.5.17.
The version we found is from '/usr/lib/
To resolve this problem, uninstall that version, either using your
operating system's package manager or by moving aside the directory.
the fixed foolscap it is available here from svn:
svn://svn.
revision 17008
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: tahoe-lafs 1.8.2-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-9-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat May 14 01:52:13 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1)
PackageArchitec
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: tahoe-lafs
UpgradeStatus: No upgrade log present (probably fresh install)
Here's where the upstream Tahoe-LAFS specifies what version of pycryptopp it needs:
http:// tahoe-lafs. org/trac/ tahoe-lafs/ browser/ trunk/src/ allmydata/ _auto_deps. py?annotate= blame&rev= 4976#L64
It says:
64 if platform. machine( ).lower( ) in ['i386', 'x86_64', 'amd64', 'x86', '']: requires. append( "pycryptopp >= 0.5.20") requires. append( "pycryptopp >= 0.5.14")
65 # pycryptopp v0.5.20 fixes bugs in SHA-256 and AES on x86 or amd64
66 # (from Crypto++ revisions 470, 471, 480, 492). The '' is there
67 # in case platform.machine is broken and this is actually an x86
68 # or amd64 machine.
69 install_
70 else:
71 # pycryptopp v0.5.13 had a new bundled version of Crypto++
72 # (v5.6.0) and a new bundled version of setuptools (although that
73 # shouldn't make any difference to users of pycryptopp).
74 install_
So it sounds like it is potentially important to upgrade pycryptopp in Ubuntu from v0.5.17 to v0.5.20. Doing so fixes a bug which causes incorrecvt SHA-256 and AES computations on x86 and amd64 architectures.