On Sun, Feb 12, 2012 at 1:39 AM, Ravi Roy <ravi.aroy_at_gmail.com> wrote:
> On Sun, Feb 12, 2012 at 4:18 AM, Nico Kadel-Garcia <nkadel_at_gmail.com> wrote:
>> On Sat, Feb 11, 2012 at 4:10 AM, Ravi Roy <ravi.aroy_at_gmail.com> wrote:
>> > Hello community,
>> > I have compiled subversion 1.6.17 and Apache 2.2.21 from source on
>> > CentOS
>> > 5.6 and serving my repository using Apache httpd server with the
>> > following
>> > details :
>> If you need the latest Subversion features, consider hopping directly
>> to the 1.7.1 or pending 1.7.2 release for RPMforge. My .spec files are
>> at https://github.com/nkadel/subversion-1.7.2-srpm: Enjoy.
> This is a decision which is not easy to take :-) Thanks.
>> Why are you using CentOS 5.x to support such a large update as Apache
>> 2.2.21? Wouldn't you be better off updateing to CentOS or Scientific
>> Linux 6.x and using httpd-2.2.15 ?
> Did not know about this (large update ..etc). I updated to httpd-2.2.15 but
> problems were not resolved.
> But when I downgraded to Subversion 1.6.12 alongwith httpd-2.2.15, problems
> are resolved.
> May be somebody needs to analyze as to why Subversion 1.6.17 have got these
> Thanks everyone for help and support.
I'm glad you're up and running. Want me to dig into my otes and find
the .spec files for building 1.6.17 SRPM for RHEL 5.x? I hadn't
bothered posting it, since 1.7.x was out and seems to be a solid,
working release. I do encourage the update to 1.7.x to be consistent
with TortoiseSVN and CygWin, for Windows access to shared working
copies. It's also why I discourage the use of svn:eol. Nothing quite
like checking it out on Linux, having your text files svn:eol managed,
then editing and checking them in on TortoiseSVN and creating.....
adventures with EOL.
Received on 2012-02-12 16:11:40 CET