I've updated the working copy (which is also the live website), and now I'd like to commit those changes to the repository.  When I try to do so I'm prompted for a password.  I'm running as user oorexx (broke out with cntrl-c at the password prompt):

[oorexx@home website]$ svn commit --message 'fixup links, copyright dates, add some new products'
Password:
svn: E210002: Commit failed (details follow):
svn: E210002: Unable to connect to a repository at URL 'svn+ssh://rvjan...@svn.code.sf.net/p/oorexx/code-0/websites/main/trunk/docroot'

the working copy info is:

[oorexx@home website]$ svn info
Path: .
Working Copy Root Path: /home/oorexx/website
URL: svn+ssh://rvjan...@svn.code.sf.net/p/oorexx/code-0/websites/main/trunk/docroot
Repository Root: svn+ssh://rvjan...@svn.code.sf.net/p/oorexx/code-0
Repository UUID: 0b6cbdbe-3aab-466e-b73a-abd511dda0a2
Revision: 12143
Node Kind: directory
Schedule: normal
Last Changed Author: rvjansen
Last Changed Rev: 11240
Last Changed Date: 2017-05-02 19:48:35 +0000 (Tue, 02 May 2017)

So... should rvjansen.../code-0 have my public ssh key?  should I have a password?  or should I be committing at all?

Should I check out from the sf site to my own computer and commit from here.  If so, how to I synchronize the oorexx.org/home/oorexx/website working (and live) copy?

Knoobs want to know!


--
taf
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to