1. We don't actually have a binary egg of pycryptopp-0.5.20 for py2.6/linux/amd64 hosted yet, see: http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/?C=M;O=D . As soon as either Josh's or Brian's buildslaves are respectively connected to the Internet or empowered with flappclient then this should be remedied.
Is 0.5.19 acceptable? That's what is in pkgsrc, and probably what was current when I added packages over the summer. I am running 1.8.0c4 with py-cryptopp 0.5.19 and it seems ok.
pgpFx9bV8Fky1.pgp
Description: PGP signature
_______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
