Re: Cleanup needed after failed update

On 16 June 2012 00:02, Justin Case <send_lotsa_spam_here_at_yahoo.com> wrote:
>> From: Felix Saphir <felix.saphir_at_kantarmedia.com>
>
>>
>> I guess this has something to do with the svn library itself, not
>> Tortoise SVN. Please ask on their mailing list.
>
> Indeed. FWIW:
> SVN 1.7 has a fancy brand new internal design, which made commits totally not-atomic.

Just to clarify this one point, commits are still atomic and always
will be. You are talking about update. I know that doesn't help at
all, but people get worried when they read about a version control
system having non-atomic commits.

> One file in use and whoops you have the new wc.db already updated but the working queue not, and nobody thought about a rollback mechanism. So the failure is almost by design, and as the design has no place for a rollback it's not likely it will get fixed any time soon. I reverted my computers to svn 1.6 (TortoiseSVN 1.6) because I can't stand that all-day cleanup...

How did this ever work before. If a file is in use it can't be updated
anyway. Are you saying the updated just bailed out in 1.6 and you
could retry later?

> Thank you,
> JC

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2971449
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].