Error -3 while decompressing data

[Martin Pool]

I think you should go ahead and report it on Launchpad, so we have a record.

It is pretty puzzling.  Normally this error means corruption outside
of bzr, but the fact that the pack file matches the expected sha means
it is not filesystem corruption of the kind we normally see.  It's
possible this is a memory error or a filesystem bug, but then it's
surprising that it would consistently occur at the same point.  As a
cheap way to check that, you could run memcheck86 on the server.

It's possible it's actually a problem introduced on the network.
(I've seen marginal Ethernet cables or switches introduce errors at a
rate of one per several MB, so that in normal use they seem to work
but bulk transfers will be corrupt.)  If that's so, then running
bzr+ssh will probably make ssh detect the problem.  You can also check
the 'ifconfig' error counters (not always reliable) and try copying a
large file across ssh.

I'm not clear from your original mail whether you can recreate the
problem by running the commit just simply in a bzr directory on the
server machine, or if bzr serve needs to be involved.

What happens if you run the commit commands against a local repository
on the server?

Hope that helps,
-- 
Martin