[tahoe-dev] Unable to test tahoe build.

Zooko O'Whielacronx zooko at zooko.com
Sat Oct 30 15:31:28 UTC 2010


Hello, Ted Rolle Jr.. Welcome to the tahoe-dev list.


On Sat, Oct 30, 2010 at 4:05 AM, Ted Rolle Jr. <stercor at gmail.com> wrote:
> python setup.py test
> Last few lines:
> pkg_resources.VersionConflict: (pycryptopp 0.5.17
> (/usr/lib/pymodules/python2.6), Requirement.parse('pycryptopp>=0.5.20'))

It just so happens that we committed the fix for this to trunk last night:

http://tahoe-lafs.org/trac/tahoe-lafs/changeset/20101029223111-93fa1-46cf3f7c76090c9a713db5a9d6a8d633d3d2bf99/trunk
http://tahoe-lafs.org/trac/tahoe-lafs/changeset/20101029222825-93fa1-27ef644983e154837952c440e734b9bffea25859/trunk

So if you get the current trunk with:

darcs get --lazy http://tahoe-lafs.org/source/tahoe-lafs/trunk tahoe-lafs

Then you won't have this problem. There is a simple workaround,
though: uninstall (delete) the pycryptopp-0.5.17 package which is
stored in /usr/lib/pymodules/python2.6.

> I did get tahoe running the first time I installed it.

How did you get past
http://tahoe-lafs.org/pipermail/tahoe-dev/2010-October/005496.html ?

I was wondering if it had to do with the difference between "cd
$BASEDIR && bin/tahoe" vs. "cd $BASEDIR/bin && ./tahoe". Was that the
difference? Or was it something else?

Regards,

Zooko



More information about the tahoe-dev mailing list