[ Please use reply all to keep the list in the loop -- I'm sending
this to users@ rather than dev@, because other users might also be
interested and/or can chime in if someone has similar issues.
Also, this list prefers bottom-posting or inline replying, so I've
rearranged to put your reply at the
On Tue, Sep 10, 2013 at 3:59 PM, Curt Sellmer wrote:
> On Tue, Sep 10, 2013 at 1:42 PM, Johan Corveleyn wrote:
>> [ Please use reply all to keep the list in the loop -- I'm sending
>> this to users@ rather than dev@, because other users might also be
>> interested and/or can chime in if someone h
On Tue, Sep 10, 2013 at 1:42 PM, Johan Corveleyn wrote:
> [ Please use reply all to keep the list in the loop -- I'm sending
> this to users@ rather than dev@, because other users might also be
> interested and/or can chime in if someone has similar issues.
> Also, this list prefers bottom-posting
On 9/10/13 2:31 PM, Curt Sellmer wrote:
> After giving it more time I can now reproduce the problem with both
> version 1.8.0 and 1.8.3 of the client. And I have now seen the
> problem with both the older and newer versions of the repository.
> Very hard to debug as it does not seem to follow any
On Tue, Sep 10, 2013 at 8:39 PM, Ben Reser wrote:
> On 9/10/13 2:31 PM, Curt Sellmer wrote:
>> After giving it more time I can now reproduce the problem with both
>> version 1.8.0 and 1.8.3 of the client. And I have now seen the
>> problem with both the older and newer versions of the repository.
I now have svn 1.8.3 with serf 1.3.1. I am not seeing the "svn:
E120104: ra_serf: An error occurred during decompression" error as
often at the moment. Have seen it a few times.
But I do intermittently get several different errors as show below.
- Note that I am running the command over and
On 9/10/13 10:41 PM, Curt Sellmer wrote:
> I now have svn 1.8.3 with serf 1.3.1. I am not seeing the "svn:
> E120104: ra_serf: An error occurred during decompression" error as
> often at the moment. Have seen it a few times.
>
> But I do intermittently get several different errors as show below
That thought had crossed my mind, but so far none of the other users
who are still using 1.7 clients have had any issues and also running
the 1.8.1 client on the server box using the file:// scheme has never
produced an error.
On Wed, Sep 11, 2013 at 2:32 AM, Ben Reser wrote:
> On 9/10/13 10:41 P
On Wed, Sep 11, 2013 at 11:02 AM, Curt Sellmer wrote:
> On Wed, Sep 11, 2013 at 8:11 AM, Curt Sellmer wrote:
>> That thought had crossed my mind, but so far none of the other users
>> who are still using 1.7 clients have had any issues and also running
>> the 1.8.1 client on the server box using
On Wed, Sep 11, 2013 at 8:11 AM, Curt Sellmer wrote:
> That thought had crossed my mind, but so far none of the other users
> who are still using 1.7 clients have had any issues and also running
> the 1.8.1 client on the server box using the file:// scheme has never
> produced an error.
>
> On Wed
On Wed, Sep 11, 2013 at 6:26 PM, Curt Sellmer wrote:
> On Wed, Sep 11, 2013 at 11:02 AM, Curt Sellmer wrote:
>> On Wed, Sep 11, 2013 at 8:11 AM, Curt Sellmer wrote:
>>> That thought had crossed my mind, but so far none of the other users
>>> who are still using 1.7 clients have had any issues an
On Wed, Sep 11, 2013 at 12:17 PM, Lieven Govaerts
wrote:
> On Wed, Sep 11, 2013 at 6:26 PM, Curt Sellmer wrote:
>> On Wed, Sep 11, 2013 at 11:02 AM, Curt Sellmer wrote:
>>> On Wed, Sep 11, 2013 at 8:11 AM, Curt Sellmer wrote:
That thought had crossed my mind, but so far none of the other u
On Wed, Sep 11, 2013 at 2:46 PM, Ben Reser wrote:
> On 9/11/13 12:24 PM, Curt Sellmer wrote:
>> Here is a tail of the error.log. This is from when I was running the
>> tests earlier.
>> I was hoping to pinpoint which set of log messages corresponded to
>> each error, but of
>> course I cannot get
On 9/11/13 12:24 PM, Curt Sellmer wrote:
> Here is a tail of the error.log. This is from when I was running the
> tests earlier.
> I was hoping to pinpoint which set of log messages corresponded to
> each error, but of
> course I cannot get it to fail at all right now. I'll keep trying
> througho
On Wed, Sep 11, 2013 at 3:04 PM, Curt Sellmer wrote:
> On Wed, Sep 11, 2013 at 2:46 PM, Ben Reser wrote:
>> On 9/11/13 12:24 PM, Curt Sellmer wrote:
>>> Here is a tail of the error.log. This is from when I was running the
>>> tests earlier.
>>> I was hoping to pinpoint which set of log messages
Curt Sellmer writes:
> On Wed, Sep 11, 2013 at 2:46 PM, Ben Reser wrote:
>> On 9/11/13 12:24 PM, Curt Sellmer wrote:
>>> Here is a tail of the error.log. This is from when I was running the
>>> tests earlier.
>>> I was hoping to pinpoint which set of log messages corresponded to
>>> each error,
On Wed, Sep 11, 2013 at 6:51 PM, Philip Martin
wrote:
> Curt Sellmer writes:
>
>> On Wed, Sep 11, 2013 at 2:46 PM, Ben Reser wrote:
>>> On 9/11/13 12:24 PM, Curt Sellmer wrote:
Here is a tail of the error.log. This is from when I was running the
tests earlier.
I was hoping to pin
On Wed, Sep 11, 2013 at 7:04 PM, Curt Sellmer wrote:
> On Wed, Sep 11, 2013 at 6:51 PM, Philip Martin
> wrote:
>> Curt Sellmer writes:
>>
>>> On Wed, Sep 11, 2013 at 2:46 PM, Ben Reser wrote:
On 9/11/13 12:24 PM, Curt Sellmer wrote:
> Here is a tail of the error.log. This is from when
On Wed, Sep 11, 2013 at 7:19 PM, Curt Sellmer wrote:
>>>
>>> You said you dumped and loaded your repository. You also have
>>> corruption shown by apache that is not shown by svnadmin. When you
>>> dump/load are you also putting the new repository in the same place as
>>> the old repository? If
19 matches
Mail list logo
