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

Re: Is subversion ready for primetime

From: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2005-02-01 04:46:27 CET

On Jan 31, 2005, at 6:58 PM, Max Bowsher wrote:

> Joseph Silverman wrote:
>>
>> As to why I am frustrated ..
>>
> ...
>> It is a rather simple matter to lock up a svn working copy...

> AFAIK, this is the first time a problem of this nature has been
> reported!
>
> I don't suppose you could find some way to script the reproduction of
> this?
>

I was happily using subversion with no problems, until today when I
started integrating a lot of code from our old database (Visual Source
Safe) to subversion. I was preparing for the rest of the company to
make the migration.

That's when I too noticed how easy it is to get the WC hosed beyond
repair. I posted a bit about it earlier under the subject 'Vendor
branch hell' something along the lines of 'vendor branches' were
giving me trouble at the time. I still don't know exactly what caused
the problem.

Not until I started doing URL to WC copies did I notice how fragile
subversion can be. It has been rock solid and operated as expected (or
at least as documented, once I figured out how my expectations were off
:) ) until I started playing with the copy command. I think in one
case I may have typed a backslash instead of a forward slash for one
part of a path or URL.. (I'm running everything on Win XP). The only
reason I say so is that when I went to commit I saw an error message
from subversion complaining about a URL (the destination of a URL->WC
copy) with the last component of the URL separated by a backslash
instead of the normal forward slash. That caused the commit to barf
and attempts to fix things complain about a folder in the WC not being
locked (the destination of the URL->WC copy).

Once subversion complains about something not locked.. you are fairly
hosed. The only solution I have found is to do a forced delete (svn rm
--force) of the offending folder in the WC.

I had previously thought that the only way I could get things so
screwed up would be to mess about in the .svn folder directly.
Apparently it is much easier than that.

But even after my frustrations today, I find subversion is still ready
for prime time... I just have to be a little careful, and now I know
how to deal with some of the odd situations that come up.

(I just wish I got *some* response when I posted about my troubles --
*shrug*)

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 1 04:49:24 2005

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