changing user and password

[Google Code Exporter]

What steps will reproduce the problem?
1. define a repository with user and password
2. check out a working copy
3. change the user with another password
4. check out somewhere else
5. try to commit some change from this new working copy

note the repository is like sourceforge open for checkout but closed for 
commits.

What is the expected output? What do you see instead?
Expected would be to be able to change the password without any problem. 
Instead no commit is possible and the working copy has a blank password.

What version of the product are you using? On what operating system?
version 1.2 on OSX 10.6.4

Please provide any additional information below.
The issue is solved by deleting all files from lachoseinteractive in 
Library/Caches or Library/Preferences/

I read issue 106 in order to solve the problem and deleted the .subversion 
folder, which had no effect. 

Original issue reported on code.google.com by [e-mail] on 8 Nov 2010 at 3:09

[Google Code Exporter]

I'm not sure I understand.
It is possible to enter/edit the password used by Repository or Working Copy 
window in svnX.
This does not affect the password required by the repository server only the 
password provided to it.
Additionally the change only takes effect when you next open that repo or WC 
window.
If you can't commit from a WC & "the working copy has a blank password" then 
close the WC window, enter a password for the WC & reopen the window.

Issue 106 was to do with HTTPS authentication.  That is quite different from 
Subversion user-names & passwords.

Original comment by [e-mail] on 8 Nov 2010 at 4:45

[Google Code Exporter]

I agree that issue was about https auth. but I thought I could solve my problem 
by deleting the .subversion/ folder.

I didn't want to change the password required by the server, but only wanted to 
check out a WC on a user account that previously had been used by a different 
svn user. So setting the new user and password on the repo window, opening the 
repository and checking out a working copy did not result in allowing commits 
(the password field was blank).

I think I tried setting the password on the WCs window and reopen the working 
copy but I will try again to be sure. Anyway I think the behaviour of the 
interface is totally misleading. Why not setting the password if given on the 
repos window??? Note that I did what you suggested (set pw in repos, open repo, 
check out WC) no luck...

Maybe I don't understand the mac world (only have to use in teaching) but 
"maybe" a button in the interface to acknowledge the change of credentials 
would help ...

otherwise I really like the software in comparison to the others I could find 
on the OSX platform. So please take only this issue as a comment to make it 
better. 

Original comment by [e-mail] on 9 Nov 2010 at 8:31

[Google Code Exporter]

svnX 1.2 *did not* copy the password from the Repositories window to the 
Working Copies window when I checkedout a new WC. That's is what I meant with 
"no luck" nad this is essentially my problem since it subsequently does not 
allow me to commit. 

The only error message I got was not being able to commit with such a WC. I can 
check more precisely if you want. The "error" was the blank password.

I deleted the ./subversion folder because my problem was a cached repository 
and credential that I could not get rid of by clicking on "minus" in the repos 
window. As said, I had to delete the Library cache and preferences from svnX.  

Since I am not admin on the computers, I will ask for upgrade and let you know 
if I can reproduce the problem.

Original comment by [e-mail] on 9 Nov 2010 at 9:14

[Google Code Exporter]

> svnX 1.2 *did not* copy the password from the Repositories window to the 
Working Copies window when I checkedout a new WC.

I just tested svnX 1.2 & reviewed the code and as far as I can see it will 
always copy the password if it automatically creates an entry in the Working 
Copies window due to a checkout from a repository window.  Are you sure you 
have svnX 1.2 & not 1.2b1 or something?


> That's is what I meant with "no luck" nad this is essentially my problem 
since it subsequently does not allow me to commit. 

Then why don't you simply enter the password for that WC in the Working Copies 
window?


> The only error message I got was not being able to commit with such a WC.

Please quote the exact error message.


>I can check more precisely if you want. The "error" was the blank password.

That is not an error - as I've previously stated.

Original comment by [e-mail] on 9 Nov 2010 at 5:17

[Google Code Exporter]

Original comment by [e-mail] on 14 Apr 2011 at 12:58

• Changed state: Invalid

[Google Code Exporter]

SvnX 1.2 should copy the password from the Repositories window to the Working 
Copies window when you checkout a new WC.
SvnX 1.3 does not copy the password.  It should be unnecessary as the password 
should have been cached by Subversion.  Unless you delete the ~/.subversion/ 
folder.  (So don't do that.)

Also, it doesn't matter what user-name/password the WC has when it is checked 
out.
It only matters what user-name/password it has when you open the WC window.
You didn't do what I suggested.  I said "enter a password for the WC" i.e. for 
the selected WC in the Working Copies window.

You are going to have to provide more info then "no luck" if you expect me to 
solve your problem.
What error message are you seeing?
What version of Subversion are you using?
Get & try svnX 1.3.

Original comment by [e-mail] on 9 Nov 2010 at 9:03