[TSVN 1.8] - Cannot update/commit/checkout working copy
From: Camilo Sasuke Tsumanuma <camilocc_at_gmail.com>
Date: Thu, 20 Jun 2013 14:56:51 -0700 (PDT)
Hi Dear TSVN Mailing List,
I have installed TSVN 1.8 over TSVN 1.7.13 and updated also the Subversion Server. I uninstalled previous SVN Server from CentOS 6.4 using yum and then I used as guideline the page http://comments.gmane.org/gmane.comp.version-control.subversion.user/113594 for building/installing the server. The server is apache/mod_dav_svn accessed through HTTP SSL. I still can access/authenticate the repositories using Firefox as usual.
In Client Side:
I upgraded 1.7.13 working copy to 1.8 working copy. Then, I asked to update.
What I wanted:
To update, to commit or (I also tried fresh checkout).
What I expected:
I expected to work as usual : to do updating, committing or checking out.
What happened:
Instead, it asked for my username and password. Ok, I automatically thought that it could be something related with the major update, so entered it and asked to save. I entered many times without success and no password remembering. Finnally, after a certain number of clicks in cancellation button of the login dialog, it appears a red error message at TSVN dialog window saying something like this : "No more credentials or auth failed too many times".
So, it stopped working after the upgrade.
Just now, I verified a similar behaviour also in command line from inside the CentOS 6.4 Server:
svn upgrade <Working Copy>
It asked for password for a previously saved user.
May it is more proper for me to send this e-mail to Apache Subversion Forum?
The usernames are e-mail addresses and contains [@_.0-9].
Portion of HTTPS configuration :
<Location "/app">
</Location>
I would appreciate very much any help.
Thank you in advance,
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
|
This is an archived mail posted to the TortoiseSVN Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.