Re: older versions of the subversion server
That is a very good question. Our subversion server has not been updated in a while and it is still on version 1.4.2. I was looking into updating it to take advantage of the new merge tracking features (among others). Since we are using such an old version, I wanted to replicate our production environment on a test server (thus requiring version 1.4.2) and performing the upgrade there first. Do you think I am being overly cautious? What are the chances for a problem to occur in the upgrade process? Thank you, Alin -Original Message- From: Ryan Schmidt subversion-20...@ryandesign.com To: Tomoiaga, Alin alin.tomoi...@ttu.edu Cc: users@subversion.apache.org users@subversion.apache.org Subject: Re: older versions of the subversion server Date: Wed, 16 Jun 2010 16:13:32 -0500 On Jun 16, 2010, at 11:11, Alin wrote: I am trying to install an older version of subversion (1.4.2) on two Linux systems Ubuntu and Red Hat ( 2.6.31-20-generic Ubuntu and 2.6.18-164.el5 ) and I am having a hard time locating the older version packages for subversion. I tried both the Ubuntu and Red Hat repositories and the subversion website. Can you please tell me if these packages are still available for download? Certainly the source is still available from the Subversion project's web site. Not sure where you'd get older precompiled packages for various OSes. Note that Subversion 1.4.x and earlier are unsupported by now, and when 1.7.0 comes out, support for 1.5.x will be dropped. Why do you need to use such an old version?
Re: older versions of the subversion server
On Jun 17, 2010, at 15:09, Alin wrote: Note that Subversion 1.4.x and earlier are unsupported by now, and when 1.7.0 comes out, support for 1.5.x will be dropped. Why do you need to use such an old version? That is a very good question. Our subversion server has not been updated in a while and it is still on version 1.4.2. I was looking into updating it to take advantage of the new merge tracking features (among others). Since we are using such an old version, I wanted to replicate our production environment on a test server (thus requiring version 1.4.2) and performing the upgrade there first. Ah, ok. Do you think I am being overly cautious? What are the chances for a problem to occur in the upgrade process? It would probably be sufficient to install Subversion 1.6.x on the test server, and copy your repository from the production server to the test server. Then test your upgrade strategy. One good way to copy the repository would be to svnadmin dump on the production server and svnadmin load on the test server. This would automatically upgrade the repository to the latest most efficient format.
RE: older versions of the subversion server
No problem. That was a good tip from Ryan on the start-commit hook. I wish I had know about it, although we did publicize to our users well in advance that they needed to upgrade and they could do it anytime before we did our server upgrade. I really only got one call from a user and he was and Eclipse user. Regards, Tom From: Alin [mailto:alin.tomoi...@ttu.edu] Sent: Thursday, June 17, 2010 4:29 PM To: Ryan Schmidt; Thomas Loy Cc: users@subversion.apache.org Subject: Re: older versions of the subversion server Ryan and Thomas, Thank you very much for your advice. -Original Message- From: Ryan Schmidt subversion-20...@ryandesign.commailto:ryan%20schmidt%20%3csubversion-20...@ryandesign.com%3e To: Thomas Loy thomas@cbeyond.netmailto:thomas%20loy%20%3cthomas@cbeyond.net%3e Cc: Tomoiaga, Alin alin.tomoi...@ttu.edumailto:%22Tomoiaga,%20alin%22%20%3calin.tomoi...@ttu.edu%3e, users@subversion.apache.org users@subversion.apache.orgmailto:%22us...@subversion.apache.org%22%20%3cusers@subversion.apache.org%3e Subject: Re: older versions of the subversion server Date: Thu, 17 Jun 2010 15:24:56 -0500 On Jun 17, 2010, at 15:18, Thomas Loy wrote: On the bright side, we had virtually no issues on our upgrade – the major issue was trying to get all of our users to upgrade their clients. There is at least a way you can automate advising your users to upgrade to Subverison 1.5 or later if they have 1.4.x or earlier: the start-commit hook script. This hook script will be passed a list of client capabilities; if the client capabilities do not include mergeinfo, you know it's older than 1.5. You could at that point abort the commit and print an error message advising the user to upgrade their client. http://svnbook.red-bean.com/en/1.5/svn.ref.reposhooks.start-commit.html I don't know of a way to detect the client version beyond that, though. And unfortunately early versions of 1.5.x weren't totally satisfactory for merge tracking, so you really do want your clients to be the latest version.
Re: older versions of the subversion server
On 6/17/2010 3:09 PM, Alin wrote: That is a very good question. Our subversion server has not been updated in a while and it is still on version 1.4.2. I was looking into updating it to take advantage of the new merge tracking features (among others). Since we are using such an old version, I wanted to replicate our production environment on a test server (thus requiring version 1.4.2) and performing the upgrade there first. 1.4.2 is still in the CentOS 5.x base and installable by yum - and that should mean that RHEL has the same if you are looking for rpms. Do you think I am being overly cautious? What are the chances for a problem to occur in the upgrade process? I wouldn't expect problems - or for you to learn much from a test copy. What you really need is to make sure you can put things back on the real server regardless of anything that happens. That means you'll need snapshots of the repository(ies) made with the server stopped and copies of the programs and any local configuration - just in case... Also, note that when you first use a new client version it will modify any working copies it touches so that older versions can't be used again. Differing versions of clients and servers will interoperate but you don't get all the new features until both are new. -- Les Mikesell lesmikes...@gmail.com
