subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Neal <bgn...@gmail.com>
Subject Re: Corrupt working copy after merge cancel - SVN 1.7.4
Date Fri, 06 Apr 2012 14:02:23 GMT
I just did some more testing. I tried to recreate my colleagues
problem by creating a working copy, doing a merge, then cancelling it.
I was unable to reproduce the problem in any event. I used both my
values for TEMP and I also used his (C:\Windows\Temp).

Thanks,
BN

2012/4/6 Brian Neal <bgneal@gmail.com>:
> Hello Thorsten,
>
>> C:\Windows\Temp is no default temporary directory for a user. Normally
>> Subversion would use the user specific Temp directory, unless you
>> configured your user to use Windows\Temp, which is not recommended at
>> all. I would guess that your environment may be a little bit special
>> and therefore you should describe it and maybe ran into permission
>> problems in Windows\Temp.
>
> I believe you have hit on something. We use an embedded compiler tool
> chain on Windows XP that is somewhat old, and it sometimes errors out
> when it encounters spaces in path names. I don't think I have
> encountered this problem, but my colleague and a few others have.
> Therefore they have explicitly set the environment variable TEMP, and
> in this particular case, my colleague has TEMP=C:\Windows\Temp. Taking
> a poll around the office, others have set it to TEMP=C:\Temp. Mine is
> still the default, which I believe is
> TEMP=C:\DOCUME~1\brian\LOCALS~1\Temp.
>
> So now we are left a bit puzzled as to why some of us have encountered
> the "spaces in path" problem with the compiler and others have not.
> But that isn't a concern for this list. :)  But in any event, I will
> advise my colleague to change the value of his TEMP variable if you
> think C:\Windows\Temp can cause a permissions problem for Subversion.
>
> Just for completeness, to answer to your questions (which may not be
> relevant now):
>
>> For example is the Working Copy user specific or system wide?
>
> I am not sure I know what you mean. It is a "normal" working copy
> created interactively by an XP user using Tortoise. I didn't know you
> could create "system wide" or "user specific" working copies.
>
>> Was the merging user really a normal user or "something" in a service context?
>
> Normal, interactive user sitting at a keyboard. :)
>
> Thank you!
>
> Regards,
> BN

Mime
View raw message