bzr python-based installer requires 32-bit python on windows; unclear message

The installer *is* correct, just its message isn't that helpful - you simply can't mix and match 32 and 64bit binaries. I'm not sure about ctypes, but there will never be a pywin32 64bit Python 2.5 build - only 2.6 and later. It is possible that Python 2.5.4 has ctypes enabled though - that might be worth checking. Alternatively, just install the 32bit version of Python 2.5 - it works just fine on a 64bit OS.

It seems like we should at least give a better message about why.

See also bug 345998, where this problem was also hit, also asking that there should be a python2.6 installer.

Hello, I reported the problem as part of https://bugs.launchpad.net/bzr/+bug/345998 in March.
The logic is quite simple: if one has a x64 Windows, he will naturally install a x64 Python. The fact that there is no python-based Windows bzr installer working in this case, is a problem: it forces people to uninstall their python x64 and install a python x86. Could you please give an update on the present bug?

Hi Guilhem,

OK, if Python x64 can't coexist with Python x86 that does make it more serious, because I can see that people might have other requirements for the 64-bit version.

So this bug would be solved if we also made binary builds against the 64-bit Python?

yes, I think so.

And until this is fixed, you might want to put a warning in http://bazaar-vcs.org/WindowsDownloads , so that users know that they should use a 32-bit Python for the Python-based installers. Otherwise they'll just lose time rediscovering this bug.

I've added a note to the windows download page pointing this out.

Our Windows build & packaging process is still somewhat manual so I think it would slow it down further to make 64-bit python builds of every release, especially if you consider that there are installers for 2.4, 2.5 and 2.6. However, perhaps it would at least be reasonable to make an installer for bzr 2.0.2 against python 2.6?

It would also help if someone who has a 64-bit python2.6 installed could re-test running bzr from source - if they get the same error quoted in the original message there may be some simpler way around it.

Hey guys,

I have an AMD 64 bit Windoze machine and I am seeing this error. It does indeed seem to prevent me from exploring the wonders of Bazaar. I'm willing to run the build from source and post the error if that would help - but I'm a python-newbie so you might have to lay some instructions on me ;-)

Regards,

icey502

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

Apparently python2.6 can now do 32<->64 bit cross-compiles on Windows.

http://docs.python.org/distutils/builtdist.html#cross-compiling-on-windows

I ran into the same problem on Win7, 64-bit.
Maybe a better solution is to ship 64-bit binaries? That would solve the problem.

We're working on making a separate 64-bit Windows build.

Can you give any estimates about when 64-bit installer for Windows will be available?

A 64bit Windows build would be a temporary work around for large files would it not?
I would love to see this sooner if possible. At present, Bazaar seems to need memory for at least 3x copies of the working data, so the largest file a Windows user can commit is somewhere between 650mb -> 1gb.

Any updates on this issue? Especially @mbp?

Would it help to compile Bazaar using IronPython, thus creating a .NET executable? As .NET executables can be compiled to target both x86 and x64 CPUs, this would probably also tackle https://bugs.launchpad.net/bzr/+bug/193685 at least for x64 Windows (out of memory exceptions on Windows machines)

It's a shame that there is still no Windows 64-bit build.

Are there any helpful hints to build with mingw?
I got not very far with mingw64, the ld error messages are no help at all.

Or is it possible to build with LLVM/Clang 3.0?

I am pleased to announce that I have successfully built a 64-bit version of Bazaar for Python 2.7. You can get the Python installer and MSI files here:

http://www.box.com/s/5e7eca3684ad9f61315d

Basically the process for doing this was as follows:

1. Install the Windows 7.1 SDK.
2. Install Microsoft Visual C++ Express 2008 (NOT 2010 - because none of the official Python builds use it).
3. Download the Bazaar source code.
4. Follow the instructions here: http://mattptr.net/2010/07/28/building-python-extensions-in-a-modern-windows-environment/
5. Run 'python setup.py bdist_wininst' to generate the installer.

I was able to install v2.5.1 with Qt interface on python 2.7 (64bit) using a bit longer route with unofficial binary packages. These are available for example from: http://www.lfd.uci.edu/~gohlke/pythonlibs/
My setup as almost according to http://wiki.bazaar.canonical.com/WindowsInstall. This is what I've used:
- pywin32-218.win-amd64-py2.7.‌exe
- curl-7.23.1-win64-ssl-sspi.zip (from http://curl.haxx.se/download)
- pycurl-7.19.0.win-amd64-py2.7.‌exe
- pycrypto-2.6.win-amd64-py2.7.exe (from http://www.voidspace.org.uk/downloads/pycrypto26)
- zlib127-dll.zip (from http://zlib.net)
- paramiko-1.7.7.1.zip (setup from source: http://www.lag.net/paramiko/download)
- PyQt-Py2.7-x64-gpl-4.9.6-1.‌exe (Qt GPL included + tools)
- bzr-2.5.1.win-amd64-py2.7.‌exe
- bzrtools-2.3.0.tar.gz (launchpad)
- qbzr-0.23.0.tar.gz (launchpad, setup from source)

Also I needed to correct c:\Python27\Scripts\bzr.bat to yield something like:
@C:\Python27\python.exe C:\Python27\Scripts\bzr %*

After all these steps 'bzr explorer' should launch.