issues with 1.4.3 to 1.5.1 upgrade?

["Robert P. J. Day" <rp...@crashcourse.ca>]

   i would like, on an RHEL4 system, to upgrade subversion from 1.4 3  
to 1.5.1 to get all the new merging features, and obviously have no  
impact whatsoever on the users.  has anyone done that upgrade, either  
on RHEL or elsewhere?  should there (theoretically) be anything to  
worry about?  i'd really hate to have promised people that it would be  
an improvement, only to have this blow up on everyone and toast the  
repositories, or something equally hideous.  thanks for any feedback.

rday


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: issues with 1.4.3 to 1.5.1 upgrade?

[da...@jpmorgan.com]

Hi,

[warning - convoluted email follows]

We used the "summersoft" 1.4.5 RPMs which provided RHEL4 binaries which 
have been great - unfortunately there haven't been any RHEL4 1.5.x binary 
RPMs made available on "summersoft" yet.

I've been looking at the pre-requisites to getting 1.5.x built for RHEL4 
in order to evaluate what our upgrade path should be. So far I've managed 
to get the RPM to the testing stage of the build. Current status is 
getting a failure on test 22 of the RA_LOCAL layer:

        Running all tests in getopt_tests.py [22/61]...FAILURE 

In order to build Subversion 1.5.x you require the following pre-requisite 
packages (taken from the INSTALL file for RHEL 1.5.1:

        apr-0.9.7 (or greater - must be built with Berkeley DB support 
enabled)
        apr-util-0.9.7 (or greater - must be built with Berkeley DB 
support enabled)
        neon-0.25 (or greater - for webdav access)
        swig-1.3.24 (or greater - required for building the perl, python, 
ruby bindings)

The summersoft RPM distribution provides binary RPMs for RHEL4 of 
apr-0.9.12, apr-util-0.9.12, swig-1.3.25 - however it does *not* provide 
neon as the system copy of neon on RHEL4 (neon-0.24.7-4) was suitable for 
building Subversion 1.4.x.

RHEL5 on the other hand provides neon-0.25.5-5.1 which - if you build it 
from the source RPM for RHEL4 enables you to install and deploy a suitable 
version on RHEL4.

If you then take the summersoft RHEL5 source RPM, modify the versions of 
apr, apr-util, neon, swig to match the actual versions required in the 
INSTALL file then build of the RPM can proceed.

Links:
======
neon-0.25.5-5.1 RHEL5 source RPM:
 
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/neon-0.25.5-5.1.src.rpm

subversion-1.5.1-1 Summersoft source RPM:
 
http://the.earth.li/pub/subversion/summersoft.fay.ar.us/pub/subversion/latest/rhel-5/src/subversion-1.5.1-1.src.rpm

Installing Subversion guide:
        http://svn.collab.net/repos/svn/trunk/INSTALL


HTH,

Dg.
--
David Grierson
JPMorgan - IB Architecture - Source Code Management Consultant
GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson@jpmorgan.com
Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
 



"Robert P. J. Day" <rp...@crashcourse.ca> 
25/08/2008 18:44

To
users@subversion.tigris.org
cc

Subject
issues with 1.4.3 to 1.5.1 upgrade?






   i would like, on an RHEL4 system, to upgrade subversion from 1.4 3 
to 1.5.1 to get all the new merging features, and obviously have no 
impact whatsoever on the users.  has anyone done that upgrade, either 
on RHEL or elsewhere?  should there (theoretically) be anything to 
worry about?  i'd really hate to have promised people that it would be 
an improvement, only to have this blow up on everyone and toast the 
repositories, or something equally hideous.  thanks for any feedback.

rday


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org




Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s).  All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org