[kepler-dev] ptolemy checkout needs port 3690 open?

[Christopher Brooks]

Derik Barseghian wrote:
 > Hey Christopher,
 >
 > Jing was trying to get Kepler checked out and running from scratch, and
 > bumped into an issue. When he's blocking outbound port 3690, the ptolemy
 > checkout fails. Does that sound right to you? I added a note to our
 > build instructions warning about it.
 >
 > Derik

Hi Derik,

It depends on which type of svn access is used.
I think :
svn: uses port 3690
svn+ssh: uses port 22
https: uses port 443

https: can be used for read only access of the ptII svn repository,
but I'm not regularly setting up read/write accounts in our https
system, so writing from https: does not usually work.

The preferred way to access the ptII svn repository is svn+ssh.

svn: works for readonly and maybe read/write.

I'm not sure how the Kepler build system is downloading ptII these
days.  It was using svn or https, which meant that I could not make
commits.  This appears to still be the case:

bash-3.2$ pwd
/Users/cxh/src/kepler/ptolemy
bash-3.2$ svn commit -m "Test of commit from within the Kepler build 
system" README.txt
svn: Commit failed (details follow):
svn: Authorization failed

http://chess.eecs.berkeley.edu/ptexternal talks about the different
ways to access the ptII svn repository.

It might be safer for the kepler build system to use https to access
all the repositories as https is more likely to be open than 3690 or 22.



_Christopher

-- 
Christopher Brooks (cxh at eecs berkeley edu) University of California
CHESS Executive Director                      US Mail: 337 Cory Hall
Programmer/Analyst CHESS/Ptolemy/Trust        Berkeley, CA 94720-1774
ph: 510.643.9841 fax:510.642.2718	      (Office: 545Q Cory)
home: (F-Tu) 707.665.0131 (W-F) 510.655.5480