Closed cmharr closed 7 years ago
I can see the path to activate is relative to st_root but that variable doesn't seem to get populated, even when using -t or setting st_root and ST_HOME in the shell.
I had renamed install.sh to synda_install.sh to be more descriptive. I just noticed if I rename it back to install.sh it tends to work better (though still appears to crash before the end of the install):
Collecting pillow>=2.4.0 (from reportlab)
Using cached Pillow-4.0.0.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/tmp/root/pip-build-525vF6/pillow/setup.py", line 138
required = {'jpeg', 'zlib'}
^
SyntaxError: invalid syntax
----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/root/pip-build-525vF6/pillow/
Regarding the first two comments, the problem is that "install.sh" script cannot be used to upgrade an RPM based installation. This script is only for source installation. The upgrade guide for RPM installation is available here: https://github.com/Prodiguer/synda/blob/master/sdt/doc/upgrade_guide.md
Regarding the third comment, this is a bug caused by an non-backward compatible change in an external library. It should only affect 3.6 version installed from source (RPM 3.6 and DEB 3.6 should not be affected).
It has been fixed in 3.7.
It can be fixed in 3.6 by downgrading the pillow
package
pip install pillow==3.4.2
Jerome, Thanks for the comments. I thought the install.sh might only be for the source install; however, the procedure for installing the globustransfer module seemed to be through the use of install.sh, thus the reason for my attempts. At any rate, I ended up upgrading everything to 3.6 via RPM.
Yes I confirm globustransfer module it is only available for source-based installation at the moment.
I've been trying to either install the globustransfer module or even upgrade my 3.4 install and the installer consistently gives me a message saying "activate not found" with no messages in the install.log
If I provide the -t option with the standard path, it then complains about other issues:
With the latter error, I do see the following one line in the install.log:
My previous install is 3.4, using an RPM. During my attempts to install the globusonline module, I ran the following as well and the log shows it apparently installing 3.6, yet at the end, synda -V still shows 3.4.