subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kai Krueger <kakrue...@gmail.com>
Subject Re: An error occurred during decompression
Date Mon, 06 Jul 2015 18:43:03 GMT
Hi,

Yes, that warning section does indeed cover the issue. Thank you for
pointing that out!

I have just yesterday updated another of our servers from Ubuntu 12.04
to 14.04 with an existing svn repository and the same apache config and
have hit the issue there as well. (Apache config has been carried
forward over many update cycles, so might well contain obsolete or
broken directives)

This time, I did however get the checksum error on checkout.

The other repository where I first reported it, was a fresh repository
(created on 14.04 but with the same old apache config) and thus didn't
contain any .gz files yet. Given I couldn't commit any .gz files, I
never saw the checkout issue.

The commit was from a working copy on the same server, so no network or
proxy should be involved  (but using https://[externalIP]/ as the url).
The svn client was 1.8.8 with ra_serf 1.3.3

Thanks,

Kai

On 7/6/15 8:22 AM, Philip Martin wrote:
> Kai Krueger <kakrueger@gmail.com> writes:
>
>> With your help, I have managed to figure out what the issue was.
>>
>> I had a " AddEncoding x-gzip gz tgz" in my apache config. Once I removed
>> that it now appears to work correctly again.
>>
>> The  --config-option servers:global:http-compression=no  option also worked.
>>
>> Enabling or disabling mod_deflate did on the other hand not appear to
>> make any difference (or my enabling/disabling did not take effect).
>>
>> The apache version is 2.4.7
> Interesting, it looks like the problem already documented in the second
> warning section here:
>
> https://subversion.apache.org/docs/release-notes/1.8.html#mod_dav_svn-fsmap
>
> but I think this is the first time it has been reported as occuring
> during a commit.
>
> I can't reproduce it and it's not immediately clear to me how a server
> setting like that could affect commit.  Were you committing from a
> working copy?  Did you see checkout problems as well?  Which client were
> you using?  Does your server setup have some sort of proxy?
>



Mime
View raw message