You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Wabe W <wa...@hotmail.com> on 2011/10/21 16:37:37 UTC
Error when updating
Hello,
When I click SVN update I get an error message (see below).
When I first commit something (doens't matter what), I can update only the same folder after the commit. For all other folders the update still doesn't work.
Once I get the error message it will pop up for all SVN folders. Until I commit something, again, only that folder will be available for update.
The problem arose immediately after installing SVN 1.7
Do you have a solution for this?
With kind regards,
Wabe Koelmans.
P.S. Error message:
---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
(users@subversion.apache.org)
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html
Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):
In file
'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)
---------------------------
OK
---------------------------
RE: Error when updating
Posted by Dominik Psenner <dp...@gmail.com>.
FWIW, my observations are that an incomplete working copy is usually
*broken* and one has to do a fresh checkout. Mostly this happens when the
.svn meta-files do no longer match the working copy files. This usecase
_can_ happen when a program holds an exclusive lock on a file and one runs
"svn up" that would have to update the locked file too. svn (1.6) would at
this point fail and leave the .svn files in a strange undefined state,
namely "incomplete". I did not yet try how 1.7 behaves.
Cheers
_____
From: Wabe W [mailto:wabekoelmans@hotmail.com]
Sent: Tuesday, October 25, 2011 1:30 PM
To: users@subversion.apache.org
Subject: FW: Error when updating
Hello,
After the update to SVN 1.7.1 the error that I reported in the e-mail below
persists.
So, I still have the same problem and am hoping there is fix for it.
Awaiting your reply,
Wabe Koelmans.
_____
From: wabekoelmans@hotmail.com
To: users@subversion.apache.org
Subject: Error when updating
Date: Fri, 21 Oct 2011 14:37:37 +0000
Hello,
When I click SVN update I get an error message (see below).
When I first commit something (doens't matter what), I can update only the
same folder after the commit. For all other folders the update still doesn't
work.
Once I get the error message it will pop up for all SVN folders. Until I
commit something, again, only that folder will be available for update.
The problem arose immediately after installing SVN 1.7
Do you have a solution for this?
With kind regards,
Wabe Koelmans.
P.S. Error message:
---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
(users@subversion.apache.org)
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html
Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\lib
svn_wc\wc_db.c'
line 11039: assertion failed (base_status == svn_wc__db_status_incomplete)
---------------------------
OK
---------------------------
Re: FW: Error when updating
Posted by Stefan Sperling <st...@elego.de>.
On Tue, Oct 25, 2011 at 11:29:59AM +0000, Wabe W wrote:
>
> Hello,
>
> After the update to SVN 1.7.1 the error that I reported in the e-mail below persists.
> So, I still have the same problem and am hoping there is fix for it.
>
Does the problem occur with an upgraded working copy or with
a new checkout? Can you please try a new checkout if you haven't already?
FW: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
Hello,
After the update to SVN 1.7.1 the error that I reported in the e-mail below persists.
So, I still have the same problem and am hoping there is fix for it.
Awaiting your reply,
Wabe Koelmans.
From: wabekoelmans@hotmail.com
To: users@subversion.apache.org
Subject: Error when updating
Date: Fri, 21 Oct 2011 14:37:37 +0000
Hello,
When I click SVN update I get an error message (see below).
When I first commit something (doens't matter what), I can update only the same folder after the commit. For all other folders the update still doesn't work.
Once I get the error message it will pop up for all SVN folders. Until I commit something, again, only that folder will be available for update.
The problem arose immediately after installing SVN 1.7
Do you have a solution for this?
With kind regards,
Wabe Koelmans.
P.S. Error message:
---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
(users@subversion.apache.org)
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html
Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):
In file
'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)
---------------------------
OK
---------------------------
Re: Error when updating
Posted by Philip Martin <ph...@wandisco.com>.
Wabe W <wa...@hotmail.com> writes:
> First, please bear with my ignorance here. I only just figured out
> that I don't get a reply to my e-mail in my inbox. I'm apparently
> supposed to visit this page...
People are replying to utwente.nl address in your Reply-To header.
> Anyway, thank you for replying. To return to the problem:
>>Does the problem occur with an upgraded working copy or with
>
>>a new checkout?
>
> The answer is: with both.
>
>>Can you please try a new checkout if you haven't already?
>
> When it first happened (after upgrading) I tried a new checkout. But
> only for one of the directories.
>
> Right now I checked out the two directories I'm currently using. And I
> still get the same error message if I simply click SVN update. Only
> if I commit (just anything) first and then update, it works fine - and
> only for that directory it works.
Did you checkout the new working copy to the same location as the old
working copy? If so did you move/delete the old working copy first?
What state is your working copy before the update that fails? Any
modifications? Can you reproduce the problem with a local test
repository?
--
Philip
RE: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
> Date: Thu, 27 Oct 2011 12:56:11 +0200
> From: stsp@elego.de
> To: wabekoelmans@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Error when updating
>
> On Thu, Oct 27, 2011 at 10:20:36AM +0000, Wabe W wrote:
> > From: Philip Martin
> > >Can you reproduce the problem with a local test repository?
> >
> > I tried to reproduce the problem by making a local test repository.
> > However, there's no problem anymore. It works perfectly fine.
>
> Are path-based access restrictions in place on the SVN server you
> are using where the update fails?
> If so, is there a path which you have no access to within the working copy?
There are no restrictions in place. And certainly not within the working copy.
Also,
if this would be the problem, it would be funny that the update fails
not all of the time, but only if I don't do a 'commit' right before
updating.
Re: Error when updating
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Oct 27, 2011 at 10:20:36AM +0000, Wabe W wrote:
> From: Philip Martin
> >Can you reproduce the problem with a local test repository?
>
> I tried to reproduce the problem by making a local test repository.
> However, there's no problem anymore. It works perfectly fine.
Are path-based access restrictions in place on the SVN server you
are using where the update fails?
If so, is there a path which you have no access to within the working copy?
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
Re: Error when updating
Posted by Philip Martin <ph...@wandisco.com>.
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>.
> 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.
> Is there a single revision that causes the problem: checkout R1 and
> update revision by revision to R2 to determine when the error occurs.
So, there's certainly no single revision causing problem. Also, because I tried 5 different repositories with all the same problem.
--Wabe
> From: philip.martin@wandisco.com
> To: wabekoelmans@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Error when updating
> Date: Thu, 27 Oct 2011 12:14:55 +0100
>
> Wabe W <wa...@hotmail.com> writes:
>
> > I also tried a checkout of a(n existing) repository to a different
> > location. I get the same error message when I try to update.
>
> 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?
>
> Is there a single revision that causes the problem: checkout R1 and
> update revision by revision to R2 to determine when the error occurs.
>
> > Maybe it is like this because our SVN server has not yet been upgraded to 1.7.
> > Although release notes say:
>
> > "Older clients and servers interoperate transparently with 1.7
> > servers and clients. However, some of the new 1.7 features may
> > not be available unless both client and server are the latest
> > version. There are also cases where a new feature will work
> > but will run less efficiently if the client is new and the
> > server old."
>
> > It seems to me that SVN Update is not a 'new feature' and, therefore,
> > it should work, right? (Anyway, I will request an update of our
> > server.) Regards,
>
> The server version should be irrelevant.
>
> --
> Philip
Re: Error when updating
Posted by Philip Martin <ph...@wandisco.com>.
Wabe W <wa...@hotmail.com> writes:
> I also tried a checkout of a(n existing) repository to a different
> location. I get the same error message when I try to update.
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?
Is there a single revision that causes the problem: checkout R1 and
update revision by revision to R2 to determine when the error occurs.
> Maybe it is like this because our SVN server has not yet been upgraded to 1.7.
> Although release notes say:
> "Older clients and servers interoperate transparently with 1.7
> servers and clients. However, some of the new 1.7 features may
> not be available unless both client and server are the latest
> version. There are also cases where a new feature will work
> but will run less efficiently if the client is new and the
> server old."
> It seems to me that SVN Update is not a 'new feature' and, therefore,
> it should work, right? (Anyway, I will request an update of our
> server.) Regards,
The server version should be irrelevant.
--
Philip
RE: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 25 Oct 2011 18:00:07 +0100
>People are replying to utwente.nl address in your Reply-To header.
Thanks for pointing this out. I don't use this hotmail address a lot and totally forgot the address in the reply-to (which stopped working about 5 years ago...)
>Did you checkout the new working copy to the same location as the oldworking copy?
Yes. I did.
>If so did you move/delete the old working copy first?
Yes. I moved them.
>What state is your working copy before the update that fails?
Perfectly fine.Clean up work nicely, everything up-to-date, nothing wrong.
>Any
modifications?
No.
I also tried a checkout of a(n existing) repository to a different location. I get the same error message when I try to update.
>Can you reproduce the problem with a local test
repository? I tried to reproduce the problem by making a local test repository. However, there's no problem anymore. It works perfectly fine.
Maybe it is like this because our SVN server has not yet been upgraded to 1.7.
Although release notes say:"Older clients and servers interoperate transparently with 1.7
servers and clients. However, some of the new 1.7 features may
not be available unless both client and server are the latest
version. There are also cases where a new feature will work
but will run less efficiently if the client is new and the
server old."
It seems to me that SVN Update is not a 'new feature' and, therefore, it should work, right?
(Anyway, I will request an update of our server.)
Regards,
Wabe.
---------------------------
Subversion Exception!
---------------------------
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_wc\wc_db.c'
line 11039: assertion failed (base_status == svn_wc__db_status_incomplete)
---------------------------
OK
---------------------------
RE: Error when updating
Posted by Wabe W <wa...@hotmail.com>.
First, please bear with my ignorance here. I only just figured out that I don't get a reply to my e-mail in my inbox. I'm apparently supposed to visit this page...
Anyway, thank you for replying. To return to the problem:
>Does the problem occur with an upgraded working copy or with
>a new checkout?
The answer is: with both.
>Can you please try a new checkout if you haven't already?
When it first happened (after upgrading) I tried a new checkout. But only for one of the directories.
Right now I checked out the two directories I'm currently using. And I still get the same error message if I simply click SVN update.
Only if I commit (just anything) first and then update, it works fine - and only for that directory it works.