[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: WC Locked & Cleanup Fails

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-02-03 07:53:08 CET

On Feb 2, 2007, at 09:53, Choate, Bryan ((IHG)) wrote:

>>> So I then attempted a cleanup, and was once again rebuked:
>>>
>>> D:\subversion\iris-web>svn cleanup
>>> svn: Can't open directory '<long file path>\.svn\tmp': The system
>>> cannot
>>> find the path specified.
>>>
>>>
>>> I added the directory manually, and was foiled a third time:
>>>
>>> D:\subversion\iris-web>svn cleanup
>>> svn: Can't open directory '<some other file path>\.svn\tmp': The
>>> system
>>> cannot find the path specified.
>>>
>>>
>>> I tried to Google this one and came up with nothing. Has anyone
>>> seen
>>> this before?
>>
>> Yes, I've seen it before. Somehow, some of the tmp directories got
>> wiped in my working copy. I never figured out how. I just trashed
>> that working copy and checked out a new one. It only happened to me
>> once so I never worried about it.
>
> That's what I ended up having to do. I guess I'm glad that it's not
> just me, but it's happened twice in the last two weeks, so there
> must be
> something specific that I'm doing or something about my WC. I'm using
> 1.4.2 on XP and the corresponding release of Tortoise.
>
> Since there are two of us, should I log a bug?

I'm not confident that there is a Subversion bug. I had assumed that
some process other than Subversion was for some reason deleting
directories called "tmp" all across the disk.

If that's true, then the only possible improvement that could be made
in Subversion would be that if the tmp directory is not there, it
would be created, rather than throwing an error. This goes against
the Subversion philosophy of "nobody touch my .svn directory!" but in
this one case (tmp directory missing) it might not be a tragedy if
that rule were broken.

However, so few people have reported this problem that I think it's
unlikely to get any developer attention, since there are much more
important things to do than fix working copies that were (probably?)
messed with by another process, and since fixing the problem manually
is simple (create the tmp directories yourself, or check out a new
working copy). It would even be trivial to write a script to add tmp
directories recursively in an entire working copy.

To test the theory that some other process is messing with your tmp
directories, you could create a directory called tmp somewhere
outside your working copy. Then use your computer as usual. At some
point later when you again encounter the problem in Subversion, see
if the tmp directory you manually created is still there or not. If
it's gone too, then I'm pretty sure some other process on your system
is removing it, and then you should try to figure out what software
you've installed is doing that.

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 3 07:53:37 2007

This is an archived mail posted to the Subversion Users mailing list.