Install problems Red Hat ES 4.0

[imhavoc]

I am attempting to install tahoe on my Red Hat ES 4.0 server.

When I first attempted to install (python setup.py build), I got an error complaining that I needed a newer version of Python 2.4.2 or newer.

After installing an alternate Python (2.6.4), I continued to encounter failures to build.

The first complaint by the system was that the setuptool Python module was not available. I addressed that and tried again.

I continued to have build failures and eventually found an obscure reference to the tahoe-deps collection and _auto_deps.py. After putting those in the source tree, I am able to run the "python2.6 setup.py build" command without errors, but all I get in response is the line, "running build."

Nothing else happens. No tahoe executable is generated.

[zooko]

The first complaint by the system was that the setuptool Python module was not available. I addressed that and tried again.

Can you please paste in the command that you executed and the output that resulted which was a complaint that setuptools was not available? That shouldn't happen and I can't think of any way that it could happen so something is not right at this step.

You should not need to install setuptools.

[imhavoc]

Replying to zooko:

The first complaint by the system was that the setuptool Python module was not available. I addressed that and tried again.

Can you please paste in the command that you executed and the output that resulted which was a complaint that setuptools was not available? That shouldn't happen and I can't think of any way that it could happen so something is not right at this step.

Unfortunately, I have been unable to reproduce that error, and the output has been bumped out of my scrollback buffer.

The command was simply "python2.6 setup.py build."

[zooko]

You can't reproduce it because now when you run python2.6 setup.py build it no longer gives that error message, right? This is almost certainly because you subsequently installed setuptools. Could you please uninstall setuptools and try again?

[imhavoc]

I removed or disabled setuptools:

$ python2.6 setup.py build Traceback (most recent call last):

File "setup.py", line 38, in <module>

from setuptools import find_packages, setup

ImportError?: No module named setuptools

[imhavoc]

Let me repost that:

$ python2.6 setup.py build

Traceback (most recent call last):

File "setup.py", line 38, in <module>

from setuptools import find_packages, setup

ImportError?: No module named setuptools

[zooko]

Trac interprets everything you write as being "trac markup". To escape from that an include literal stuff such as command-line output, use triple curly braces, like this:

{{{
$ python2.6 setup.py build
Traceback (most recent call last):
    File "setup.py", line 38, in <module>
        from setuptools import find_packages, setup
ImportError?: No module named setuptools 
}}}

which comes out as:

$ python2.6 setup.py build
Traceback (most recent call last):
    File "setup.py", line 38, in <module>
        from setuptools import find_packages, setup
ImportError?: No module named setuptools 

[zooko]

Okay, so line 38 of setup.py at version 1.5.0 (which is the version you get by following ​http://allmydata.org/source/tahoe/trunk/docs/install.html ), is: setup.py@#L36. Hrm, but that line doesn't say from setuptools import find_packages, setup. Are you following the instructions on ​http://allmydata.org/source/tahoe/trunk/docs/install.html ? In particular, the part that says "Download the 1.5.0 release zip file:

​http://allmydata.org/source/tahoe/releases/allmydata-tahoe-1.5.0.zip"?

[imhavoc]

Replying to zooko:

Okay, so line 38 of setup.py at version 1.5.0 (which is the version you get by following ​http://allmydata.org/source/tahoe/trunk/docs/install.html ), is: setup.py@#L36. Hrm, but that line doesn't say from setuptools import find_packages, setup. Are you following the instructions on ​http://allmydata.org/source/tahoe/trunk/docs/install.html ? In particular, the part that says "Download the 1.5.0 release zip file:

​http://allmydata.org/source/tahoe/releases/allmydata-tahoe-1.5.0.zip"?

Yes, those are precisely the instructions, including downloading that link to that zip, that I am attempting to follow.

I see that the following lines in setup.py "might" be looking for setuptools:

{{{
     38 from setuptools import find_packages, setup
     39 from setuptools.command import sdist
     40 from setuptools import Command
}}}

I will re-download the zip file and try again.

[imhavoc]

Well, it worked that time. I guess you can close this ticket. Sorry for the disruption.

[zooko]

Well, since you had a setup.py file that had something else on line 38, I guess you must have downloaded the wrong version the first time. But how could that happen? Did you just click the link in ​http://allmydata.org/source/tahoe/trunk/docs/install.html which leads to ​http://allmydata.org/source/tahoe/releases/allmydata-tahoe-1.5.0.zip or did you manually enter in a url such as ​http://allmydata.org/source/tahoe/releases/ and explore, or what? Hm, a little exploring the source code browser shows me that the setup.py that came with Tahoe-LAFS v1.4.1 had the line from your stack trace on line 38:

from setuptools import find_packages, setup

So unless you tell me otherwise, I'm guessing that you somehow got v1.4.1. Maybe you had already downloaded it long ago when it was the current version and then you accidentally used it, thinking you were using the current version, today?

[imhavoc]

So unless you tell me otherwise, I'm guessing that you somehow got v1.4.1. Maybe you had already downloaded it long ago when it was the current version and then you accidentally used it, thinking you were using the current version, today?

I wish I had an explanation for it. I redownloaded the zip from the link on the page and did a checksum on both files -- exact match. I must have done something out of order in the process.

It's running now: ​http://bigpig.org:5234/

I'm stumped.

[zooko]

Okay, I can't figure out how to prevent the next person from stepping into whatever hole you stepped into, so let's close this ticket now. Cool that it (eventually) worked!