tags:

views:

1398

answers:

5

I'm trying to commit to an SVN server hosted on my school's network. I have installed SVN 1.5.2 with binaries downloaded from CollabNet here. The error reported is:

svn: Commit failed (details follow):
svn: MKACTIVITY of '/opensvn/cs598r/!svn/act/defe271c-f33b-4851-a706-b2906301fed0': authorization failed (http://dna.cs.byu.edu)

That's the complete error message - nowhere does it say 403 Forbidden. I have tried deleting my working copy and checking it out again to no avail. I have checked and double-checked that my password and permissions are correct on the server. I have checked that the URL is correct. I can successfully commit from a remote machine, but not from mine. Other members of my team are able to commit from their computers, but when they try from mine, they get the same error. One of the other members of my team is using 1.5.1 CollabNet binaries with no trouble. What about my client is broken?

A: 

Can you confirm with your schools sys admin that you are authorized to write to the repository? This may be the case if you are able to read from the repository (check out) but not to write (commit).

Mark Roddy
I've confirmed with the administrator, and I have write permissions. Furthermore, other members of the team who can successfully commit on their computers cannot on mine.
A. Morrow
When the other members of your team commit, are they using their usernames, or your cached authentication? Along those lines, you should try to do a commit from some other computer to make sure it is a problem with your setup. Out of curiosity, what protocol do you connect via svn, svn+ssh, https?
Mark Roddy
The other members are using their usernames and passwords. I will try a commit from another computer as soon as I can. The repo is accessed via http.
A. Morrow
In the mean time, if you can connect to the machine that the repository is on (via say SSH), connect to it and check if you can commit from there. That will confirm whether or not it is a permission issue.
Mark Roddy
I just successfully committed to the repo from a remote machine using SSH. It is a local problem.
A. Morrow
Hi Morrow.. You said it is local problem.. What kinda problem you had at that time. Because I am facing the same issue from several days that I am not able to commit my changes as you had it long ago. I appreciate your help
alienavatar
Morrow can you tell me what is the local problem that you have encountered. Please let me know as I am having the same issue since long.
alienavatar
A: 

Not all forms of accessing a repository allow all forms of access. If you checked out your code via a read-only method, you won't be able to commit. As an example, it isn't uncommon for a WebDav repository to allow only anonymous checkout on http://... and allow authentication and commits only on https://...

Check that the repository you are checking out from is letter-for-letter identical to the repositories that the other members of your team are checking out from.

Zed
I just deleted my working copy, copied the URL from the source on our Google group again, checked it out, still can't commit. I SSH'd into a remote machine, used the same URL, and successfully committed. It's a local problem.
A. Morrow
A: 

Make sure you're using the proper CAPS for the entire svn url

olore
Checked as per the previous two answers, and the URL is correct. I can commit on a remote machine, but not on mine.
A. Morrow
A: 

Since you can commit from other machines, and your team members can commit but not from your machine, I'd say it's probably an issue with your subversion client. I'd suggest you uninstall the client you have, then install the version that's being run on the server just to be safe.

Mark Roddy
It's time to just do a wipe an install. Thanks for all your help, though.
A. Morrow
A: 

I think the problem is within the parentheses (http://dna.cs.byu.edu). You can often checkout with the http path, but commits usually want https.

Sarah Elkins