One of our developers ran into this same problem during a bzr push:
> user@user-linux:~/curl-7.19.7$ bzr push Using saved push
> location: bzr+ssh://bzr/srv/some/path/to/repo/branch/
> No handlers could be found for logger "bzr"
> bzr: ERROR: Server sent an unexpected error: ('error', 'Somehow we ended up with too much compressed data, 4202 > 4096')
This occurred in the same folder where our bzr-index problem occurs each night. The push did run successfully, but the error message is disconcerting. All files in the folder are text files.
One of our developers ran into this same problem during a bzr push:
> user@user- linux:~ /curl-7. 19.7$ bzr push Using saved push //bzr/srv/ some/path/ to/repo/ branch/
> location: bzr+ssh:
> No handlers could be found for logger "bzr"
> bzr: ERROR: Server sent an unexpected error: ('error', 'Somehow we ended up with too much compressed data, 4202 > 4096')
This occurred in the same folder where our bzr-index problem occurs each night. The push did run successfully, but the error message is disconcerting. All files in the folder are text files.