running svnadmin hotcopy does not touch the source repository? what difference and advantage bet. linear and sharded?
Thanks, West On Fri, Jul 2, 2010 at 8:12 PM, Nico Kadel-Garcia <nka...@gmail.com> wrote: > On Fri, Jul 2, 2010 at 3:18 AM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: >> Nico Kadel-Garcia wrote on Thu, 1 Jul 2010 at 23:11 -0400: >>> On Thu, Jul 1, 2010 at 10:04 PM, west alto <westa...@gmail.com> wrote: >>> > Thanks guys, Ho do i upgrade from 1.3 to 1.6? Do i need to install >>> > first 1.4 then do a svn dump and load, then 1.5 and then svn dump and >>> > load .... etc. >>> >>> No, move aside the repository, do a good backup to tape, then install >>> version 1.6. Then do an "svnadmin hotcopy" with version 1.6, which >>> should build you a nice clean upgraded >> >> I have tested it and I think you are mistaken here: running 'svnadmin1.7 >> hotcopy' on a 1.4-format FSFS repository produces another 1.4-format >> FSFS repository. > > Oh. I see that you're right, and I'd left out the "svnadmin upgrade > the-new-repo" step. > > >> >> [[[ >> % rm -rf t >> % /usr/bin/svnadmin create t --pre-1.5-compatible >> % cat t/**/format >> 2 >> 5 >> % svntrunk >> % svnadmin hotcopy t t2 >> % cat t2/**/format >> 2 >> 5 >> % svnadmin --version >> svnadmin, version 1.7.0 (dev build)? >> compiled Jul 1 2010, 12:12:57 >> ]]] >> >> I suggest a dump|load instead. > > Dumpload is, historically, rather fragile and doesn't bring over your > configuration files. This is particularly critical if you have > modified hook scripts and configuration files. Resolving those can be > an adventure. >