Forum OpenACS Q&A: Re: install-oacs.sh help

Collapse
9: Re: install-oacs.sh help (response to 8)
Posted by Gustaf Neumann on
That behavior is strange. I've now tried to get the contents from cvs. via ADSL from a public provider, i had no problems.

I assume, you get the same timeout if you issue the following commands:

   mkdir -p /var/www/oacs-5-8
   cd /var/www/oacs-5-8
   cvs -q -d:pserver:anonymous@cvs.openacs.org:/cvsroot checkout -r oacs-5-8 acs-core
Can it be, that you have any of the following CVS enviromnet variables set?
http://www.thathost.com/wincvs-howto/cvsdoc/cvs_19.html

Collapse
10: Re: install-oacs.sh help (response to 9)
Posted by christopher laurence on
Hello,

Yeah I get the timeout message. I did the following for all
the environment variables. Most are empty besides path and home.

===============================================
test-engr@testengr-Latitude-E6420:~$ echo $CVSINGNORE

test-engr@testengr-Latitude-E6420:~$ echo $CVSWRAPPPERS

test-engr@testengr-Latitude-E6420:~$ echo $CVSREAD

test-engr@testengr-Latitude-E6420:~$ echo $CVSUMASK

test-engr@testengr-Latitude-E6420:~$ echo $CVSROOT

test-engr@testengr-Latitude-E6420:~$ echo $EDITOR

test-engr@testengr-Latitude-E6420:~$ echo $CVSEDITOR

test-engr@testengr-Latitude-E6420:~$ echo $VISUAL

test-engr@testengr-Latitude-E6420:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
test-engr@testengr-Latitude-E6420:~$ echo $HOME
/home/test-engr
test-engr@testengr-Latitude-E6420:~$ echo $HOMEDRIVE

test-engr@testengr-Latitude-E6420:~$ echo $CVS_RSH

test-engr@testengr-Latitude-E6420:~$ echo $CVS_SERVER

test-engr@testengr-Latitude-E6420:~$ echo $CVS_PASSFILE

test-engr@testengr-Latitude-E6420:~$ echo $CVS_CLIENT_PORT

test-engr@testengr-Latitude-E6420:~$ echo $CVS_RCMD_PORT

test-engr@testengr-Latitude-E6420:~$ echo $CVS_CLIENT_LOG

test-engr@testengr-Latitude-E6420:~$ echo $CVS_SERVER_SLEEP

test-engr@testengr-Latitude-E6420:~$ echo $CVS_IGNORE_REMOTE_ROOT

test-engr@testengr-Latitude-E6420:~$ echo $COMSPEC

test-engr@testengr-Latitude-E6420:~$ echo $TMPDIR

test-engr@testengr-Latitude-E6420:~$ echo $TMP

test-engr@testengr-Latitude-E6420:~$ echo $TEMP

test-engr@testengr-Latitude-E6420:~$

Collapse
12: Re: install-oacs.sh help (response to 11)
Posted by Gustaf Neumann on
Dear christopher,

in case we don't get CVS working on your side, i've added an additional as additional source for OpenACS the tar release. To get the OpenACS 5.8.1 release via tar file, get the newest version of install-oacs.sh from git and uncomment the following line:

oacs_tar_release=

When you rerun the script, the core of OpenACS will be installed via wget + tar file. By using this way, one has to install the application packages via "install from repository".

Collapse
13: Re: install-oacs.sh help (response to 12)
Posted by christopher laurence on
Hello Gustaf,

The fix in the script worked. I wasn't able to download xowf and the IT group hasn't gotten back to me about what is being blocked. Is it an issue if I don't have xowf?

Collapse
14: Re: install-oacs.sh help (response to 13)
Posted by Gustaf Neumann on
no, xowf is (a) optional and (b) once acs-core is installed, one can get it via "install from repositpory" directly from OpenACS.

The primary reason for having xowf in the script was that up to the release of OpenACS 5.8.1 getting it from git was the only solution.

all the best
-g

Collapse
15: Re: install-oacs.sh help (response to 14)
Posted by christopher laurence on
Hello Gustaf,

Thanks for all the help!

Collapse
16: Re: install-oacs.sh help (response to 15)
Posted by Gustaf Neumann on
Guess, we should make the "install from tar-release" default, and let developer choose to use cvs/git as an option...