By default the Google App Engine SDK doesn’t run on Ubuntu 9.04 (Jaunty Jackelope)… You can fix it!

After a little searching I noticed neither posts about this issue nor a quick fix were top of the Google rankings… hoping to resolve that with this post and get all of us Ubuntu 9.04 (Jaunty) users up on App Engine. UPDATE: This post is now first when searching for “App Engine Ubuntu Jaunty Problem” and even “App Engine Ubuntu Jaunty” in one day, nice!

Once you download the SDK as usual and run one of your apps on a default Ubuntu 9.04 Jaunty install you will see errors galore, you see Ubuntu 9.04 ships Python 2.6 and App Engine is built on Python 2.5 and they are not friendly!

Here is how I got my environment running, I will update the post if I run into further errors.

In a terminal install Python 2.5

They will coexist on the system.

sudo apt-get install python2.5

Edit dev_appserver.py in your google_appengine directory

Change the first line in dev_appserver.py…

#!/usr/bin/env python

….to…

#!/usr/bin/env python2.5

App Engine should now load and run your apps properly!

I believe this is the simplest noninvasive way to let App Engine find what it wants, Python 2.5, and let Ubuntu carry on as it likes with Python 2.6 and beyond. Here is a source on this issue, commenters have many different solutions.

Hope this post helps at least one of you,
-Ben

I’m throwing this post out there that brings together the things I learned as I worked to get the free Windows 7 Public Beta running on Ubuntu 8.10 Intrepid Ibex via VirtualBox. Hoping this post helps those trying to do the same, in all my Google queries on these issues information was sparse… a few hours wasted on my part will hopefully save you time. This is written in a “just the facts” style and not a full “how to” but should get you where you are going avoiding some of the pot holes.

Proof it’s possible!

Tips

Getting the Install Media – Downloading ISOs

Ok, so Microsoft is having trouble serving download demand thus I tried many paths (torrents, 3rd party links, etc.) to download these multi-gigabyte files trying to avoid the rush… Don’t! Getting partial or corrupted files is rampant even from the right source. I found the cleanest path was to download through the TechNet Customer Preview pages, they don’t have near the traffic pointed to them and seemed reliable. Follow all the steps and save your key to a text file on the desktop when you get it. I suggest downloading the 32 bit version for VirtualBox use, although 64 bit is supposed to work in the latest version unless you are going to give it a ton of RAM (4GB plus) I’d just stay with 32 bit.

Second tip here… no matter how much you want to use Linux/FireFox/wget to download, I tried them all… Don’t! Follow their rules, fire up a copy of Internet Explorer however you can to download the ISOs and then copy them over a network or large flash drive back to your Ubuntu machine. The ActiveX (I know, gross…) downloader appears to have less issues corrupting files which just plain saves you time.

Getting VirtualBox Ready

Either…
You already have VirtualBox running on Ubuntu and have run a number of virtual OSs without any issues… Great!… Nope, thats what I thought… Make sure you force an upgrade to the very latest VirtualBox available, doing anything on older version causes blank screens, “Aborting” of the OS and other things that waste your time.
Or…
You are new to VirtualBox, in this instance you are probably better off, go to VirtualBox.org and grab the latest version.

Setup a new VirtualBox “machine” choose Windows Vista as the type and give it at least 1GB of RAM and 20GB of hard drive. In the network area I suggest you choose the “Intel PRO/1000 MT Desktop (82540EM)” adapter rather than the default, Windows 7 seems to like it better from scratch. Connect your downloaded ISO to the CDROM and it should boot from it by default. You won’t even have to ever even burn that DVD, beautiful.

Installation Bumps and Bruises

Install speed, blank screens, file expanding… Installation will be SLOW don’t shut it down and restart when you are impatient, I did that about 5 times, it is working unless the VirtualBox aborts of the installer throws errors.

Can’t find “install.wim” – Your ISO is corrupt, you are going to have to download again unfortunately please make sure you download if from Microsoft directly and via Internet Explorer and the custom downloader. I downloaded two corrupt version before I gave in and followed the rules too, thats 5+ GB of wasted time and downloaded bytes.

Virtual machine crashes and returns to Virtual Box with the status “Aborted” – For me, all these issues were due to running and old version of VirtualBox and corrupted ISOs.

I hope some of those issues I dealt with help you get you copy up an running, now go beat the tar out of it and let Microsoft know if you will be using it in the future or sticking on the Linux side of the fence.
-Ben