On Wed, Jun 20, 2012 at 1:39 PM, Philip Martin
wrote:
> When you disabled v2 you probably restarted apache. Perhaps the
> original error was caused by mod_perl reloading the Perl and then
> getting redefinitions of the symbols present from the previous load.
> Restarting apache would make this go
Doug Hunley wrote on Wed, Jun 20, 2012 at 13:03:32 -0400:
> On Mon, Jun 18, 2012 at 4:48 PM, Daniel Shahaf
> wrote:
> > Doug Hunley wrote on Mon, Jun 18, 2012 at 10:55:02 -0400:
> >> Hey everyone,
> >> We're currently running Apache 2.2.x on an OS X server with SVN 1.6.x
> >> and have a mod_perl
Doug Hunley writes:
> On Mon, Jun 18, 2012 at 4:48 PM, Daniel Shahaf
> wrote:
>> Doug Hunley wrote on Mon, Jun 18, 2012 at 10:55:02 -0400:
>>> Hey everyone,
>>> We're currently running Apache 2.2.x on an OS X server with SVN 1.6.x
>>> and have a mod_perl based authentication handler for SVN rep
On Mon, Jun 18, 2012 at 4:48 PM, Daniel Shahaf wrote:
> Doug Hunley wrote on Mon, Jun 18, 2012 at 10:55:02 -0400:
>> Hey everyone,
>> We're currently running Apache 2.2.x on an OS X server with SVN 1.6.x
>> and have a mod_perl based authentication handler for SVN repo access.
>> It works fine and
Doug Hunley wrote on Mon, Jun 18, 2012 at 10:55:02 -0400:
> Hey everyone,
> We're currently running Apache 2.2.x on an OS X server with SVN 1.6.x
> and have a mod_perl based authentication handler for SVN repo access.
> It works fine and has for many months. When we upgrade to 1.7.x, our
> commits
