I'm impacted by this bug as well, as the 32-bit binaries shipped with the Bzr installer run out of memory when migrating my huge SVN repos with 50k files, ~24k revisions, and ~25GB of data.
I tried building bzr from source on 64-bit Python 2.6, but the missing zlib header files tripped me up. In case anyone's interested this is the error I got after doing a 'python setup.py build':
bzrlib/_chk_map_pyx.c(32) : fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory
Cannot build extension "bzrlib._chk_map_pyx".
Use "build_ext --allow-python-fallback" to use slower python implementations instead.
At any rate, I don't think it's realistic to count the build from source option as a viable workaround, at least not as of now.
Incidentally, I had almost the exact same problem trying to migrate this repos to Mercurial. It really sucks as it's preventing me from migrating our team away from SVN
I'm impacted by this bug as well, as the 32-bit binaries shipped with the Bzr installer run out of memory when migrating my huge SVN repos with 50k files, ~24k revisions, and ~25GB of data.
I tried building bzr from source on 64-bit Python 2.6, but the missing zlib header files tripped me up. In case anyone's interested this is the error I got after doing a 'python setup.py build':
bzrlib/ _chk_map_ pyx.c(32) : fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory
Cannot build extension "bzrlib. _chk_map_ pyx". python- fallback" to use slower python implementations instead.
Use "build_ext --allow-
At any rate, I don't think it's realistic to count the build from source option as a viable workaround, at least not as of now.
Incidentally, I had almost the exact same problem trying to migrate this repos to Mercurial. It really sucks as it's preventing me from migrating our team away from SVN