OverflowError while commiting large binary file

This a known limitation. bzr handles binary files as text lines and split them by lines.

It's the first I see bzr failing on a too long lie though.

I don't understand how can one handle a binary file per line? As there has not to be a LF i don't think this is a good idea.

Wouldn't it be better if the file is detected as binary to split it into chunks of size X? But I have to admit that I don't know well enough how bazaar handles binary files.

Maybe this will be fixed if Bug #109114 is fixed.

Same here, I was about to open a bug on this. My case was actually when I tried to commit a 270MB tar.gz. I didn't get to the point of an exception but I noticed that mempry consumption when running "top" did not stop growing (I stopped at about 60% of a 1GB total ram)

It's probably not the most common use case but something to consider. I personally use git to backup important documents and wanted to try bzr.

I use bzr, but don't maintain it. You are sending these messages to me
in error.

Best,
Chris
On Jun 22, 2009, at 1:43 AM, Martin Pool wrote:

> *** This bug is a duplicate of bug 109114 ***
> https://bugs.launchpad.net/bugs/109114
>
> ** This bug has been marked a duplicate of bug 109114
> [master] bzr holds whole files in memory; raises MemoryError on
> large files
>
> --
> OverflowError while commiting large binary file
> https://bugs.launchpad.net/bugs/269125
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 109114).
>
> Status in Bazaar Version Control System: Triaged
>
> Bug description:
> During my evaluation of different (D)VCS systems I tried to commit a
> large (549MB) Image (BMP format) into bazaar. But after executing
> "bzr ci" I got an error telling me: OverflowError: line is longer
> than a Python string can hold.
> The Image was an empty 16000x12000 Image created with Gimp and saved
> as BMP.
>
> I installed bzr on Mac OS X Leopard using MacPorts.
>
> I attached the corresponding backtrace.