FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 04-14-2010, 12:38 PM
Les Mikesell
 
Default SVN server update

Matt Keating wrote:
>> Dear all,
>>
>> i have SVN server 1.4.x working on production.
>> i want to go ahead and update to 1.6.x
>>
>> i'm hoping your experience would help me prevent possible downtime..
>> is there any issues that may arise from updating the SVN server from one
>> version to another on a production server?
>
> I upgraded ours ok with no issues * But Iąd like to see what anyone else

Rpmforge has 1.6.x packages that work well, but be careful what else you update
from there to avoid conflicts. If you use viewvc, it has to come from the same
repository and epel may have a higher version number.

You shouldn't have any problem upgrading the server side and it will be
backwards compatible with older clients, but you should be aware that when you
use an upgraded client it will modify the working copy format in place so that
you can't go back to an older client without doing a fresh checkout. That can
be a problem if you use a mix of command line and GUI clients. Also you don't
get all of the new merge tracking features unless you use newer clients as well.

--
Les Mikesell
lesmikesell@gmail.com
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 04-14-2010, 02:24 PM
Paul Heinlein
 
Default SVN server update

On Wed, 14 Apr 2010, Les Mikesell wrote:

> Matt Keating wrote:
>>> Dear all,
>>>
>>> i have SVN server 1.4.x working on production.
>>> i want to go ahead and update to 1.6.x
>
> You shouldn't have any problem upgrading the server side and it will
> be backwards compatible with older clients, but you should be aware
> that when you use an upgraded client it will modify the working copy
> format in place so that you can't go back to an older client without
> doing a fresh checkout. That can be a problem if you use a mix of
> command line and GUI clients. Also you don't get all of the new
> merge tracking features unless you use newer clients as well.

My experience is in line with Les' advice: you'll have a harder time
on the client side than on the server. It's an especially difficult
issue if several different machines share a filesystem containing
repository working directories. (Getting CentOS and Debian to
work and play well with SVN trees in an environment with a central
/home mount is *fun*!)

--
Paul Heinlein <> heinlein@madboa.com <> http://www.madboa.com/
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 10:25 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org