On Sun, Jun 23, 2013 at 7:38 PM, Alexey Neyman wrote:
> On Sunday, June 23, 2013 07:20:50 PM Nico Kadel-Garcia wrote:
>
>> On Sun, Jun 23, 2013 at 3:56 PM, Alexey Neyman wrote:
>
>> > Hi,
>
>> >
>
>> >
>
>> >
>
>> > I've tried upgrading the client to SVN 1.8, and now see some strange
>> > merge
>
Hi,
After I upgraded to 1.8.0, svnsync process started to fail. I am using apache
2.2.3. I suspect it's really serf's problem (1.2.1),
but nevertheless I had to revert back to 1.7.10. Is this a known limitation?
Thanks,
Vadym
On 24.06.2013 01:38, Alexey Neyman wrote:
>
> Are you calling RPMs provided by WanDisco's "fun and games"? I think
> Subversion developers employed by WanDisco might be somewhat insulted
> by such judgment.
>
Hmm I'd sooner be insulted by someone anticipating my reaction like
that. :)
Nobody
On Jun 30, 2013, at 07:06, Vadym Chepkov wrote:
> After I upgraded to 1.8.0, svnsync process started to fail. I am using apache
> 2.2.3. I suspect it's really serf's problem (1.2.1), but nevertheless I had
> to revert back to 1.7.10. Is this a known limitation?
You said you upgraded to 1.8.0.
On Jun 30, 2013, at 2:18 PM, Ryan Schmidt wrote:
>
> On Jun 30, 2013, at 07:06, Vadym Chepkov wrote:
>
>> After I upgraded to 1.8.0, svnsync process started to fail. I am using
>> apache 2.2.3. I suspect it's really serf's problem (1.2.1), but nevertheless
>> I had to revert back to 1.7.10. I
On Tue, Jun 25, 2013 at 9:40 AM, Daniel Shahaf wrote:
> On Mon, Jun 24, 2013 at 03:40:44PM -0400, Nico Kadel-Garcia wrote:
>> The normal way to handle changing deployment environments is with an
>> actual configuration or deployment tool, such as autoconf, that sets
>> the path to the locally dete
