You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Philip Martin <ph...@wandisco.com> on 2011/11/01 12:08:02 UTC
Re: Error when updating
Wabe W <wa...@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
RE: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
Thanks, Philip.
Looking forward to it. Now it takes me quite some extra time to work with SVN.
-Wabe
> From: philip.martin@wandisco.com
> To: wabekoelmans@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Error when updating
> Date: Thu, 3 Nov 2011 16:09:58 +0000
>
> Wabe W <wa...@hotmail.com> writes:
>
> > So, we just have to update the server and see if the problem is solved?
>
> It's issue 4048, it may get fixed in a 1.7.x release:
> http://subversion.tigris.org/issues/show_bug.cgi?id=4048
>
> --
> Philip
RE: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
The update problem has been solved.
The solution was to upgrade the server to a recent version.
Now, it works like a charm.
-Wabe.
> From: philip.martin@wandisco.com
> To: wabekoelmans@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Error when updating
> Date: Thu, 3 Nov 2011 16:09:58 +0000
>
> Wabe W <wa...@hotmail.com> writes:
>
> > So, we just have to update the server and see if the problem is solved?
>
> It's issue 4048, it may get fixed in a 1.7.x release:
> http://subversion.tigris.org/issues/show_bug.cgi?id=4048
>
> --
> Philip
Re: Error when updating
Posted by Philip Martin <ph...@wandisco.com>.
Wabe W <wa...@hotmail.com> writes:
> So, we just have to update the server and see if the problem is solved?
It's issue 4048, it may get fixed in a 1.7.x release:
http://subversion.tigris.org/issues/show_bug.cgi?id=4048
--
Philip
RE: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
> >> I assume you are using some sort of server. Which version of Subversion
> >> is the server running?
>
> > It is 1.0.8 (2004)
>
> That's old (very old) and unsupported.
I will tell my professor :-)
> The client should still work but
> I haven't built or used 1.0.x for years.
So, we just have to update the server and see if the problem is solved?
> >>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.
>
> It won't be a googlecode server. serf/neon is a client question.
We use the standard: neon
>
> --
> Philip
-Wabe
Re: Error when updating
Posted by Philip Martin <ph...@wandisco.com>.
Wabe W <wa...@hotmail.com> writes:
>> I assume you are using some sort of server. Which version of Subversion
>> is the server running?
> It is 1.0.8 (2004)
That's old (very old) and unsupported. The client should still work but
I haven't built or used 1.0.x for years.
>>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.
It won't be a googlecode server. serf/neon is a client question.
--
Philip
RE: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
> 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 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:)?
http
> 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.
BTW,
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.
Regards, Wabe.
RE: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
I got word from the person that runs the server.
He replied the following:
> Which Subversion protocol are you using (http:, https:, svn:, file:)?
http://
> I assume you are using some sort of server.
Which version of
> Subversion is the server running?
subversion 1.0.8-2.2 (r11084) on a Suse Linux 9.2
Distribution (i586)> Is it a googlecode server? Are you using serf
> or neon?
This depends on the client, not the server.
Re: Error when updating
Posted by Philip Martin <ph...@wandisco.com>.
Philip Martin <ph...@wandisco.com> writes:
> 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.
Oops! I meant to say I can't see how end_directory_update is called.
--
Philip