Hello community,
here is the log from the commit of package xtrabackup for openSUSE:Factory checked in at 2013-11-26 19:35:35
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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 2013-09-26 07:22:12.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.xtrabackup.new/xtrabackup.changes 2013-11-26 19:35:37.000000000 +0100
@@ -1,0 +2,39 @@
+Mon Nov 25 22:46:42 UTC 2013 - andreas.stieger@gmx.de
+
+- update to 2.1.6 [bnc#852224]
+- New Features:
+ * New innobackupex --force-non-empty-directories option
+ * now supports logs created with the new log block checksums
+- New Features specific to MySQL 5.6:
+ option innodb_log_checksum_algorithm in Percona Server 5.6
+- Bugs Fixed:
+ * innobackupex --copy-back fails on empty innodb_data_home_dir
+ * A fixed initialization vector (constant string) was used while
+ encrypting the data. This opened the encrypted stream/data to
+ plaintext attacks among others.
+ * innobackupex --version-check is now on by default.
+ * Since Version Check is enabled by default, new optin
+ --no-version-check option has been introduced to disable it.
+ * xtrabackup_slave_info didn't contain any GTID information, which
+ could cause master_auto_position not to work properly
+ * now supports absolute paths in innodb_data_file_path variable.
+ * wouldn't back up the empty directory created with mkdir
+ (i.e. test) outside of the server which could lead to
+ inconsistencies during the Percona XtraDB Cluster State Snapshot
+ Transfer.
+ * wasn't able to perform backups to the NFS mount in some NFS
+ configurations, because it was trying to preserve file ownership.
+ * unable to perform backup if innodb_log_arch_dir variable was
+ used in server configuration
+ * Race condition in start_query_killer child code could cause
+ parent MySQL connection to close.
+ - Bugs Fixed specific to MySQL 5.6:
+ * xtrabackup_56 was using CRC32 as the default checksum algorithm
+ This could cause error if the innodb_checksum_algorithm value
+ was changed to strict_innodb value after a restore.
+ * xtrabackup_56 binary didn't store the server’s
+ innodb_checksum_algorithm value to backup-my.cnf. This value is
+ needed because it affects the on-disk data format.
+- update and tag percona-xtrabackup-2.1.x-nodoc.patch
+
+-------------------------------------------------------------------
Old:
----
percona-xtrabackup-2.1.5-nodoc.tar.gz
New:
----
percona-xtrabackup-2.1.6-nodoc.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ xtrabackup.spec ++++++
--- /var/tmp/diff_new_pack.xVKe2J/_old 2013-11-26 19:35:39.000000000 +0100
+++ /var/tmp/diff_new_pack.xVKe2J/_new 2013-11-26 19:35:39.000000000 +0100
@@ -23,7 +23,7 @@
License: GPL-2.0
Group: Productivity/Databases/Tools
Name: xtrabackup
-Version: 2.1.5
+Version: 2.1.6
Release: 0
Url: http://www.percona.com/software/percona-xtrabackup/
Source: percona-xtrabackup-%{version}-nodoc.tar.gz
++++++ percona-xtrabackup-2.1.5-nodoc.tar.gz -> percona-xtrabackup-2.1.6-nodoc.tar.gz ++++++
/work/SRC/openSUSE:Factory/xtrabackup/percona-xtrabackup-2.1.5-nodoc.tar.gz /work/SRC/openSUSE:Factory/.xtrabackup.new/percona-xtrabackup-2.1.6-nodoc.tar.gz differ: char 5, line 1
++++++ percona-xtrabackup-2.1.x-nodoc.patch ++++++
--- /var/tmp/diff_new_pack.xVKe2J/_old 2013-11-26 19:35:39.000000000 +0100
+++ /var/tmp/diff_new_pack.xVKe2J/_new 2013-11-26 19:35:39.000000000 +0100
@@ -1,3 +1,8 @@
+From: Andreas Stieger