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

Re: Switching problem

From: Nick Gilbert <nick_at_x-rm.com>
Date: Fri, 13 Jun 2008 11:01:32 +0100

Stefan Küng wrote:
> Nick Gilbert wrote:
>> Hi all,
>> Whenever I switch, it always goes wrong and I have no idea why.
>> Today, I committed everything and then tried to switch and it said
>> something about local unversioned files and failed to switch (but
>> everything was committed and no unversioned files showed up in the
>> commit dialog). But after it's said that, it seems to leave your
>> working copy in an unusable state rather than putting it back to how
>> it was before the switch. It tells you to try a clean up which
>> appears to work but then you can't revert and restore the folders
>> which were deleted during the switch. It seems that subversion, or
>> TSVN doesn't perform any checks to see if the switch is going to work
>> before it actually does it and it does it non-atomically, so if it
>> fails, it leaves you with a broken working copy that has to be deleted.
>> Is there any way to reliably switch or should I just stick to setting
>> up a new checkout and working environment every time I want to change
>> to a different branch? Are there some checks I'm supposed to be
>> doing before I switch that I've missed? Switching seems to be very
>> unreliable and I've only seen it work once or twice in the dozen or
>> so times I've tried it recently. If it's not going to work, why
>> doesn't it tell you so before it starts altering the working copy? If
>> it's because of "unversioned files" surely it can check for this
>> before it does work which will break the working copy?
>> So far, it's failed about three times in the last week and each time
>> I have to recover from it, it takes me about half an hour to set up
>> all the correct folder permissions on a new working copy.
> "it takes me about half an hour to set up all the correct folder
> permissions on a new working copy"
> Does that mean you have set up special permissions on your working
> copy folders? Then you have the reason for the switch failing: when
> you switch a working copy, Subversion requires *full* access to *all*
> folders in your working copy.
> Stefan
No, my account already has full permission and I don't think subversion
has any problems creating files. It's a website project so what I need
to to set up a new WC are to configure are things like copying in a
large number of unversioned files (image libraries etc) and permissions
for the "network service" or ASPNET account to have write permissions to
various folders where it creates logs, thumbnail images and configure it
in IIS etc etc... It just seemed to me that switch very often doesn't
work, and I don't really see why. I also don't see why it can't tell
you in advance that something is wrong. I'll take more detailed
information down next time I do this, and the status of the WC before I
switch as I appreciate that I probably haven't given you enough
information about my problem.


To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-06-13 12:01:46 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.