Reputation: 1007
Here is the situation: One man checked out repository and now I have to update some of the folders. Problem is that he left and no one knows the password. So, I would like to use my own account. I execute this command:
svn up --username (my_user_name) --password (my_password) --no-auth-cache
SVN asks for my password and SVN doesn't accept it. It looks like my credentials are ignored and original credentials are used (the one who did check out). I tested my account doing check out in /tmp
and worked fine.
Why SVN does not accept my credentials while doing update?
Upvotes: 12
Views: 38176
Reputation: 631
Please try the command bellow. It is the proper way to remove cached credentials.
$ rm -f ~/.subversion/auth/svn.simple/*
After that:
$ svn up --username <your username>
Upvotes: 3
Reputation: 8103
I had the same problem and I found that this option servers:global:http-library=serf
can solve the issue if the protocol is http/https.
Your command then would be:
svn up --username (my_user_name) --password (my_password) --no-auth-cache \
--config-option servers:global:http-library=serf
Upvotes: 7
Reputation: 9592
Get the required permissions and become owner of the workspace by changing user and group settings:
chown -R user:group path/to/workspace/root/
Try again accessing the workspace with your credentials.
Upvotes: 1
Reputation: 83599
I have never tried this, but it looks like SVN stores the user ID internally once you check out something. I am not sure you can override this when checking in.
Why don't you just change the ex-employee's password on the server (he doesn't need his password anymore ;-)). Then do the checkin under his name, with the changed password. This is arguably cleaner anyway, because then the checkin will appear under his names, and the changes were done by him.
Upvotes: -1
Reputation: 1436
Try this
mv $HOME/.subversion $HOME/.subversion-old
cd <your working copy>
svn up --username <your username>
This should ask for the password for your username
Upvotes: 6