> -----Original Message-----
> From: Andrew Reedick [mailto:[email protected]]
>
> > > On Apr 28, 2015, at 2:03 PM, Andrew Reedick <[email protected]> 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
>
Looks like the "fsfs" type was introduced in 1.1. However, a 1.1.4 client
fails with
svn: Can't open file 'devel/db/current': The system cannot find the
file specified.
And the 1.0.9 client fails with
svn: Berkeley DB error while opening 'nodes' table for filesystem devel
- Copy/db:
No such file or directory
Looks like I need a bigger hammer.
