Canonical investigated and told me how to fix the download Short answer: branching over http on Windows fails, but branching over bzr+ssh succeeds. The problem was traced to a file in the repository, which is a little bit more than 900MB when decompressed and Windows memory chokes because of problem with the file.
The easy solution on my side was to login to launchpad so the transfer goes through bzr+ssh instead of http (the anonymous method). This took some time becase I had to use Puttygen and Pageant to create and register public key with launchpad. Thought it was worth putting the BZR help link here in case anyone else runs into the same problem where Windows runs out of memory trying to complete the download of revision 3086. See https://answers.launchpad.net/bzr/+question/175127 for the gory details Below is a summary of the what they say (my and I below are who wrote this) and it includes a suggested fix to the repository: ... my guess is that 'lp:leo-editor' has a bit of junk data in it. Something that compresses entirely too well (like a 900MB file of all 0 bytes). Further, that data might not actually be referenced in the real history, but just be present in a revision that was pushed into the repository, but then that revision was uncommitted/etc. When you access the data via HTTP, the bzr client has to download the whole blob, unpack it locally, and then use whatever content it actually wanted from the blob. In contrast, if you use 'bzr+ssh://' the server side can notice "oh, you only want bytes XX and YY from that blob, I'll unpack it on my side, and then only send you the bytes you are actually going to use". I did a little bit more digging, and I found the record that is specifically problematic: spellpyx.txt-20080228081140-oy1uzrph8dr32kq8-508 which is at bytes from 2361701 to 904890145 in the uncompressed block. This file is referenced in a revision which is no longer in the ancestry of lp:leo-editor. My guess is he committed it by mistake, pushed it to Launchpad, realized his error, uncommitted it, and then started a new branch. However, the data is still there in the repository. The best way to get rid of it is to get someone to branch it into another location (which won't include it) delete that repository, and push the 'clean' branch back into place. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
