Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So the answer seems to be to install over the existing version.
I took that to mean:
Before the above process was run: svn –version –quiet prints 1.6.17
After the above process was run: 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 process described here. SVN is working right now, no problem, I just want to upgrade it.
well.. I’m not sure why, but running svn –version –quiet indicates that I’m running 1.7.2 now.
I haven’t restarted but I AM running a VPS, so maybe the guys at my host did something (not sure why they would, since I didn’t ask them for any help).
If anyone else is having the same issues, and you are running CentOS and cPanel, please just follow the steps in the link provided in the OP, without doing the RPMForge stuff. Its a little out of date, and kind of obscure, but persistence and a lot googling on linux commands will get you there.