[tahoe-dev] Dependency trouble for 1.8.0 upgrade on Win7-64

Zooko O'Whielacronx zooko at zooko.com
Sun Oct 3 07:11:06 UTC 2010

On Wed, Sep 29, 2010 at 12:22 AM, Kyle Markley <kyle at arbyte.us> wrote:
> So, what brings my run-time dependencies up-to-date?
> I hope I'm not supposed to do that manually.

I'm afraid so. You could accomplish this by removing the too-old
pycryptopp or by installing a new one.

There is a feature which is intended to fix this:

http://tahoe-lafs.org/trac/tahoe-lafs/ticket/530# use setuptools's
--multi-version mode

If you would like to try it and report back then apply the following patch:

diff -rN -u old-trunk/setup.cfg new-trunk/setup.cfg
--- old-trunk/setup.cfg 2010-10-03 01:00:03.000000000 -0600
+++ new-trunk/setup.cfg 2010-10-03 01:00:09.000000000 -0600
@@ -37,7 +37,7 @@
 # (See http://tahoe-lafs.org/trac/tahoe-lafs/ticket/142 .)

-build = darcsver --count-all-patches develop --prefix=support
make_executable build
+build = darcsver --count-all-patches develop --multi-version
--prefix=support make_executable build
 test = darcsver --count-all-patches develop --prefix=support
make_executable build trial
 sdist = darcsver --count-all-patches sdist
 install = darcsver --count-all-patches install
diff -rN -u old-trunk/src/allmydata/scripts/keygen.py
--- old-trunk/src/allmydata/scripts/keygen.py   2010-10-03
01:00:06.000000000 -0600
+++ new-trunk/src/allmydata/scripts/keygen.py   2010-10-03
01:00:09.000000000 -0600
@@ -14,6 +14,9 @@
 keygen_tac = """
 # -*- python -*-

+import pkg_resources
 from allmydata import key_generator
 from twisted.application import service

> On closer examination, their pycryptopp is also too old (0.5.19).  So why
> did setup.py test run and say that all the tests passed?

Perhaps setup.py test was testing the old copy of Tahoe-LAFS installed
into your system instead of testing the new copy in whose source tree
was your current working directory?

> For reasons unknown to me, I'm seeing that when I start my tahoe node it's
> coming up as 1.7.1 on the web status page even though I can run
> tahoe.pyscript --version and get 1.8.0 with pycryptopp: 0.5.19-r704.
> Shouldn't that be impossible because 1.8.0 requires 0.5.20?

Yes. That is pretty confusing. Are you sure that's what happened?



More information about the tahoe-dev mailing list