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

bug report: svn requires upgrade, complains of corruption and won't tell me current status

From: Diggory Hardy <lists_at_dhardy.name>
Date: Fri, 15 Feb 2013 12:21:16 +0100

Dear list,

I have an old checkout of an svn repo. This results in:

L10036 mmBackend$ svn info
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: Working copy '/home/dhardy/code/all/mmBackend' is too old
(format 10, created by Subversion 1.6)
L10036 mmBackend$ svn st
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: Working copy '/home/dhardy/code/all/mmBackend' is too old
(format 10, created by Subversion 1.6)
L10036 mmBackend$ svn upgrade
svn: E155016: This working copy is corrupt and cannot be upgraded. Please
check out a new working copy.
svn: E155016: Bad base MD5 checksum for
'/home/dhardy/code/all/mmBackend/COPYING'; expected:
'46aaf69a91703493b666f212a04f2d8d'; found '94d55d512a9ba36caa9b7df079bae19f';

(As to why the checkout is corrupt, I have no idea. The files on my local disk
are unlikely to have been corrupted.)

Problem 1: what was the repo URL? Examining the files in .svn manually solves
this.

Problem 2: what was the status of the repo (did I have uncommitted changes or
other local files)? I see no easy way of checking this. I'll try installing an
old version of svn, but I don't find this a satisfactory solution, hence this
bug report.

Ideally 'svn info' and 'svn st' should work on old checkouts without requiring
any changes (upgrades or other) to them.

Best regards,

Diggory
Received on 2013-02-15 12:34:08 CET

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

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