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

Re: Upgrade 1.5.4 to 1.7.5

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Fri, 3 Aug 2012 06:05:53 -0400

On Fri, Aug 3, 2012 at 4:16 AM, <Robin.Gueldenpfennig_at_enercon.de> wrote:
>
> Hi Subversion fellows,
>
> we plan to upgrade our Subversion Server from version 1.5.4 to 1.7.5
>
> Subversion runs in a context of a HTTPD version 2.2.3 with FSFS repository
> structure.
>
> It has been build manually by compiling the source code.
>
> Server environment is a SLES system.

Robin, if you're on SLES 11 or later, I urge you to go to
http://www.wandisco.com/subversion/download and grab their 1.7.5
RPM's. Just save yourself time building it, and get a working toolkit.

If you have the skills to build it well manually, you have the skills
to build RPM's. I'm going to assume you've done so, and if not, you're
welcome to my SRPM components for Red Hat based systems at
https://github.com/nkadel/subversion-1.7.5-srpm. They'd need tuning
for SLES: the latest version I see published for OpenSuSE directly is
1.6.17. If you need to rebuild 1.7.5 from that SRPM, it should be
pretty easy, especially if you hit my .spec file for 1.7.5
differences. (My published 1.6.18 and 1.7.5 .spec files have been
synchronized to avoid irrelevant discrepancies.)

> My humble questions are the following:
>
> Do I just need to compile the new source and overwrite the existing binary
> files?
> Are there any new dependencies or upgrades?

Yeah, especially if you want features like the kwallet tools. The psvn
add-on tool also has new Emacs version dependencies, and it's unclear
which SLES release you are using, so it's unclear if you'll have the
Python dependencies to cmpile it.

> It's long ago since I installed Subversion and I'm not an advanced Linux
> administrator in case of installing software by hand from source code.

Then avoid it. Use the RPM's or build from the SRPM's to get a new
version: that helps tremendously with resolving dependencies. Many
tools, such as subversion, only enable certain features if you have
the local libraries at configuration and build time, and working with
the SRPM's helps assure that you have them available.

>
> So I thank you in advance for your anwers and hints.
>
>
> Best regards
> Robin Güldenpfennig
>

Not a problem. I'm getting very fond of the bundled toolkits from
Wandisco: the site management toolkits are very useful.
Received on 2012-08-03 12:06:30 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.