tags:

views:

126

answers:

5

Hi everyone, I'm new to setting up subversion but originally when I made a repository, all my team members could update and commit without problem. There was a problem with it so we decided to recreate it, but now only I can commit changes to it. And my username/password doesn't work on their computers, so I'm sure it's something obvious and silly, but I just don't know enough to know what's causing it.

The passwd and svnserve.conf files are the same as the original repository that worked for everyone.

Any ideas? Thanks in advance.

A: 

I had an issue like this. In the end I ended up removing all the users and groups, then recreating them all.

NitroxDM
A: 

If your repository is on a linux box, and you are using svn+ssh, I think setting permissions on the repository can solve your problem. Ideally, you would want to create a group for all users who need access to the repository and make the repository writable to that group. If you can't create a group, then you'll have to make it world writable.

Alternatively, you can set up Apache web server to access your repository through the web. It will work with tortoissvn as well.

Dima
i made it world writeable just to see if it would work, and it's not giving me any luck :/
Calvin
Make sure that you are using svn+ssh so that the authentication is done by ssh not by svnserve... Don't know what else to tell you...
Dima
A: 

Is a firewall active on the other computers? deactivate it and try again. If it then works, define a proper exception. Maybe then also consider re-enabling the firewall on your machine :-)

jdehaan
+1  A: 

You'll want to focus on things that changed...

svn+ssh requires that you are logged into the repository system and that auth-access = write (in svnserve.conf), at least that's how I've seen it set up. Is it possible that there were sessions logged into the repository initially, and they are no longer there?

There's a great tutorial on setup:

"Setup Guide for Linux Subversion Server, using SSH client access (using the svn+ssh protocol with svnserve -t)

Gunther Strube ([email protected], March 2004)"

but you probably already knew that ;-)

Dak
+1  A: 

You may have to delete the local svn authentication cache on each machine accessing the svn server to force each user to authenticate again. The authentication cache is in the user's home directory: Linux: /home//.subversion Windows: c:\Documents and Settings\.subverison

Most svn client tools have a debug option - please turn this on and review the output. I have seen clients that do not handle NTLM authentication very well. The svn server should always offer BASIC authentication on top of NTLM.

dev_doctor