On 10/18/06, Spike Henning <chenning@uwf.edu> wrote:
> There was no problem creating the repository and working copy (fsfs) and
> accessing it myself. It turns out that when I access the same working
> copy from another machine, TortoiseSVN on that machine is unaware that
> the directory contains a working copy and won't give me any options to
> update, commit, etc. I first thought it was a security issue because I
> was logging in under a different set of credentials to see if there was
> a problem there, which there was. I then logged in on that machine under
> the same set of domain credentials I used when I first created the
> repository/working copy and the directory (working copy) still isn't
> recognized as a working copy it.
>
> With the _svn (dot net hack) directory in the directory structure, why
> doesn't TortoiseSVN recognize the directory as a working copy? What am I
> doing wrong.
Do all the clients have the dot net hack environment variable set? At
a minimum, I think this has to be set on each machine that accesses
the working copy - if it can't be applied as a system-wide environment
variable, then it'll need to be set for each user on each computer.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Oct 18 20:44:20 2006