Maybe I should download and get a better zlib package.  Let me try and keep
everyone posted.

On Wed, Dec 21, 2011 at 9:14 AM, Phil <cwst...@gmail.com> wrote:

> I have about 155 packages in the repository that I want to checkout.  This
> has never worked with v1.6.  The workaround is to checkout each package one
> at a time (svn co svn://).  As you can see, that's very tedious.  I assume
> subversion doesn't care how many packages are in my repository.  I did the
> basic installation of svn v1.6 (tar'ing subversion-1.6.17.tar and
> subversion-deps-1.6.17.tar).  Then I did another installation but with v1.7
> to see if I ran into the same issue.  I installed it on a different
> directory location.  I was able to checkout the 155 packages successfully.
>
>
> On Wed, Dec 21, 2011 at 8:05 AM, Stefan Sperling <s...@elego.de> wrote:
>
>> On Wed, Dec 21, 2011 at 07:47:16AM -0500, Phil wrote:
>> > Setting LC_ALL=C does not work either.  Wonder why it works for v1.7 but
>> > not for v1.6.  Again, I'm getting "svn: Compression of svndiff data
>> failed"
>> > when executing "svn co svn://path/to/repo/prj working_directory".  But
>> if I
>> > do a "svn co file:///...." then it's okay for v1.6.
>>
>> The error is coming from zlib when compressing data.
>> Maybe svnserve is failing to compress data for transmission to the
>> client via the svn:// protocol.
>>
>> If you use file:// the only possible interaction with zlib during a
>> checkout is decompressing data. Though it might not even be trying to
>> decompress anything at all depending on the content of the respitory
>> you are checking out from.
>>
>> I would suspect that your Subversion 1.6 install has a problem with the
>> zlib it is using.
>>
>> Has checkout ever worked with 1.6 and suddenly stopped working?
>> Was zlib updated or recompiled without also recompiling its dependencies?
>> Or are you trying to get a fresh Subversion install working?
>>
>> That's all I can tell you given the information you provided.
>> Not sure what the problem really is, though.
>>
>
>

Reply via email to