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

Re: Fwd: Re: Problems after upgrape to svn 0.27

From: <cmpilato_at_collab.net>
Date: 2003-08-18 16:15:01 CEST

mailing.lists@gmx.net writes:

> Hi
>
> >
> > Did you update to 0.27, or to HEAD? I asked, because...
> >
> > > [Mon Aug 18 13:51:33 2003] [error] [client xx.xx.xx.xx] (17)File
> > > exists: Malformed node-revision skeleton [500, #160027], referer:
> > > https://yy.yy.yy.yy/
> >
> > ... after 0.27 was rolled out, we changed the filesystem schema in an
> > incompatible way that would yeild *exactly* this error if you didn't
> > put your repository through an svnadmin dump/load cycle.
> >
>
> i just updated to the HEAD,
>
> so i have to make an svnadmin dump and a load?
> is there any docu about this?

I don't know if we have any generic notes about this. I might have
put something in the book about it.

But it's easy:

1. Backdate your subversion to sometime before the schema changed.
   You could also just grab the 0.27 tarball and build it,
   --disable-shared.

2. Rename the old repos: 'mv repos old-repos'

3. Using the old(er) code, run 'svnadmin dump old-repos > dumpfile'.

4. Using the new code, run 'svnadmin create repos', then 'svnadmin
   load repos < dumpfile'.

5. Move any hook scripts or whatever from the old repos to the new
   one.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 18 16:18:14 2003

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