> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: Thursday, June 14, 2012 5:43 AM
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: Bug report - TortoiseSVN 1.7.7 - SVN update
>
> On Thu, Jun 14, 2012 at 9:36 AM, Keren Aharon <Kerena_at_praxell.com>
> wrote:
> >
> > I have installed the a new version of SVN client:
> >
> > TortoiseSVN 1.7.7, Build 22907 - 32 Bit , 2012/05/15 12:16:05
> >
> > Subversion 1.7.5,
> >
> >
> >
> > I am running into a bug that didn’t exist before and it happened to
> me a few times already.
> >
> >
> >
> > 1. I executed SVN update while one of the updated docs was
> opened in my desktop. I got the following error:
>
> Yup, that's the problem: the file was exclusively opened in another
> app.
>
>
> > 2. I closed the opened document and ran update again (this is
> something I did all the time in the previous version). I got the
> following error:
> >
> >
> > 3. I tried to run cleanup and got the following error:
> >
> > Now I am in a loop. I cannot update anymore or run cleanup. Restart
> didn’t help.
> > The only solution I found so far is to delete the entire repository
> from my desktop and retrieve again from the beginning.
> > This is a real pain since I work with many open documents all the
> time and I need to update them in real time….
>
> That's a known (and also very old) problem. The svn lib leaves the wc
> corrupt in such situations. And yes, the only solution now is a fresh
> checkout.
>
I have had some luck, with older versions of SVN, with deleting the entire directory containing the problematic file and then updating. I haven't had this problem with 1.7 so maybe with the single .svn directory this will not work?
Wayne
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2971140
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-06-14 21:17:59 CEST