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

RE: Dealing with very old repo format (version 1)

From: Andrew Reedick <jreedick_at_incomm.com>
Date: Tue, 28 Apr 2015 21:12:11 +0000

> -----Original Message-----
> From: Joseph Bruni [mailto:jbruni_at_icloud.com]
> Sent: Tuesday, April 28, 2015 5:09 PM
> To: Andrew Reedick
> Cc: users_at_subversion.apache.org
> Subject: Re: Dealing with very old repo format (version 1)
>
> > On Apr 28, 2015, at 2:03 PM, Andrew Reedick <jreedick_at_incomm.com> wrote:
> >
> > Does anyone have any tips on how to upgrade a very old repo? The db/format lists "1". A 1.8 svn client cannot hotcopy, dump or "svnadmin upgrade" such an old repo, all of which fail with "svnadmin: > E720002: Can't open file 'devel\db\current': The system cannot find the file specified."
> >
> > Do I need find a really old svn client (1.3?) and upgrade? Do I need to manually create the db/current file?
> >
> >
> > Supposedly , a format of "1" is from pre-svn 1.0. https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_repos/repos.h -> "Formats 0, 1 and 2 were pre-1.0."
> >
>
> Hi Andrew,
>
> I'm guessing your old format was built using the BerkeleyDB backend since many of the earlist repos defaulted to BDB until FSFS came around. If you build your svn with BDB, does it still complain?
>

Forgot to mention, "db\fs-type" is "fsfs" so BDB isn't (shouldn't) be an issuse.

On the plus side, I found some ancient installers: http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=469&expandFolder=469&folderID=11149
Received on 2015-04-28 23:13:23 CEST

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.