first log onto minotaur.apache.org and run svnpasswd
then try it again. I just added you to the jdo repo. If you can set the svnpasswd, you should be good to go.
geir
On Mar 7, 2005, at 1:55 PM, Craig Russell wrote:
Hi Geir,
I tried my new svn login and could not commit to the jdo repository. Here's the console output:
[d-usca14-133-145:~/apachejdo/jdo] clr% cat *
test!
updated 3/7/05
[d-usca14-133-145:~/apachejdo/jdo] clr% svn commit
Sending README.txt
Authentication realm: <https://svn.apache.org:443> ASF Committers
Password for 'clr':
Authentication realm: <https://svn.apache.org:443> ASF Committers
Username: clr
Password for 'clr':
Authentication realm: <https://svn.apache.org:443> ASF Committers
Username:
Password for '':
subversion/libsvn_client/commit.c:765: (apr_err=170001)
svn: Commit failed (details follow):
subversion/libsvn_ra_dav/util.c:294: (apr_err=170001)
svn: CHECKOUT of '/repos/asf/!svn/ver/155140/incubator/jdo/README.txt': authorization failed (https://svn.apache.org)
subversion/clients/cmdline/util.c:352: (apr_err=170001)
svn: Your commit message was left in a temporary file:
subversion/clients/cmdline/util.c:352: (apr_err=170001)
svn: '/Users/clr/apachejdo/jdo/svn-commit.tmp'
[d-usca14-133-145:~/apachejdo/jdo] clr%
Craig
On Mar 6, 2005, at 7:50 AM, [EMAIL PROTECTED] wrote:
Please note that until the Project Management Committee responsible
for the project to which you were given group membership actually grants
you access to the relevant source code modules, you won't be able to
commit anything.
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
-- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED]
