SVN Proxy hangs on adding new solution to SCC

( SVNSCC )

Type: Public Status:Closed Created: 09 Jun 05 06:00 Updated: 30 Jun 05 06:00

--> Oleg Akolupin (admin) at 30 Jun 05 06:00 writes

Please try new SVN Proxy version 1.2.0_RC1.
There problems with login are solved.

--> Oleg Akolupin (admin) at 22 Jun 05 06:00 writes

We now releasing version 1.2 of plugin and we will solve this issue in this
version. We put accepted status to your ticket.

--> Chris (user) at 14 Jun 05 06:00 writes

This solution is inconvenient because it requires a special configuration
of the repository. Furthermore, not all SVN clients use the SVN disk cache
for credentials, and the solution fails if using one of these clients. For
example, Tortoise SVN uses the Windows registry to cache credentials, and
so calling a write function from Tortoise SVN client won't work in your
solution. It would be better if SVN Proxy (through svn) could simply
request credentials from the user if it needs them, and not rely on some
other client to cache the credentials. Is this not possible?

This solution also doen not fix the second problem I am seeing, which is
that the Change Source Control function does not work. It only works for
the Add Solution to Source Control function.

--> Oleg Akolupin (admin) at 14 Jun 05 06:00 writes

1. Issue with authentication and anon access
Our plug-in relays into authentication
cache functions build in into SVN. This functions cache your
credentials on your local PC after first successful access attempt
into repository.
Login operation, which exist in plug-in just call svn list command
(which not change anyhthing in repository) providing your user name
and password.
But, unfortunately this is "readonly" operation, and if your
repository allows anonymous "readonly" access (which is on by
default) auth credentials not cached.
The solution is:
a) Switch off anonymous access (anon=none)
b) Call any write enabled operation from any other client, which will
cause svn to cache auth credentials on your local disk.

1. How to use other name than current user name
The info can be found for example here:
http://www.pushok.com/help/svnscc/index.php?redirect=basic_addtoscc.htm
[VS .NET]
First of all select a user name for accessing to SVN: open the
configuration window Tools\Options\Source Control\Scc provider and specify
the name in the Login ID field. Then right-click on tree root (solution)
in
Solution Explorer. Select Add to source control.

--> Chris (user) at 13 Jun 05 06:00 writes

Uninstalling Tortoise SVN 1.1.7 made no difference.

Problem may be an authentication bug in how SVN Proxy connects to svnserve.
The \"Add Solution to Source Control\" menu works after doing the
workaround suggested in the previous post: turn off anonymous read access
on the svn server. SVN Proxy then seems to work (mostly), but this is not a
good workaround because anonymous read access is lost.

Even with this workaround, the \"Change Source Control...\" menu still does
not work. Errors are: \"Server Binding\" = \"\", and,
\"Status\" = \"Invalid\".

The system specifics seem to have been lost in posting. They are: VS .NET,
Latest, WIN 2000/XP.

--> Oleg Akolupin (admin) at 13 Jun 05 06:00 writes

1. Please uninstall Tortoise SVN 1.1.7 and try it again.

2. If problem still exist let us know.
NOTE : Necessarily describe specific your system

--> Chris (user) at 09 Jun 05 06:00 writes

SVN Proxy hangs when adding a new solution to source code control. I am
doing the following steps:
(1) Create new blank solution in VS.NET File menu
(2) Verify that SVN username is correct in "Tools/Options/Source Control"
menu
(3) Right-click new solution, and select "Add Solultion to Source
Control".
(4) Enter SVNURL in "Select SVNURL" dialog window
(5) Click Login button, enter password, and click OK (get "The SVNURL is
OK")
(6) Enter SVN MODULE and click Check (get "The MODULE is OK")
(7) Verify that LOCAL PATH is correct
(8) Click OK

SVN Proxy then creates the local .svn folder and pops up a message window
with "Adding files in: ..." and "Checking files in: ..." and then hangs.
The SVN Proxy message window Cancel button does not respond, and VS.NET
does not respond. The only way to regain control of VS.NET is to use Task
Manager to kill svn.svn.exe. The repository is initially empty, except for
the directory specified in SVN MODULE. SVN Proxy does not check anything
into the repository.

There is no problemm creating files or directories in the repository using
Tortoise SVN 1.1.7 with the same username and credentials.

Do you have any suggestions on how to make SVN Proxy work. It is currently
unusable for us.

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

SVN Proxy hangs on adding new solution to SCC