X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=1.5 required=5.0 tests=AWL,BAYES_00,BOTNET
X-Spam-Check-By:	sourceware.org
Message-id:	<4AAE5ED0.1000402@acm.org>
Date:	Mon, 14 Sep 2009 08:18:40 -0700
From:	David Rothenberger <daveroth AT acm DOT org>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: subversion hangs on svn up using 1.6.4 & 1.6.5
References:	<3ae83b000909131346s6e6184c9r98732d1fc765f2af AT mail DOT gmail DOT com>
In-reply-to:	<3ae83b000909131346s6e6184c9r98732d1fc765f2af@mail.gmail.com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 9/13/2009 1:46 PM, John Bito wrote:
> I'm not sure how to diagnose this problem, as svn up produces no
> output and svn admin recover says:
> 
> svnadmin: Expected repository format '3' or '5'; found format '10'
> 
> I imagine that the format 10 indicates that the repository is corrupt.
>  Do you have any suggestions for repairing it?

"svnadmin recover" is for recovering a repository, not a working copy. 
Which are you trying to do?

> There's some possibility that subclipse was what created this working
> copy, though I was pretty sure I used Cygwin SVN to update it most
> recently.  I tried svn up with Cygwin SVN 1.6.4 and then upgraded to
> Cygwin SVN 1.6.5, both hang with no output.  Then I tried svnadmin
> recover .svn which gives the message above.

What does "svn st" say?

I use "svn up" against an http repository all the time. Also, both 
releases of SVN passed the test suite, which runs against a local FSFS 
and BDB repository, as well as svn:// and http:// repositories.

> If there's not a clear path to repairing my working copy, do you know
> of any guidance for moving work from a broken working copy to a new
> checkout so that svn up will merge changes/flag conflicts?

I usually fix this by replacing all the .svn directories in my working 
copy. I use commands like the following. Note, this is from memory, so 
check them yourself before running.

% cd /my/working/copy
% find . -name .svn -prune -print0 | xargs -0 rm -fr
% cd /tmp
% svn co http://my/repository/path svn-tmp
% cd svn-tmp
% find . -name .svn -prune -print0 | \
   rsync -avri --files-from=- --from0 ./ /my/working/copy
% cd /my/working/copy
% rm -fr /tmp/svn-tmp
% svn status

-- 
David Rothenberger  ----  daveroth AT acm DOT org

I'll burn my books.
                 -- Christopher Marlowe

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -