Hi, Thanks for the suggestions. Here are my findings: ** 1. Changed Windows firewall configuration to OFF, but still getting the same error. (python was already an exception in my firewall settings, means firewall does not apply for python)
2. after copying the tahoe-deps directory, I am getting another error. "error: Setup script exited with Cannot find ssleay32.a, aborting" As per http://www.mail-archive.com/tahoe-dev@allmydata.org/msg03338.htmlsolution is "have a pre-installed copy of OpenSSL" Ok, Installed OpenSSL from http://launchpadlibrarian.net/29331282/pyOpenSSL-0.9.win32-py2.5.exe but while executing getting same issue. Request for help. Thanks, --Sid On Wed, May 12, 2010 at 4:56 AM, Zooko O'Whielacronx <zoo...@gmail.com>wrote: > On Tue, May 11, 2010 at 5:15 PM, David-Sarah Hopwood > <david-sa...@jacaranda.org> wrote: > > sidsal sal wrote: > > > # Searching for darcsver>=1.2.0 > > # Reading http://allmydata.org/source/tahoe/deps/tahoe-dep-sdists/ > > # Download error: [Errno 10060] A connection attempt failed because the > > # connected party did not properly respond after a period of time, or > > # established connection failed because connected host has failed to > > # respond -- Some packages may not be found! > > > > This seems to be purely a networking (or perhaps firewall) problem. > > Can you download files from > > <http://allmydata.org/source/tahoe/deps/tahoe-dep-sdists/> > > on the same machine? > > Probably the firewall would allow your web browser to download the > files but does not allow the Python executable to download the files. > > The work-around that Sid discovered in his original post was to copy > the tahoe-deps directory. He wrote: > > > As a solution, I copied "tahoe-deps" directory (from > http://tahoe-lafs.org/source/tahoe-lafs/deps/) in my top directory, build > seems to be fine. > > An alternative work-around is to configure your firewall to allow > outgoing connections by your Python executable. > > I wonder if we should switch to making the sumo zip file be the > recommended file on > http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.html . > > Then people who have a firewall or other networking issue will > probably build successfully just by following the current > quickstart.html. > > The cost is download size. For the current snapshot: > > [ ] allmydata-tahoe-1.6.0-r4256.zip 20-Mar-2010 13:33 1.3M > [ ] allmydata-tahoe-1.6.0-r4256.tar.gz 20-Mar-2010 13:33 > 1.2M > [ ] allmydata-tahoe-1.6.0-r4256.tar.bz2 20-Mar-2010 13:32 > 1.0M > [ ] allmydata-tahoe-1.6.0-r4256-SUMO.zip 20-Mar-2010 13:32 > 7.1M > [ ] allmydata-tahoe-1.6.0-r4256-SUMO.tar.gz 20-Mar-2010 13:31 > 7.0M > [ ] allmydata-tahoe-1.6.0-r4256-SUMO.tar.bz2 20-Mar-2010 13:29 > 6.9M > > http://tahoe-lafs.org/source/tahoe-lafs/snapshots/?C=M;O=D > > So people would download 7.1 MB instead of 1.3 MB. A few years ago > that was a big deal, but nowadays maybe most people won't notice the > difference. > > Whoops! Not true! I just tried downloading those files from > http://tahoe-lafs.org and they came down slowly -- about 30 KB/s. I > guess they are at the wrong end of a DSL line and the more people who > try to download them at once the worse it will be. I guess we need to > get a new public Tahoe-LAFS grid operated by volunteers running so > that we can host the downloadables from there for the release! > > I am leaning toward making the downloadable linked from > quickstart.html be > > http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.7.0-SUMO.zip > instead of > http://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-tahoe-1.7.0.zip > . > > Regards, > > Zooko > _______________________________________________ > tahoe-dev mailing list > tahoe-dev@allmydata.org > http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev >
_______________________________________________ tahoe-dev mailing list tahoe-dev@allmydata.org http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
