Comment 10 for bug 1027075

SRU Bug Template

[Impact]

 * A change in MySQL confused the python-mysqldb (version 1.2.3) build process into omitting SSL support. Andy Dustman, the upstream author, dealt with this by adding this patch. It simply checks for the new MySQL versions and automatically sets the proper C macro variable to enable SSL support in the Python module.

 * MySQL supports SSL encrypted connections which is very handy for remote clients connecting over the Internet. This was originally working in the stable release, but was inadvertently lost in the Python module due to the change in MySQL.

 * The patch simply enables the interface module to create and use the additional variables required to support SSL connections.

[Test Case]

 * detailed instructions how to reproduce the bug:
I am omitting the detailed instructions. There is a fair amount of setup work with certificates and a remote MySQL server to test ssl connections. Applying this patch fixed the failure for me.

 * these should allow someone who is not familiar with the affected
   package to reproduce the bug and verify that the updated package fixes
   the problem.

[Regression Potential]

 * People rebuilding from source could foul up the SSL dependencies so that they could specify SSL parameters within a python-mysqldb connection request, but not have SSL support in their compiled versions of the MySQL client libraries.

My usage includes both SSL connections and unencrypted "regular" connections. All work fine.

[Other Info]

The need for this patch disappears when you catch up to the latest python-mysqldb.

I had problems when I attempted to compile the most recent version of python-mysqldb in the 1.2 series on my Ubuntu 12.04 system. That's why I settled for the simple patch to enable SSL without picking up other changes. It appears that Debian is your upstream source for python-mysqldb. I presume they will understand and deal with any additional changes forced by the later versions.