Hello community, here is the log from the commit of package xtrabackup for openSUSE:Factory checked in at 2012-12-07 14:53:11 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/xtrabackup (Old) and /work/SRC/openSUSE:Factory/.xtrabackup.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "xtrabackup", Maintainer is "" Changes: -------- --- /work/SRC/openSUSE:Factory/xtrabackup/xtrabackup.changes 2012-10-03 10:46:34.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.xtrabackup.new/xtrabackup.changes 2012-12-07 14:53:13.000000000 +0100 @@ -1,0 +2,36 @@ +Wed Dec 5 21:02:57 UTC 2012 - andreas.stie...@gmx.de + +- update to 2.0.4 + + a regression introduced in XtraBackup 2.0.2 caused incremental + backups to fail because the init parameter values were not + normalized to the values used inside InnoDB + + a regression introduced in traBackup 2.0.2 didn’t take the + separate doublewrite tablespace into an account + + XtraBackup was handling the separate doublewrite buffer file + incorrectly. File path of the doublewrite buffer wasn’t added + to the backup-my.cnf and after the restore old doublewrite buffer + file was used instead of one made during the prepare stage + + XtraBackup now accepts the --innodb=force option, previously it + would throw an error if the option was set + + Option safe-slave-backup wasn’t working correctly + + In case safe-slave-backup-timeout was reached when using the + safe-slave-backup option, SQL_THREAD was left in stopped state + causing the slave thread to lag behind. This was fixed by + checking the initial SQL_THREAD state and starting it before + terminating with a timeout error and starting the SQL_THREAD + only if it was running initially. + + In case of streaming backups, innobackupex would resume the + Xtrabackup process and then wait for it to finish before running + UNLOCK TABLES. This caused database to be unnecessarily locked + with FLUSH TABLES WITH READ LOCK. Innobackupex now waits only + till log copying is finished to unlock the databases + + XtraBackup would fail on --apply-log when filesystem didn’t + support Linux AIO + + XtraBackup binary would ignore innodb_use_native_aio when it’s + specified either in my.cnf or as a command line option + + XtraBackup would print a warning message during the prepare + stage about innodb_file_io_threads being deprecated, even if the + variable wasn’t set + + XtraBackup Galera tests can now be run concurrently + +------------------------------------------------------------------- Old: ---- percona-xtrabackup-2.0.3-nodoc.tar.gz New: ---- percona-xtrabackup-2.0.4-nodoc.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ xtrabackup.spec ++++++ --- /var/tmp/diff_new_pack.jMlm0p/_old 2012-12-07 14:53:16.000000000 +0100 +++ /var/tmp/diff_new_pack.jMlm0p/_new 2012-12-07 14:53:16.000000000 +0100 @@ -23,7 +23,7 @@ License: GPL-2.0 Group: Productivity/Databases/Tools Name: xtrabackup -Version: 2.0.3 +Version: 2.0.4 Release: 0 Url: http://www.percona.com/software/percona-xtrabackup/ Source: percona-xtrabackup-%{version}-nodoc.tar.gz ++++++ percona-xtrabackup-2.0.3-nodoc.tar.gz -> percona-xtrabackup-2.0.4-nodoc.tar.gz ++++++ /work/SRC/openSUSE:Factory/xtrabackup/percona-xtrabackup-2.0.3-nodoc.tar.gz /work/SRC/openSUSE:Factory/.xtrabackup.new/percona-xtrabackup-2.0.4-nodoc.tar.gz differ: char 5, line 1 ++++++ xtrabackup-nodoc.sh ++++++ --- /var/tmp/diff_new_pack.jMlm0p/_old 2012-12-07 14:53:16.000000000 +0100 +++ /var/tmp/diff_new_pack.jMlm0p/_new 2012-12-07 14:53:16.000000000 +0100 @@ -14,7 +14,7 @@ # published by the Open Source Initiative. # -XTRABACKUP_VERSION=2.0.3 +XTRABACKUP_VERSION=2.0.4 MYSQL51_VERSION=5.1.59 MYSQL55_VERSION=5.5.17 -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
