Wabe W <wabekoelm...@hotmail.com> writes: >> This is reproducible? You checkout some revision R1 and update to R2 >> and see the error? >> >> Can you describe the changes between R1 and R2? > > I just did a checkout of the latest revision of the repository. So, if > I click update the chances are large that there is no newer revision. > But whether there is new revision or not, this doesn't influence the > fail of the update.
The error you report is: 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\wc_db.c' line 11039: assertion failed (base_status == svn_wc__db_status_incomplete) That happens inside the function end_directory_update, which is called from close_edit only if the editor didn't open the root. You report that it doesn't happen immediately after a commit and that makes sense since the commit will likely leave a mixed revision working copy so the update will not run this bit of code. I'm surprised it happens when the update makes changes to the working copy, I can't see how close_edit is called in that case. You report that a commit makes the next update work. Does an update after the successful update work? Which Subversion protocol are you using (http:, https:, svn:, file:)? I assume you are using some sort of server. Which version of Subversion is the server running? Is it a googlecode server? Are you using serf or neon? -- Philip
