RE: Commit failed + checksum mismatch

> -----Original Message-----
> From: smartsvn@... [mailto:smartsvn@...] On Behalf
> Of Eric Mader
> Sent: Wednesday, February 11, 2009 9:09 AM
> To: smartsvn@...
> Subject: Re: [smartsvn] Commit failed + checksum mismatch
>
> I have seen the same problem on Vista Ultimate x64. At the time, I had
> Visual Studio 2008 running. When I did an update from the repository on
> another machine I saw that the file had actually been committed.
>
> Regards,
> Eric Mader
>
> syntevo Support wrote:
> >
> >
> >  > We've also noticed that closing Visual Studio before committing
> changes
> >  > seems to prevent the error... still testing that theory.
> >
> > That sounds interesting and we would really appreciate your input here.
> Is
> > there any SVN integration in Visual Studio which might interfere with
> > SmartSVN?
> >
> > Visual Studio is definitely a common application; do other VS users
> > experience
> > similar problems in combination with SmartSVN?
> >
> > --
> > Best regards,
> > Marc Strapetz
> > _____________
> > syntevo GmbH
> > www.syntevo.com
> >
> > "ZedUbal" <skrymsli@... <mailto:skrymsli%40gmail.com>> wrote:
> >
> >  > Hello!
> >  >
> >  > Recently we switched over to Subversion from CVS. I have been a
> >  > longtime fan of smartcvs so I got smartsvn. Everything seems to be
> >  > working well except some random errors that occur during commits. I
> >  > am on Windows Vista x64 using version 5.0.4. Noticed these same
> >  > problems in 5.0.3 and 4.0.x.
> >  >
> >  > I've read posts on similar problems from other users, but nothing in
> >  > those threads seems to apply or fix the problem.
> >  >
> >  > Details:
> >  >
> >  > Randomly during commits I will get a message "Commit failed (details
> >  > follow): Unknown error". The commit fails and the files that I was
> >  > trying to commit are still displayed as "modified" in smartsvn. The
> >  > more files I commit at once, the more likely this error happens.
> >  >
> >  > After this happens I try to update and I get a message like:
> >  >
> >  > Update to HEAD: working copy '<directory>' locked; try performing
> >  > 'cleanup'
> >  >
> >  > I go to that directory and I select Modify->Cleanup. This always
> >  > removes the lock icon. Now I can update and when I do most of the
> >  > files change to an "unmodified" state, so they were actually
> committed
> >  > successfully. One file will still show modified. When I attempt to
> >  > commit that file I get a checksum mismatch error.
> >  >
> >  > This has probably happened to me about 30 times in the span of two
> >  > months. It is very frustrating. To fix the checksum mismatch I end
> >  > up marking the file as replaced. The only other way I have found to
> >  > fix this problem is to check out the file in a new location, copy
> over
> >  > the modified file and then commit again. It seems that the local
> >  > metadata for the file gets corrupted somehow.
> >  >
> >  > I have a co-worker who is working on the same repository using
> >  > smartsvn on Linux. He never saw any problems like this. As soon as
> >  > he started working on the code in Vista (using smartsvn) he started
> to
> >  > see exactly the same problems on his machine. It seems to be
> >  > something specific to windows or vista. We've also noticed that
> >  > closing Visual Studio before committing changes seems to prevent the
> >  > error... still testing that theory.
> >  >
> >  > Any ideas? What information or log files can I provide to help you
> >  > debug this problem?
> >  >
> >  >
> >  >
> >  > ------------------------------------
> >  >
> >  > Yahoo! Groups Links
> >  >
> >  >
> >  >
> >  >
> >
> >
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>