[tahoe-dev] Fixed? Freebsd unparsable directory

[Ben Hyde]

I believe I was suffering the same problem Ben Laurie reported[1].   
I.e. on FreeBSD after installing tahoe fetching the test grid's public  
directory generates an exception around parsing out an integer and  
looking for a colon.

Note I had to hand add Ben's tiny patch to make freebsd6 an acceptable  
target.

Zooko asked[2] to about make test; those all passed, after Ben's patch.

Zooko asked[2] to have pycryptopp untar and 'python setup.py test'  
run; that show failures <http://sprunge.us/NhUA>

So that lead me to notice the my cryptopp is 5.4 (i.e. what freebsd  
ports gives me); and that there was a newer version 5.5.2 - hand  
installed that ... same result.

Then I noticed that allmydata-tahoe-1.0.0.tar.gz is older than  
allmydata-tahoe-1.0.0-r2525.tar.gz (I'd lept to the conclusion that  
the listing at http://allmydata.org/source/tahoe/tarballs/ has time  
ordered).

Building with that everything seems to work.

At this point I don't know if you have to have the freshest version of  
both tahoe and cryptopp.

  - ben (not Ben)

[1] http://allmydata.org/pipermail/tahoe-dev/2008-May/thread.html
[2] http://allmydata.org/pipermail/tahoe-dev/2008-May/000540.html