Comment 9 for bug 1232992

Wow, I can't believe it was a lightweight checkout. It really did take 1.2gigs or so of ram and like 45 minutes or so to download what is basically the same thing in a 45 meg MariaDB release + 20 megs of state for the .bzr directory.

I tried your suggestion, but it failed, because the first bzr branch command also fails with a python "maximum recursion depth exceeded" error message. The back trace is included in the latest .bzr.log file I've attached.
Apparently bzr can't really do anything when its location file is messed up.

So, is the bug fix just an error message for when the location file is messed up? I think an error message would be better than a python exception from an infinite recursion loop.

The other thing I tried was the MariaDB repo that is available for download. It's mentioned on the page https://mariadb.com/kb/en/getting-the-mariadb-source-code/ . You just download and unarchive it. However, it is just a bzr repo with no branches checked out, so you need to do a "bzr branch lp:maria" to get an actual bzr checkout, because most commands don't seem to work when nothing is checked out such as "bzr tags."

When running the bzr branch lp:maria command it seems to connect to lanuch pad, and download some stuff, and then it crashes with a segmentation fault:

dly@betty mariadb2> bzr branch lp:maria/5.5
You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data. See "bzr help launchpad-login".
Segmentation fault -

The "Segmentation fault - " replaces where the network activity status was. A back trace of this error should also be in the attached .bzr.log. So using that repo doesn't work for me either.

I tried reinstalling bzr a few times. Each time I get the "Cannot build extension "bzrlib._annotator_pyx"." error. So, I do the "build_ext --allow-python-fallback" trick to get it to build anyway. I'm starting to doubt my bug is a real bug in bazaar, but instead a bug in my install of bzr, which seems to be messed up. I'm running an older Slackware 13.37 release, which is a few years old, which may have contributed to these issues.

So, could you please download the MariaDB repo as explained on the page https://mariadb.com/kb/en/getting-the-mariadb-source-code/ in the section "Source Tree Tarball." It's really simple just download the file. Remember to make a new directory and cd to it, because unarchiving the archive will create a .bzr directory in the current directory not in a containing directory. Then supposedly running the command "bzr branch lp:maria" will then checkout the latest version. I get a segmentation fault when I do this, but you shouldn't.

Anyway, after doing all that to setup a MariaDB repo just type the command "bzr tags." It will list a whole bunch of tags. Pick one representing a newish MariaDB release. I forget their exact naming--something like: "Maria-5.5" "MariaDB-10.0" or something with a 5.5 or 10.0 version number, which are the latest releases. Then try to checkout that tag using something like "bzr update -r <tagnamehere>" or "bzr switch -r <tagnamehere>". I forget the actual syntax that goes in "<tagnamehere>." I think there is a "tag:" prefix or something.

If this winds up with the "maximum recursion depth exceeded" error I keep getting, then you should be able to reproduce this problem, and my bug is real. If not, then this bug is mostly likely with my install of bzr, and can probably be safely ignored.

Thanks,
Dave.