dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

Issue with Subversion proxy not using correct format for network locations when not mapped

( SVNSCC )
Type: Public Status:Closed Created: 07 Feb 05 02:00 Updated: 02 Feb 06 02:00
--> Igor Pushkov (admin)  at 02 Feb 06 02:00 writes

This issue fixed in plug-in version 1.3
--> Robert (user)  at 18 Sep 05 09:00 writes

Just FYI but since it has taken so long and you still have not corrected
this we have decided to move to Visual Studio Team System which will not
have these types of issues.

Thanks.
--> Igor Pushkov (admin)  at 14 Feb 05 02:00 writes

Well, once again I not have good news. SVN really can access and
manage working copy on network share. But currently we use the
svn.exe, not the direct client API. Most operations are based on
concept of working directory. I.e. we setup working directory
c:\work\myproj and ask "svn update file1 file2". We launch separate
process for this, which cannot accept network share path as working
directory.
The solution for this problem can be to use SVN client code directly,
instead of wrapping svn.exe. This is already in our plans, but after
release of SVN 1.2.
I put "accepted" status to your ticket and will notify you when we
will solve this problem. Sorry again.
--> Robert (user)  at 11 Feb 05 02:00 writes

Thank you. I'll look forward to hearing back.
--> Igor Pushkov (admin)  at 11 Feb 05 02:00 writes

We are sorry for delay with answer to you. Actually, from the
beginning I am consider your way to use SVN not very standard. Last
month we have spent many time on new automated test environment and new
version of CVS plug-ins.
Right now we plan to have new stopping at the SVN plug-in, and plan to
release new version. So, now it is time to look in deep to your issue.
Once again sorry for delay. I will return to you shortly.
--> Robert (user)  at 10 Feb 05 02:00 writes

Any update? I sent several emails regarding this with no reply also.
--> Robert (user)  at 07 Feb 05 02:00 writes

This is related to a previous issue I reported where your reply was that it
was not possible. I have copied the issue below at the bottom as I
originally stated it for your reference.

The basic issue is that if my web project is located on a server and I do
not want to map the location on the server to a drive letter, and instead
specify the network location of the web project as follows:

//somewhere.somewhere.com/wwwroot$

The proxy fails to pass the location properly to the subversion client on
my local machine which then returns an error because it can not locate the
directory on the server in question.

You originally replied by saying the subversion client does not support
this type of location and that I MUST map the location to a drive letter
instead. This is not possible due to the number of people who must work on
the project and the impossibility of ensuring that everyone is on the same
page.

I have further more found evidence (below) that the subversion client is
fully capable of handling this type of network location and does not
require the location to be only a mapped drive.

Below, I've put an excerpt of what I found at the URL:
http://tortoisesvn.tigris.org/docs/TortoiseSVN_en/ch03s03.html

To access your local repository you need the path to that folder. Just
remember that Subversion expects all repository paths in the form
file:///C:/SVNRepository/

To access a repository located on a network share you can either use drive
mapping, or you can use the UNC path. For UNC paths, the form is
file:///\ServerName/path/to/repos/. Note the backslash before the server
name.

NOTE: the issue is that when passing a servername instead of a drive
letter, you apparently must place a backslash before the server name.

The Subversion plugin disables the local working directory textbox so you
can't edit it and apparently copies the location the project was opened
from. This works fine for a mapped drive but not for a servername UNC path
since the plugin won't then pass the path to subversion with a backslash in
front as is apparently required.

What is the chance that you can look into this and correct it in the near
future?

This is still a showstopper for us using this plugin instead of CVS.

-----------------------
ORIGINAL ISSUE REPORT
-----------------------

So i updated myself to the latest version of the plugin and subversion.

I then made sure the setting to use _svn directories instead of .svn was
chosen for the plugin.

Now when adding a web project to source control I get the error:

svn: "\mrdata2.xyz.com\wwwroot$\CASDB" is not a working copy

Here's my setup:

I'm running VS.NET 2003 on a desktop machine. The web site is on a remote
server. It is the same server which happens to be running subversion
also.

So VS.NET 2003 is opening the web application that resides on the Windows
Server. (It is not running on IIS on my desktop nore can it.)

When completing the dialog for adding a project, the "local path" ends up
being:

//mrdata2.wellsfargo.com/wwwroot$/CASDB

This is where the actual files reside on the server.

Is this what should be in the local path box?

What does the "not a working copy" indicate that I am doing wrong?
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9552288 visitor since 20 Jan 2003.
740 visitors today and 1 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com