Nico, that will be great. I've also posted on stack overflow.
If you use it and want some rep, you can post there, also. If you don't use it, I can post your answer there and reference you. Ton PS: I've read updating RPM can cause some nasty issues because it updates everything to bleeding edge. Can you confirm or deny this? ________________________________ From: Nico Kadel-Garcia <nka...@gmail.com> To: Ton Robin Duong <rhdu...@uh.edu> Cc: "users@subversion.apache.org" <users@subversion.apache.org> Sent: Tuesday, December 20, 2011 8:15 AM Subject: Re: Upgrade SVN 1.6 to 1.7 on CentOS 5.5 with cPanel On Tue, Dec 20, 2011 at 2:38 AM, Ton Robin Duong <rhdu...@uh.edu> wrote: > I tried to upgrade by running a make install again with the new 1.7.2 tar. > This should in theory replace the binaries right? > I took that to mean: > > download new version (1.7.2) > configure > make > make install > > Before the above process ran: svn --version --quiet prints 1.6.17 > After the above process ran: svn --version --quiet prints 1.6.17 (should > show 1.7.2) > What am I doing wrong here? > > PS: SVN was installed initially using modified (skipped the rpmforge stuff) > process described here: > http://sven.webiny.com/subversion-on-cpanel-3-with-centos-55-and-easyapache-32/ > SVN is working right now, no problem, I just want to upgrade it. I've previously published some patches to get the "build an RPM" tools to work right for RHEL-5 and RHEL-6. I've updated them for the 1.7.2 release. Shall I repost them? For reference, I was involved in the last couple of RPMforge updates of this package. (Contributed updated .spec files.)
