[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: question on summary stats after svn update

From: Edmund Wong <edmund_at_belfordhk.com>
Date: Wed, 30 Sep 2009 09:12:25 +0800

Paul Burba wrote:
> Hi Edmund,
> You'd get this message if d:\svn\svn is not actually a working copy,
> which seems appropriate to me, but this is also the result when
> updating a working copy format which is too old (which I'm guessing is
> what is happening to you). This is confusing at best:

Actually, I'm not sure if it's either since I've updated this
wc before.

D:\extprogs\svn>svn --version -q

D:\extprogs\svn>svn status
svn: warning: '.' is not a working copy

D:\extprogs\svn>svn update
Skipped '.'
Summary of conflicts:
   Skipped paths: 1

D:\extprogs\svn>svn upgrade
..\..\..\subversion\svn\upgrade-cmd.c:70: (apr_err=200032)
..\..\..\subversion\libsvn_client\cleanup.c:68: (apr_err=200032)
..\..\..\subversion\libsvn_wc\upgrade.c:504: (apr_err=200032)
..\..\..\subversion\libsvn_wc\upgrade.c:297: (apr_err=200032)
..\..\..\subversion\libsvn_subr\sqlite.c:850: (apr_err=200032)
..\..\..\subversion\libsvn_subr\sqlite.c:616: (apr_err=200032)
svn: Schema format 13 not recognized

Isn't format 13 the latest in the trunk or is it 14?


Received on 2009-09-30 03:19:53 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.