Log message:
Changes 5.1.60:
* Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not
  work. Now on Linux it is possible to use rpm -U to replace any installed MySQL
  product by any other of the same release family. It is not necessary to remove
  the old produce with rpm -e first.
* MEMORY table creation time is now available in the CREATE_TIME column of the
  INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE
  STATUS output.
Bugs Fixed
* Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost  \ 
 if the server crashed at a precise moment when other columns were being
  updated in an InnoDB table.
* InnoDB Storage Engine: This fix improves the performance of instrumentation
  code for InnoDB buffer pool operations.
* InnoDB Storage Engine: Lookups using secondary indexes could give incorrect
  matches under a specific set of conditions. The conditions involve an index
  defined on a column prefix, for a BLOB or other long column stored outside
  the index page, with a table using the Barracuda file format.
* InnoDB Storage Engine: This fix corrects cases where the MySQL server could
  hang or abort with a long semaphore wait message. (This is a different issue
  than when these symptoms occurred during a CHECK TABLE statement.)
* Replication: Issuing the following statements, in the order shown, could cause \ 
 a deadlock between the user thread and I/O thread.
* more...

Log message:
Update mysql51-client and mysql51-server package to 5.1.58 (MySQL 5.1.58).

This is bug fix release.  Since whole changes are too many to write here,
please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html.

Especially, some important one for related to us.

