> In the future, could you just type the error messages instead of attaching
jpegs.
Definitely, and I apologize. I am new to using mailing lists and didn't even
think twice about it.
The following error occurred when trying to update a working copy using
Tortoise. The working copy was cleaned up, tried to update again, same
message. Deleting entire working copy and checking out HEAD again had no
problems. I searched the mailing list for related posts and could not find
anything related besides commit messages. Any ideas as to what might have
caused this?
Both working copy and server running svn, version 1.6.3
> Subversion encountered a serious problem.
> Please take the time to report.....
>
> Subversion reported the following:
>
> In file
>
'...\TortoiseSVN-1.6.10\ext\subversion\subversion\libsvn_delta\text_delta.c'
> line 657: assertion failed (window->sview_len == 0 ||
(window->sview_offset >= ab->sbuf_offset && (window-> sview_offset +
window->sview_len >= sbuf_offset + ab->sbuf_len)))
A different error (or message) occurred when trying to update through
Subclipse:
Command from Eclipse console:
> update [working copy] -r HEAD --force
Error:
> org.tigris.subversion.javahl.ClientException: svn: Svndiff has
backwards-sliding source views
If this helps at all... looking into this a bit more last week, I found the
culprit that was actually causing the error. It is an xml file that looks
like it has gone back and forth in its revision history. Say a change was
made in revision 3, the next revision may actually be a copy of revision 1
with one alteration. The next change may pull everything from 3 back in,
etc. etc. Should this just not be done? We are actually in the process from
migrating from VSS to SVN (finally!!), so this history is actually coming
from our current VSS repo, which does not have a problem it.
Thanks guys.
Patrick Fletcher
Marquis Software Development
Business Phone: (850) 877-8864 x132
Business Fax: (850) 877-0359
Received on 2010-08-20 16:35:09 CEST