Package: python-mysqldb Version: 1.1.6-1 Severity: important hello,
i tried to reopen bug #270555, as this bug is not really fixed, it's just hidden thru a workaround. unfortunately, the bug is already archived and no further changes may be made. thus i opened a new one ... everytime when MySQLdb-python is used with libapache(2)-mod-python and built with libmysqlclient12-dev, connect.cursor() segfaults instead of executing whatever it is told to. currently all python2.*-mysqldb packages in debian are built with libmysqlclient10-dev, what circumvents the bug, but in the long term we should use the most recent stable mysql version, and that's currently mysql 4.0.23, not 3.23.56. i submitted this bug to MySQLdb-python upstream author Andy Dustmann, and i'll do some further debugging someday, but currently i'm quite busy with my abitur. andy stated that he'll use MySQLdb-python with libapache-mod-python soon on gentoo, and he'll report his experiences to me. if he has no problems with using it, it must be a mysql debian specific bug. we'll see ... bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