* On FreeBSD 64-built builds of the embedded server, exceptions were not
  prevented from propagating into the embedded application. (Bug #38965,
  Bug #11749418)

Log message:
Update mysql51-{client,server} package to 5.1.57.

This is simply maintenance release, no security fix.
Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-57.html in
detail.

Log message:
not compatible with mysql-5.5.

Log message:
patch-ab: take 2

Log message:
Fix building with Clang.

Log message:
Update MySQL package to 5.1.56.

Functionality added or changed:

* mysqldump --xml now displays comments from column definitions. (Bug #13618)

Bugs fixed:

* InnoDB Storage Engine: InnoDB returned values for ¡Èrows examined¡É
  in the query plan that were higher than expected. NULL values were
  treated in an inconsistent way. The inaccurate statistics could
  trigger ¡Èfalse positives¡É in combination with the MAX_JOIN_SIZE
  setting, because the queries did not really examine as many rows as
  reported. (Bug #30423)

* Partitioning: Trying to use the same column more than once in the
  partitioning key when partitioning a table by KEY caused mysqld to
  crash. Such duplication of key columns is now expressly disallowed,
  and fails with an appropriate error. (Bug #53354, Bug #57924)

* Replication: When using the statement-based logging format, INSERT
  ON DUPLICATE KEY UPDATE and INSERT IGNORE statements affecting
  transactional tables that did not fail were not written to the
  binary log if they did not insert any rows. (With statement-based
  logging, all successful statements should be logged, whether they do
  or do not cause any rows to be changed.) (Bug #59338)

* Replication: Formerly, STOP SLAVE stopped the slave I/O thread first
  and then stopped the slave SQL thread; thus, it was possible for the
  I/O thread to stop after replicating only part of a transaction
  which the SQL thread was executing, in wich case¡½if the transaction
  could not be rolled back safely¡½the SQL thread could hang.

  Now, STOP SLAVE stops the slave SQL thread first and then stops the
  I/O thread; this guarantees that the I/O thread can fetch any
  remaining events in the transaction that the SQL thread is
  executing, so that the SQL thread can finish the transaction if it
  cannot be rolled back safely. (Bug #58546)

* A query of the following form returned an incorrect result, where
  the values for col_name in the result set were entirely replaced
  with NULL values:

  SELECT DISTINCT col_name ... ORDER BY col_name DESC;
  (Bug #59308, Bug #11766241)

* DELETE or UPDATE statements could fail if they used DATE or DATETIME
  values with a year, month, or day part of zero. (Bug #59173)

* The ESCAPE clause for the LIKE operator allows only expressions that
  evaluate to a constant at execution time, but aggregrate functions
  were not being rejected. (Bug #59149)

* Memory leaks detected by Valgrind, some of which could cause
  incorrect query results, were corrected. (Bug #59110, Bug #11766075)

  mysqlslap failed to check for a NULL return from mysql_store_result()
  and crashed trying to process the result set. (Bug #59109)

* In debug builds, SUBSTRING_INDEX(FORMAT(...), FORMAT(...)) could
  cause a server crash. (Bug #58371)

* When mysqldadmin was run with the --sleep and --count options, it
  went into an infinite loop executing the specified command. (Bug
  #58221)

* Some string manipulating SQL functions use a shared string object
  intended to contain an immutable empty string. This object was used
  by the SQL function SUBSTRING_INDEX() to return an empty string when
  one argument was of the wrong datatype. If the string object was
  then modified by the SQL function INSERT(), undefined behavior
  ensued. (Bug #58165, Bug #11765225)

* Parsing nested regular expressions could lead to recursion resulting
  in a stack overflow crash. (Bug #58026, Bug #11765099)

* The mysql client went into an infinite loop if the standard input
  was a directory. (Bug #57450)

* The expression const1 BETWEEN const2 AND field was optimized
  incorrectly and produced incorrect results. (Bug #57030, Bug
  #11764215)

* Some RPM installation scripts used a hardcoded value for the data
  directory, which could result in a failed installation for users who
  have a nonstandard data directory location. The same was true for
  other configuration values such as the PID file name. (Bug #56581,
  Bug #11763817)

* On FreeBSD and OpenBSD, the server incorrectly checked the range of
  the system date, causing legal values to be rejected. (Bug #55755,
  Bug #11763089)

* When using ExtractValue() or UpdateXML(), if the XML to be read
  contained an incomplete XML comment, MySQL read beyond the end of
  the XML string when processing, leading to a crash of the
  server. (Bug #44332)

Log message:
Update mysql51-{client,server} package to 5.1.55.

Full changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-55.html

MySQL 5.1.55

Functionality added or changed:

The time zone tables available at
http://dev.mysql.com/downloads/timezones.html have been updated. These
tables can be used on systems such as Windows or HP-UX that do not
include zoneinfo files. (Bug#40230)

Log message:
Update mysql51-{client,server} package to 5.1.54.

Functionality added or changed:

* Support for the IBMDB2I storage engine has been removed. (Bug#58079)

* The pstack library was nonfunctional and has been removed, along with the
  --with-pstack option for configure. The --enable-pstack option for mysqld is
  deprecated and will be removed in MySQL 5.5. (Bug#57210)

Bugs fixed:

* Performance: InnoDB Storage Engine: Improved concurrency when several
  ANALYZE TABLE or SHOW TABLE STATUS statements are run simultaneously for
  InnoDB tables. (Bug#53046)

* InnoDB Storage Engine: For an InnoDB table created with
  ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, a query using the READ
  UNCOMMITTED isolation level could cause the server to stop with an assertion
  error, if BLOB or other large columns that use off-page storage were being
  inserted at the same time. (Bug#57799)

* Partitioning: An INSERT ... ON DUPLICATE KEY UPDATE column = 0 statement on
  an AUTO_INCREMENT column caused the debug server to crash. (Bug#57890)

* Several compilation problems were fixed. (Bug#57992, Bug#57993, Bug#57994,
  Bug#57995, Bug#57996, Bug#57997, Bug#58057)

* Passing a string that was not null-terminated to UpdateXML() or
  ExtractValue() caused the server to fail with an assertion. (Bug#57279)

* Queries executed using the Index Merge access method and a temporary file
  could return incorrect results. (Bug#56862)

* The find_files() function used by SHOW statements performed redundant and
  unnecessary memory allocation. (Bug#51208)

Log message:
Update mysql51-{client,server} to 5.1.53.

Most changes are related to replication and seems to no security fix.
For more detail, please refer:

	http://dev.mysql.com/doc/refman/5.1/en/news-5-1-53.html