You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Justin Kominar <jk...@quarry.com> on 2007/02/06 17:06:59 UTC

SVN 1.1.4 error

Hello,

I don't know if this of any interest to you but I've just discovered the
following error:

If you run 'svn status -u -N' at the command line, you receive the following
error message back from the client:

svn: subversion/libsvn_wc/status.c:917: tweak_statushash: Assertion
`repos_text_status == svn_wc_status_added' failed.
Aborted

Other pertinent details:

svn, version 1.1.4 (r13838)
compiled Apr 12 2005, 16:01:59
Running on Redhat Linux, on a PC platform.

Hopefully this is of some use to you.

-Justin

---------------------------------
Justin Kominar
Interface Developer
Quarry Integrated Communuications
Waterloo, Ontario, Canada
519-743-4300 x2208 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: SVN 1.1.4 error

Posted by Ramanathan Muthaiah <ru...@gmail.com>.
> Hi and thanks for the report.  That version of svn is nearly 2 years
> old, so there won't be another 1.1.x release.  If this problem is
> still reproducible on a more recent version of svn (1.4 or even a
> trunk build), we'd like to hear about it.

I tried the same command, with SVN v1.4.0 and v1.4.3 and did not face
such errors. I have attached the command output for your reference:

As you can see, no problems are reported.

Am running these SVN versions on FC5 system running 2.6.15-1.2054_FC5

=========== SVN 1.4.0 ===============

[ram@thinnai ~]$ /opt/svn-1.4.0/bin/svn status -u -v -N
/home/ram/svnarticle_draft/
               33       32 ram          /home/ram/svnarticle_draft/images
               35       35 ram          /home/ram/svnarticle_draft/svn_article
               33       33 ram          /home/ram/svnarticle_draft
Status against revision:     35

=========== SVN 1.4.3 ===============

[ram@thinnai ~]$ /opt/svn-1.4.3/bin/svn status -u -v -N
/home/ram/svnarticle_draft/
               33       32 ram          /home/ram/svnarticle_draft/images
               35       35 ram          /home/ram/svnarticle_draft/svn_article
               33       33 ram          /home/ram/svnarticle_draft
Status against revision:     35

/Ram

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: SVN 1.1.4 error

Posted by Peter Lundblad <pl...@google.com>.
Justin Kominar writes:
> svn, version 1.1.4 (r13838)
> compiled Apr 12 2005, 16:01:59

Hi and thanks for the report.  That version of svn is nearly 2 years
old, so there won't be another 1.1.x release.  If this problem is
still reproducible on a more recent version of svn (1.4 or even a
trunk build), we'd like to hear about it.

On another note, for us to be able to fix this problem, we would need
more information.  The best is if you can provide us with a
reproduction recipe, a series of commands (from repository creation to
failed command) so we cantry it out.

thanks,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

RE: SVN 1.1.4 error

Posted by Justin Kominar <jk...@quarry.com>.
Thanks folks.

I'm sorry to have bothered you all with an old issue, and I promise I did
try to search the bug repository for this issue before emailing about it,
but I guess wasn't searching for the right terms.

I'll see about upgrading our local copy of svn, and if I'm able to reproduce
it, will write back.  My current understanding however, is that the build of
svn (1.1.4) we're running is the most current one the Redhat Enterprise
Management Services will "allow" us to push out to our servers, so it's more
Redhat that's behind the times than us.  May be a while before we can
actually move to something a little more current :(  I'd really love that
--xml feature to interface with what I'm trying to do here <sigh />.

Cheers,

-Justin

> -----Original Message-----
> From: Malcolm Rowe [mailto:malcolm-svn-dev@farside.org.uk] 
> Sent: Wednesday, February 07, 2007 2:03 PM
> To: Justin Kominar
> Cc: dev@subversion.tigris.org
> Subject: Re: SVN 1.1.4 error
> 
> On Tue, Feb 06, 2007 at 12:06:59PM -0500, Justin Kominar wrote:
> > If you run 'svn status -u -N' at the command line, you receive the 
> > following error message back from the client:
> > 
> > svn: subversion/libsvn_wc/status.c:917: tweak_statushash: Assertion 
> > `repos_text_status == svn_wc_status_added' failed.
> > Aborted
> > 
> > Other pertinent details:
> > 
> > svn, version 1.1.4 (r13838)
> > compiled Apr 12 2005, 16:01:59
> 
> For reference, this is almost certainly issue 2122, a fix for 
> (the crashing part of) which was included in Subversion 1.2.0.
> 
> Regards,
> Malcolm
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: SVN 1.1.4 error

Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Tue, Feb 06, 2007 at 12:06:59PM -0500, Justin Kominar wrote:
> If you run 'svn status -u -N' at the command line, you receive the following
> error message back from the client:
> 
> svn: subversion/libsvn_wc/status.c:917: tweak_statushash: Assertion
> `repos_text_status == svn_wc_status_added' failed.
> Aborted
> 
> Other pertinent details:
> 
> svn, version 1.1.4 (r13838)
> compiled Apr 12 2005, 16:01:59

For reference, this is almost certainly issue 2122, a fix for (the
crashing part of) which was included in Subversion 1.2.0.

Regards,
Malcolm