> The error you report is:
> 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 end_directory_update is called in that case.
Just to be clear: the error doesn't happen - as you correctly state - after a commit. Once I get an error (from updating any of the repositories), all other updates of all other repositories will fail. Until I do another commit and then - only that repository - will correctly update. Changes do not seem to affect this in any way. So, whether the update really comes with a new version of any file doesn't seem to matter.
Another lead that might make your search easier:
The error never occurs when updating subfolders. So, only if do an update of a root folder the error occurs.
> You report that a commit makes the next update work. Does an update
> after the successful update work?
Yes, it works for quite a while. At least several hours (although I'm not sure it is time dependent in any way) . At some point it breaks down again.
> 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?
It is 1.0.8 (2004)
>Is it a googlecode server? Are you using serf or neon?
I sent the person that runs the server an e-mail regarding these questions.
It is a Linux server, that I know.
I'll get back to you ASAP.
A colleague just did a fresh install of Tortoise SVN 1.7.1 and he has got the same problem. He uses the same SVN server as I do.
Thnx for all the help.
Received on 2011-11-02 17:35:57 CET