[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

unable to commit to a subversion repository

From: Rob Jefferson <techstep_at_gmail.com>
Date: 2005-12-14 19:18:23 CET

I have recently set up Subversion access with GForge and Apache. At
this point, I can check out a project from GForge using the
command-line svn client, make changes, and add files. When I go to
commit my changes, I get:

  mk-600-20:~/blah/subtest2 jeffrl$ svn commit -m "testing"
  Authentication realm: <https://www.bridgproject.org:443> Subversion repository
  Password for 'jeffrl':
  svn: Commit failed (details follow):
  svn: MKACTIVITY of
'/svn/subtest2/!svn/act/cc3f13ae-e307-0410-be2a-8a168ec37191': 403
Forbidden (https://www.bridgproject.org)

It looks like svn is properly authenticating -- when I type in an
incorrect password, I am asked for it again -- but for some reason I'm
not able to commit changes even though I am the owner of the project.

Looking at an earlier thread
(http://svn.haxx.se/tsvn/archive-2005-10/0199.shtml), the solution
there doesn't seem to apply, since the repository URL hasn't changed
(I checked out the repository using https, and am using https to check
it in).

I am unsure of what is going on. Has anyone out there run into a
similar problem with this configuration? If so, what should I look
out for?



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 14 19:23:09 2005

This is an archived mail posted to the Subversion Users mailing list.