lp:~maxb/ubuntu/lucid/python-mysqldb/py2.7

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

23. By Max Bowsher on 2012-11-16

No-change rebuild to add python2.7 support.

22. By Matthias Klose on 2010-02-01

Rebuild dropping the extension for python2.5.

21. By Jonas Meurer <email address hidden> on 2009-08-27

[ Jonas Meurer ]
* fix 02_python_2.6.dpatch to use set insteat of Set in conversions{}.
  thanks to Chris Lamp for the bugreport. (closes: #543667)

[ Bernd Zeimetz ]
* Removing myself from uploaders.
* Use py_setup_install_args from /usr/share/python/python.mk

20. By Mathias Gug on 2009-08-18

* Merge from debian unstable, remaining changes:
  - Add 07_python_2.6.dpatch to fix python 2.6 related warnings. (LP: #341943)
  - Build for python2.6.

19. By Mario Limonciello on 2009-08-15

Add 07_python_2.6.dpatch to fix python 2.6 related warnings. (LP: #341943)

18. By Matthias Klose on 2009-02-23

Build for python2.6.

17. By Bernd Zeimetz on 2008-06-16

[ Sandro Tosi ]
* debian/control
  - list items lines in description starts with 2 space, to avoid reformat
    on webpages (Closes: #480341)

[ Bernd Zeimetz ]
* debian/patches/02_reconnect.dpatch:
  - Dropping patch:
    Comment in Storm which explains the problem:

      # Here is another sad story about bad transactional behavior. MySQL
      # offers a feature to automatically reconnect dropped connections.
      # What sounds like a dream, is actually a nightmare for anyone who
      # is dealing with transactions. When a reconnection happens, the
      # currently running transaction is transparently rolled back, and
      # everything that was being done is lost, without notice. Not only
      # that, but the connection may be put back in AUTOCOMMIT mode, even
      # when that's not the default MySQLdb behavior. The MySQL developers
      # quickly understood that this is a terrible idea, and removed the
      # behavior in MySQL 5.0.3. Unfortunately, Debian and Ubuntu still
      # have a patch right now which *reenables* that behavior by default
      # even past version 5.0.3.

16. By Matthias Klose on 2008-04-09

Disable the 02_reconnect patch. LP: #64270, #163184.

Comment in Storm which explains the problem:

# Here is another sad story about bad transactional behavior. MySQL
# offers a feature to automatically reconnect dropped connections.
# What sounds like a dream, is actually a nightmare for anyone who
# is dealing with transactions. When a reconnection happens, the
# currently running transaction is transparently rolled back, and
# everything that was being done is lost, without notice. Not only
# that, but the connection may be put back in AUTOCOMMIT mode, even
# when that's not the default MySQLdb behavior. The MySQL developers
# quickly understood that this is a terrible idea, and removed the
# behavior in MySQL 5.0.3. Unfortunately, Debian and Ubuntu still
# have a patch right now which *reenablesthat behavior by default
# even past version 5.0.3.

15. By Bernd Zeimetz on 2007-10-14

[ Piotr Ożarowski ]
* Rename XS-Vcs-Svn field to Vcs-Svn (dpkg supports it now)
* Add Vcs-Browser field

[ Bernd Zeimetz ]
* debian/patches:
  - Adding 05_null-connection-guard.dpatch, providing an interface to set
    MYSQL_OPT_RECONNECT
  - Adding 00dpatch.conf to make the handling of dpatches more easy
* debian/control
  - Adding myself as uploader
  - Adding Homepage field
  - Replacing the depricated ${Source-Version} by ${binary:Version} in the
    dependency list of python-mysqldb-dbg

14. By Andrew Mitchell on 2007-05-23

* Merge from debian unstable, remaining changes:
  - Build a python-mysqldb-dbg package.
  - Set Ubuntu maintainer address.
* Dropped 04_unicode.patch, integrated upstream.