Hello community,

here is the log from the commit of package xtrabackup for openSUSE:Factory 
checked in at 2014-10-05 20:32:17
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/xtrabackup (Old)
 and      /work/SRC/openSUSE:Factory/.xtrabackup.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "xtrabackup"

Changes:
--------
--- /work/SRC/openSUSE:Factory/xtrabackup/xtrabackup.changes    2014-09-15 
18:24:42.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.xtrabackup.new/xtrabackup.changes       
2014-10-05 20:34:03.000000000 +0200
@@ -1,0 +2,35 @@
+Sun Oct  5 11:55:10 UTC 2014 - andreas.stie...@gmx.de
+
+- Percona XtraBackup 2.2.5
+- New features:
+  * Percona XtraBackup has been rebased on MySQL 5.6.21.
+- Bugs fixed:
+  * Fix a regression for users with huge numbers of InnoDB
+    tablespaces, and the workaround of raising the open files
+    limits didnt work in all cases due to a limitation in the Linux
+    kernel. A new innobackupex --close-files option has been
+    implemented to close the file handles once they are no longer
+    accessed. NOTE: Using this option may result in a broken
+    backup if DDL is performed on InnoDB tables during the backup.
+  * Fix a regression since  2.2.0 which caused Percona XtraBackup
+    to fail to copy redo logs in random cases.
+  * innobackupex --galera-info didn't copy the last binlog file
+    when it was taking a backup from server where backup locks are
+    supported.
+  * xtrabackup binary would accept arguments that were not options,
+    which could lead to unexpected results.
+  * If innobackupex is run against MySQL 5.1 with built-in InnoDB,
+    it will now suggest using Percona XtraBackup 2.0 or upgrading
+    to InnoDB plugin, rather than just failing with the generic
+    unsupported server version message.
+  * Using the (deprecated) log parameter in mysqld section would
+    cause backups to fail.
+  * Percona XtraBackup now uses MySQL code to get the stack trace
+    in case Percona XtraBackup crashes with a segmentation fault or
+    an assertion failure.
+  * Attempt to use any of the following options without the
+     --incremental option now fails with an error message rather than
+    create a full backup: --incremental-lsn, --incremental-basedir,
+    --incremental-history-name, --incremental-history-uuid.
+
+-------------------------------------------------------------------

Old:
----
  percona-xtrabackup-2.2.4-nodoc.tar.xz

New:
----
  percona-xtrabackup-2.2.5-nodoc.tar.xz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ xtrabackup.spec ++++++
--- /var/tmp/diff_new_pack.2IZIT7/_old  2014-10-05 20:34:04.000000000 +0200
+++ /var/tmp/diff_new_pack.2IZIT7/_new  2014-10-05 20:34:04.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           xtrabackup
-Version:        2.2.4
+Version:        2.2.5
 Release:        0
 Summary:        Online backup for MySQL / InnoDB
 License:        GPL-2.0

++++++ percona-xtrabackup-2.2.4-nodoc.tar.xz -> 
percona-xtrabackup-2.2.5-nodoc.tar.xz ++++++
/work/SRC/openSUSE:Factory/xtrabackup/percona-xtrabackup-2.2.4-nodoc.tar.xz 
/work/SRC/openSUSE:Factory/.xtrabackup.new/percona-xtrabackup-2.2.5-nodoc.tar.xz
 differ: char 27, line 1

-- 
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org

Reply via email to