I ran into this issue last night with Ubuntu Dapper. I reviewed the change tickets for Edgy, and confirmed that this patch will not be backported to Dapper, although it will be available in Edgy.
However, it is fairly easy to install the most recent version of setuptools from cheeseshop, and then run the setup shell script included with the source package for MySQLdb on Sourceforge. This will build MySQLdb from scratch and an additional command will install it (see MySQLdb release notes). Not the most elegant solution, but it certainly works well. Note that you will need gcc, libmysqlclient15- dev, and a few other things to make MySQLdb build properly from source. The shell script gives good feedback, so it should be easy to determine what the dependencies are. For Debian users, p2 is the version currently in "testing", which I think is preferable to Sarge at this point in Debian's release cycle anyway. "Testing" is one step up from "Stable" (standard Sarge), and it includes packages that are more stable than "Unstable", but not yet accepted into "Stable". Anyone who has issues with installing MySQLdb from source on Sarge should change to "Testing" (edit /etc/apt/ sources.list, apt-get update && apt-get dist-upgrade). Hope this helps someone. On Mar 19, 11:10 am, "James Crasta" <[EMAIL PROTECTED]> wrote: > On 3/18/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > Of slightly more concern to me, but related, is something Jeff Croft > > pointed out today: the next release will cause problems on Dreamhost, > > since they are using an older MySQLdb setup. Not a big deal right this > > minute -- anybody using svn checkouts in production knows the risks they > > are taking -- but going to be a slightly more visible issue when 0.96 is > > released. > > > One solution there is for existing Dreamhost customers to ask for an > > upgrade of that module (pointing out the reasons). The alternative is to > > install a version of the module locally or test very carefully that the > > bugs that caused the upgrade do not occur for them and then comment out > > the version check (benefit of having the source available, again). > > However, none of these are zero work (although requesting an upgrade by > > Dreamhost might be close to zero work. Would be good if somebody who's a > > customer could try that). > > This doesn't address your the problem directly, but in the case of > Dreamhost, they allow (and condone) you compiling local versions of > PHP and python. I'm currently running a local python 2.5 in my > homedir with my own compiled MySQLdb and etc. Of course, this may be > tricky for other users, and somewhat irritating to set up. (though I > could put a wiki article up if there's not one already) > > I will put in a request ticket anyway to have Dreamhost upgrade their > version of mysql-python, and update if I get any progress on that. > From what I remember however, they usually only upgrade these things > one server at a time, when a customer requests it, and say "request it > for your server" if you want it. If the demand is high enough > though, they might push it out to all servers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
