Summary - here's my log of working out how simple fixing the leo bzr window problem seems to be, will address next steps in new thread:
Log: Test 1GB Windows XP-32bit system (VirtualBox emulation) Install Python 2.7.2 Install Bzr 2.5 beta 2 "Start bzr in command shell" from Start menu bzr branch lp:leo-editor Hit out of memory when the estimated progress was at 68054 / 74386. Restart the virtual machine with 4GB ram (host system, Ubuntu 11.10 64-bit, has 6GB) rmdir /s leo-editor bzr branch lp:leo-editor Ran out at 68061 / 74407 So I start fiddling with the fast-export thing. Tags leo-4-6-[123]-final seemed to get lost. Apart from that, I don't think we loose anything except compatibility with existing branches / checkouts. On a larger project that might be a big deal, for Leo I don't know if it's that big a deal, we'd have to set a deadline to merge all outstanding changes, that's all. However, I'm not sure how to test the rebuilt vs. original repo. Using HTTP to access both the old and the new work for me in 1GB WinXP using my local copies. Which suggests that the bad reference which we're blaming exists only in the LP copy. I.e. fast-export isn't really needed fix it, any new branch is ok. Which further suggests that a new push of the existing repo to LP might be fine... with that in mind I've branched Leo-trunk to lp:~terry-n-brown/+junk/leo_test ... now branching back to the 1GB WinXP machine (at least download is a lot faster than upload...) bingo - seems fixed, and commit IDs are the same, so should work fine with other existing branches -- 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.
