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

[Kyle Markley]

>> Tonight I finally got around to upgrading my grid to 1.8.0 and it went
>> smoothly everywhere except on Win7-64.  There is something wrong with
>> the
>> dependency checking there; setup.py build ran cleanly but setup.py test
>> complained that the installed version of pycryptopp was too old.  (It's
>> right, it is.)  I reran setup.py build and saw no mention at all of
>> pycryptopp -- it appears that somehow it wasn't even checked, so the
old
>> version wasn't detected until setup.py test.
> 
> "python setup.py build" doesn't check for run-time dependencies
> (packages that are needed to run the code), only for build-time
> dependencies (packages that are needed to build the code).

So, what brings my run-time dependencies up-to-date?
I hope I'm not supposed to do that manually.


>> Two other systems (WinXP-32 and Vista-32) didn't have any problem with
>> the
>> upgrade, so this may be a platform-specific problem.
> 
> Perhaps they didn't have a too-old version of pycryptopp installed?

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?

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?

I'm thoroughly confused at this point, and need to go to sleep.

-- 
Kyle Markley