You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Brian Neal <bg...@gmail.com> on 2012/04/05 23:23:58 UTC
Corrupt working copy after merge cancel - SVN 1.7.4
Hello -
We are using SVN 1.7.4 and TortoiseSVN 1.7.6 on Windows.
My colleague was doing a merge and hit cancel. His working copy now
appears to be corrupted. All operations fail with a message that
cleanup is needed. Trying to run cleanup at the top level folder
results in Tortoise putting up an error dialog that says:
"Cleanup failed to process the following paths: D:\Project_Files\BlackCoS
Can't open file 'C:\WINDOWS\TEMP\svn-D4AA62C8'. The system cannot find
the file specified."
Luckily he has no outstanding changes and can make a new working copy.
But if you have any suggestions on how to un-wedge it, or if we can do
any trouble-shooting for you if this is a bug, please let me know.
Thanks,
BN
Re: Corrupt working copy after merge cancel - SVN 1.7.4
Posted by Brian Neal <bg...@gmail.com>.
I'll keep the working copy around in case anyone wants us to
troubleshoot it somehow. I don't know if you can interrogate the
sqlite database or metadata somehow and see why it is "stuck". Again,
we can't seem to reproduce the problem.
Thanks,
BN
Re: Corrupt working copy after merge cancel - SVN 1.7.4
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Brian Neal,
am Freitag, 6. April 2012 um 14:57 schrieben Sie:
> 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.
What I meant aren't any Subversion concepts, but because of your
Windows\Temp I thought you may have a setup where you working copy is
checked out to something like C:\WorkingCopy and used by different
users, tools or whatever at the same time. But that doesn't seem to be
and in your case their even shouldn't be permission errors because
files created by one user on Windows\Temp normally are fully
controlled by that user. Filemon/Process Monitor and a look to the
directory should have given some more hints.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Corrupt working copy after merge cancel - SVN 1.7.4
Posted by Brian Neal <bg...@gmail.com>.
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 <bg...@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
Re: Corrupt working copy after merge cancel - SVN 1.7.4
Posted by Brian Neal <bg...@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
Re: Corrupt working copy after merge cancel - SVN 1.7.4
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Brian Neal,
am Donnerstag, 5. April 2012 um 23:23 schrieben Sie:
> "Cleanup failed to process the following paths: D:\Project_Files\BlackCoS
> Can't open file 'C:\WINDOWS\TEMP\svn-D4AA62C8'. The system cannot find
> the file specified."
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. For example is the Working Copy user
specific or system wide? Was the merging user really a normal user or
"something" in a service context?
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow