Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: local policy)
From: "Cooke, Mark" <mark.cooke@siemens.com>
To: "users@subversion.apache.org" <users@subversion.apache.org>
CC: Arivarasan Manivasagam <wings.arivarasan@gmail.com>
Date: Mon, 15 Oct 2012 11:39:51 +0100
Subject: RE: Subversion server upgrade from 1.4 to 1.7
Thread-Topic: Subversion server upgrade from 1.4 to 1.7
Thread-Index: Ac2qvVrX+mlE9NxbTCygUqh0nBuDQAAAqS7Q
Message-ID: 
 <4F7A7621A511B945915EB16D655311D8127C8B7671@GBOXFW99E01MSX.ww005.siemens.net>
References: 
 <CAOMRTm3nhdEv4UxDZ9GB2f4dk_rRawn=bFUmCk4k+uf72NFFRA@mail.gmail.com>
	<4F7A7621A511B945915EB16D655311D8127C8B763C@GBOXFW99E01MSX.ww005.siemens.net>
 <CAOMRTm1iHHT=Bwktt3BEQY2LyL3DVW9W-4_TEsD-kEUB+4DAgw@mail.gmail.com>
In-Reply-To: 
 <CAOMRTm1iHHT=Bwktt3BEQY2LyL3DVW9W-4_TEsD-kEUB+4DAgw@mail.gmail.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> On Mon, Oct 15, 2012 at 3:19 PM, Cooke, Mark=20
> <mark.cooke@siemens.com> wrote:
>=20
> > -----Original Message-----
> > From: Arivarasan Manivasagam
> > To: users@subversion.apache.org
> > Subject: Subversion server upgrade from 1.4 to 1.7
> >
>=20
> > Hi,
> > We want to upgrade subversion server from 1.4 to 1.7
> > Is this feasible?
> > Can you share any steps or documents related to the same?
> >
> > thanks,
> > Arivarasan Manivasagam
> =09
> =09
> It is feasible and there are plenty of hits using=20
> google with very similar questions.  It would be useful if=20
> you could say what your platform is (or will be if you plan=20
> on upgrading the hardware also).
> =09
> I suggest you start with the release notes for the 1.5,=20
> 1.6 and 1.7 [1] versions which should cover most of the=20
> gotchas but in theory a current server should be able to just=20
> pick up the old repositories and serve them.  However, I=20
> would guess that a 1.4 to 1.7 upgrade would benefit from a=20
> dump / load cycle to make use of the latest repository=20
> structure features (as well as giving you a handy dump file=20
> backup of the pre-upgrade repositories).
> =09
> Perhaps you can provide more info and ask some more=20
> specific questions?
> =09
> 	~ Mark C
> =09
> 	[1] http://subversion.apache.org/docs/release-notes/1.7.html
> =09
> -----Original Message-----
> From: Arivarasan Manivasagam [mailto:wings.arivarasan@gmail.com]=20
> Sent: 15 October 2012 11:11
> To: Cooke, Mark
> Cc: users@subversion.apache.org
> Subject: Re: Subversion server upgrade from 1.4 to 1.7
>=20
> Thanks for the reply.
>=20
> Currently we run this version (svn, version 1.4.6 (r28521))=20
> on a AIX machine. I am looking at upgrading to=20
> v1.7.6-1(http://www.perzl.org/aix/index.php?n=3DMain.Subversion)

Hmm, I'm sure I've seen some messages recently about AIX ~ have you searche=
d the list archive (see http://subversion.apache.org/mailing-lists.html for=
 search links)?

> Is it enough if I do the following=20
> (http://subversion.apache.org/faq.html#dumpload)? Or do I=20
> need to do anything more?

Did you have a look at the Subversion Book contents linked from that FAQ?  =
Useful reading.

> 1. Shut down svnserve, Apache, and anything else that=20
>    might be accessing the repository.
> 2. svnadmin dump /path/to/repository > dumpfile.txt ,=20
>    using version X of svnadmin.
> 3. mv /path/to/repository /path/to/saved-old-repository
> 4. Now upgrade to Subversion Y (i.e., build and install Y,=20
>    replacing X).
> 5. svnadmin create /path/to/repository, using version Y of=20
>    svnadmin.
> 6. svnadmin load /path/to/repository < dumpfile.txt ,=20
>    again using version Y of svnadmin.
> 7. Copy over hook scripts, etc, from the old repository to=20
>    the new one.
> 8. Restart svnserve, Apache, etc.

That should be good for you, I've done similar on Windoze.

> Can you also elaborate step 7 on hook scripts and etc.,?

Subversion supports "hook scripts" that are called by subversion before/aft=
er specific actions [2].  They are in the repositories `hooks` folder (alon=
g with a load of templates with the `.tmpl` extension).  If you have any ho=
oks active, e.g. for emailing people after a commit, then you need to trans=
fer these to the new repository yourself, there is no automatic support for=
 this.  Make sure that you set the required permissions on these files for =
whichever user account runs the subversion server process!

> Thanks again for the support!

[2] http://svnbook.red-bean.com/en/1.7/svn.reposadmin.create.html#svn.repos=
admin.create.hooks

Hope that helps.  Do read the release notes for each version upgrade before=
 you do anything and don't do it on a live system without testing offline!

~ mark c